Skip to content
Draft
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions apps/inbox/index.css
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,8 @@
@import "../../packages/inbox/prs/prs.css";
/* A launched session's permission prompt (components/PermissionCard.tsx). */
@import "../../packages/inbox/permissionCard.css";
/* Two thread panes side by side ("Open beside", packages/inbox/panes/). */
@import "../../packages/inbox/panes/panes.css";
/* The sidebar's Agents section and the animated agent marks (packages/inbox/agents/). */
@import "../../packages/inbox/agents/agents.css";
@import "../../packages/inbox/agents/iconDialog.css";
Expand Down
1 change: 1 addition & 0 deletions docs/agent-guides/environment.md
Original file line number Diff line number Diff line change
Expand Up @@ -153,6 +153,7 @@
- `inboxPlans` (`true` / `false`, default off): Plans in the Plannotator Inbox (`inbox-plans.md`). On only by the person: `plannotator plans` (no gate), or `POST /api/inbox/settings` `{ plans: { on } }` from the window; `plannotator plans off` turns it off and keeps `plan-library/`. Off or unset: every `/api/plans` path answers `404`, the library is never opened or imported, the settings answer has no `plans` key, and nothing an agent reads changes. On: the read-only import of `history/`, `plans/` and `feedback/` into `<data dir>/plan-library/` runs in the background. Read on every request. No env-var equivalent.
- `inboxChapterDiagrams` (`true` / `false`, default on): Chapter diagrams in the Plannotator Inbox, under Code review (Settings → Capabilities → Chapter diagrams, row `data-settings-chapter-diagrams`, shown only while `inboxCodeReview` is on). Off (`false`): with Code review on, get_guide_brief has no chapter diagram rule and no `sections[].diagram` in its schema, submit_guide's `guide` field has no `diagram?`, and `/review-curate` and `/review-recheck` have no diagram line (removals only, as Shape off removes Shape's words); submit_guide still takes a diagram, and the window draws one folded under its Diagram header (one click opens it; nothing is kept). Read on every request (`inboxChapterDiagramsOn` in `packages/shared/config.ts`). Written through `POST /api/inbox/settings` `{ chapter_diagrams: { on } }` (the owner only; the windows hear it as `event: capabilities`, present there and in the settings answer only while Code review is on). No env-var equivalent. Tests: `packages/server/inbox-chapter-diagrams-switch.test.ts`, `apps/hook/server/show-me-off.test.ts`, `packages/inbox/reviewSkills.test.ts`, DOM `packages/inbox/guideChapterDiagram.test.tsx`.
- `inboxSystem` (`true` / `false`, default off): System in the Plannotator Inbox (see `inbox-system.md`), shown only while `inboxCodeReview` is on. In 0.29 System stays off and hidden (approval "system-inbox", addendum 2026-11-08): it turns on only by setting `inboxSystem: true` here, for testing. Settings → Capabilities → System (under Code review, shown only while it is on, and while hidden only once System is on: `SYSTEM_SETTINGS_ROW_VISIBLE` in `packages/inbox/components/Settings.tsx`) writes it through `POST /api/inbox/settings` `{ system: { on } }`. Off: the window shows nothing of System and `/api/inbox/system/*` answers `409 system_off`; drawings are kept.
- `inboxSplitView` (`true` / `false`, default off): a preview of the Inbox's second thread pane. On: a row's menu offers "Open beside" while another thread is open and the list and two threads fit in the window with the sidebar folded: the list's 380 px, two 440 px thread columns (`stack.ts`) and the gutters, 1292 px with the Soft look (`besideFits` in `panes/beside.ts`). Where a docked sidebar leaves too little room (a 1440 px window with the default 232 px sidebar), choosing it folds the sidebar on screen without writing the person's choice (`sidebarHeld`, `panes/sidebarHold.ts`), and closing the second pane brings it back; a sidebar the person folded stays folded. The two threads then share the room after the list, each its own pane (header, scroll, reply box, ✕), only the active one counting messages as seen. The list's edge hides the list (and the sidebar) as for one thread, and the first pane's ‹ Inbox brings them back; a pair that loses the room (the person opens the sidebar, the window narrows) covers the list as one thread does, and below 904 px it is one pane again. Closing either pane is one pane again. No Settings row and not in the public docs; the settings read carries `split_view: { on: true }` only while on (`packages/server/inbox.ts`), read on every request. Off: nothing changes. Tests: `packages/server/inbox-split-view.test.ts`, `packages/inbox/panes/openBeside.test.tsx`, `tests/e2e/inbox-open-beside.spec.ts`.
- `inboxBoardIntro` (`{ shownAt? }`): when the Plannotator Inbox's Board first-visit dialog was shown, once per machine, and only once the Board is on. Written only by the server (`POST /api/inbox/board/intro`, a compare-and-set: the first page on this computer or the owner's over their tailnet to ask gets the dialog). The Board reveal's claim never writes it (the owner, 2026-11-04: its offer has no Copy prompt), so the first visit to a Board turned on from the offer, or later in Settings after Not now, shows this welcome with Copy prompt; someone who already has it (seen before, 0.28.49 included) does not see it again. Remove it to see the dialog again; the Board's "?" opens it any time. No env-var equivalent.
- `inboxReveals` (`{ lastShownAt?, dayShownAt?, notNowAt?, shownLoad?, agentNote?: { shownFor? }, waitingSince?: { sound?, list_intro?, voice?, snooze?, bro?, board?, steps? }, board?: { shownAt?, key? }, steps?: { shownAt?, key? }, bro?: { shownAt?, key? }, star?: { shownAt?, key? }, launch_tip?: { shownAt?, key?, launchedAt? }, sidebar_tip?: { shownAt?, key? } }`; `launch_tip` is the Launch tip's stamp, outside the line, and `launchedAt` when an agent was first seen started here (approval "launch-tip", `inbox-launch.md`); `sidebar_tip` is the Sidebar tip's stamp, outside the line too ("The Sidebar tip" in `inbox-window.md`); the schedule's fields, approval "inbox-one-time-dialogs": `dayShownAt` the last dialog of the line, the agent note included (the gap counts from it too; the one-a-day rule it was named for ended 2026-11-09); `notNowAt` the last offer closed with Not now (offers only), three days before the next (the owner, 2026-11-06; it was four); `shownLoad` the page load that showed the last dialog, so the load first seen right after it shows none (which load came after which is kept in the server's memory, not here); `agentNote.shownFor` the agents the agent note was shown for, once each; `waitingSince` also retires an offer after 14 days, never an update-day dialog): the queue of one-time reveals for returning users (rules in `packages/shared/inbox/reveals.ts`; "Reveals for returning users" in `inbox-window.md`). Written only by the server. `lastShownAt`: the last one-time announcement claimed on this machine by a release build (list options, voice, Snooze, the Board); the fresh-install stamps of the list and voice intros are not shows and do not write it. The 40-minute spacing's clock (the owner, 2026-11-09; it was one day, and 48 h before that) is the latest of `lastShownAt`, `inboxSnoozeIntro.shownAt`, `inboxBoardIntro.shownAt`, and `inboxListIntro.shownAt` / `inboxVoiceIntro.shownAt` when beside a `dueAt` (an announcement shown before this key existed). `waitingSince`: the first time each reveal was next, for the 3-day patience (calendar time; when every qualifying reveal has waited that long, the longest wait goes). `board.shownAt`: the Board reveal was claimed (it turns nothing on and never stamps `inboxBoardIntro`). `steps.shownAt`: the Checklist reveal was claimed (it turns nothing on). `bro.shownAt`: the Bro mode offer was claimed (it turns nothing on). `key` beside any of them: the claiming page's own key, so that page's retry after a lost answer is shown it again; any other key is not. A dev build reads and writes none of it. Remove `board` and `lastShownAt`, any announcement stamp from the last day (and `inboxBoardIntro.shownAt` if the Board's welcome was shown since), and unset `inboxBoard`, to see the Board reveal again. Remove `bro` and `lastShownAt`, any announcement stamp from the last day, and unset `inboxBro`, to see the Bro mode offer again (it also needs heavy use). No env-var equivalent.
- `starAsk` (`{ checkedAt?, canStar?, shownAt?, surface?, answer?, answeredAt? }`, unset by default): the "Star the repo" ask (approval "star-ask"; `packages/shared/star-ask.ts`), once per machine across the Inbox, plan review, code review and annotate. Written only by the servers: `checkedAt` and `canStar` when the already-starred check ran (a done-screen page at load; reused, never re-run; the ask stays open), `shownAt` and `surface` (`inbox`, `plan`, `review`, `annotate`) when a surface drew it, `answer` (`starred`, `opened`, `not-now`, or `already` when the check found the repo starred before anything showed). A `shownAt` or `answer`, or any value that is not an object, means it never shows again. Remove the key to see the ask again in a scratch env.
Expand Down
4 changes: 2 additions & 2 deletions docs/agent-guides/inbox-messages.md

Large diffs are not rendered by default.

Loading
Loading