You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/ui/src/features/inbox/CLAUDE.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,13 @@ The Inbox is the PostHog surface for **Self-driving**: agents that watch product
4
4
5
5
## Product Model
6
6
7
-
The renderer still talks to backend endpoints and TypeScript types with the legacy `signals` naming. User-facing copy should say **Self-driving**, **Responder**, **report**, **run**, or **finding** depending on context. Do not rename backend paths or shared API fields unless the PostHog Cloud backend has changed too.
7
+
The renderer still talks to backend endpoints and TypeScript types with the legacy `signals` naming. User-facing copy should say **Self-driving**, **agent**, **report**, **run**, or **signal** depending on context. Do not rename backend paths or shared API fields unless the PostHog Cloud backend has changed too.
8
8
9
9
The main objects are:
10
10
11
11
-`SignalReport`: the unit shown in all Inbox tabs.
12
12
- Findings: the source observations that contributed to a report, fetched separately for detail screens.
13
-
- Artefacts: structured agent output attached to a report, such as priority, actionability, suggested reviewers, repo selection, and findings from research.
13
+
- Artefacts: structured agent output attached to a report, such as priority, actionability, suggested reviewers, repo selection, and signals from research.
14
14
- Report tasks: links from a report to tasks created for research or implementation.
15
15
16
16
## Information Architecture
@@ -53,7 +53,7 @@ same artefact-lift pattern as `priority`/`actionability`/`already_addressed` —
53
53
so cards avoid an N+1 per-card artefact fetch. Unknown reason codes fall back to
54
54
the raw value; cards with no dismissal artefact simply omit the chip.
55
55
56
-
Responder configuration is **not** an Inbox tab. It is the top-level Responders sidebar item at `/code/agents`. The legacy `/code/inbox/agents` route redirects there.
56
+
Agent configuration is **not** an Inbox tab. It is the top-level Agents sidebar item at `/code/agents`. The legacy `/code/inbox/agents` route redirects there.
57
57
58
58
Reviewer scope is a UI preference stored in `inboxReviewerScopeStore`. It filters the list between reports suggested for the current user and reports for someone else. It does not change tab membership; the tab predicates are independent.
59
59
@@ -90,7 +90,7 @@ Tab membership and counts live in `utils/reportMembership.ts`. Keep that file as
90
90
Detail screens layer additional data on top of the base report:
91
91
92
92
-`useInboxReportById(reportId)` for the report record.
93
-
-`useInboxReportSignals(reportId)` for contributing findings.
93
+
-`useInboxReportSignals(reportId)` for contributing signals.
94
94
-`useInboxReportArtefacts(reportId)` for structured outputs such as suggested reviewers and repo selection.
95
95
-`useReportTasks(reportId, status)` for linked research/implementation tasks.
96
96
@@ -102,7 +102,7 @@ The Inbox reads from PostHog Cloud's Self-driving backend, currently implemented
102
102
103
103
-`GET /api/projects/{teamId}/signals/reports/`: paginated report list. Supports filters such as status, ordering, source product, suggested reviewers, and priority.
104
104
-`GET /api/projects/{teamId}/signals/reports/{id}/`: single report detail.
-`GET /api/projects/{teamId}/signals/reports/{id}/tasks/`: tasks linked to a report.
108
108
@@ -112,7 +112,7 @@ Card headlines are derived client-side from `summary` by `utils/reportPresentati
112
112
113
113
## Configuration Surface
114
114
115
-
Responder setup lives in `features/agents/components/AgentsView.tsx`, which mounts `ConfigureAgentsSection`. This surface composes existing GitHub, Slack, source-toggle, and MCP configuration pieces. Keep setup copy outcome-focused: the user is asking Self-driving to figure out what matters, not choosing internal artefact types.
115
+
Agent setup lives in `features/agents/components/AgentsView.tsx`, which mounts `ConfigureAgentsSection`. This surface composes existing GitHub, Slack, source-toggle, and MCP configuration pieces. Keep setup copy outcome-focused: the user is asking Self-driving to figure out what matters, not choosing internal artefact types.
116
116
117
117
Onboarding/setup should be task-backed when it starts work. Do not model it as a static checklist if the intended behavior is to launch an agent task.
118
118
@@ -124,7 +124,7 @@ Shared primitives exist to keep the surfaces consistent:
124
124
125
125
-`InboxDetailPageHeader` for detail headers.
126
126
-`DetailSection` for content sections inside detail screens.
127
-
-`SignalsList` and the existing detail `SignalCard` for contributing findings.
127
+
-`SignalsList` and the existing detail `SignalCard` for contributing signals.
128
128
- Badge and metadata helpers in `components/utils/` and `InboxMetaRow`.
129
129
-`SOURCE_PRODUCT_META` for source-product labels and icons.
130
130
@@ -134,7 +134,7 @@ When adding or changing UI, reuse those primitives first. Avoid encoding one-off
134
134
135
135
- Do not reuse the deleted legacy `ReportListRow`, `ReportDetailPane`, or old list/detail stores.
136
136
- Do not put page-level Inbox title or navigation into the global app header; `InboxView` owns the Inbox page chrome.
137
-
- Do not add a configure shortcut back into the Inbox header; Responders configuration is a sidebar destination.
137
+
- Do not add a configure shortcut back into the Inbox header; Agents configuration is a sidebar destination.
138
138
- Scout (`signals_scout`) is a real Cloud source product. Keep it covered wherever source products surface: `INBOX_SOURCE_OPTIONS`, `SOURCE_PRODUCT_META`, and the scout-name display in `SignalCard`.
139
139
- Scout management UI (fleet configuration, run history) lives in `features/scouts/` and is backed by the PostHog Cloud scout endpoints (`/api/projects/{teamId}/signals/scout/`). Do not add scout controls that have no backing endpoint there.
140
140
- Do not put preview shims or mock report data in `apps/code/index.html`; the app shell should stay minimal.
0 commit comments