agentbox-app 0.1.7 → 0.1.11

package/shared/agents.mjs

@@ -49,24 +49,22 @@ export function sameInstant(a, b) {
 // already records each worker's sessionId when it spawns it. Either alone is
 // enough; both means the fold cannot drift as one of them changes.
 //
-// This matters because without it Agentbox shouts its own work back at her. In
-// the raw picture she asked to see, rows two and three were agentbox-bf and
-// agentbox-a8 — Agentbox's own workers, already in her inbox as work items, filing
-// a second row about themselves.
+// This matters because without it Agentbox shouts its own work back at the
+// user. In the raw list, Agentbox's own workers, already in the inbox as work
+// items, showed up again as a second row about themselves.
 export function startedByZero(agent, { pids = new Set(), sessionIds = new Set() } = {}) {
   if (agent.sessionId && sessionIds.has(agent.sessionId)) return true;
   return !!agent.ppid && pids.has(agent.ppid);
 }
 
 /* --------------------------- is it asking anything ----------------------- */
-// A ROW THAT ASKS NOTHING DOES NOT GET FILED. Her standing rule, and the one
-// place this feature could most easily break it: of the 13 outside agents on
-// her machine, 12 were idle and 1 was waiting. Filing all 13 puts twelve rows
-// in front of her that say "nothing is asked", which is the picture she
-// rejected.
-//
-// So the inbox takes exactly the agents that are waiting on a human. The other
-// twelve are still listed, still findable, one keystroke away — they just do
+// A ROW THAT ASKS NOTHING DOES NOT GET FILED. A standing rule, and the one
+// place this feature could most easily break it: most outside agents on a
+// machine are idle at any moment, and filing them all puts a wall of rows in
+// the inbox that say "nothing is asked".
+//
+// So the inbox takes exactly the agents that are waiting on a human. The
+// others are still listed, still findable, one keystroke away — they just do
 // not interrupt.
 export function asksSomething(agent) {
   return agent.status === 'waiting';
@@ -79,14 +77,14 @@ export function asksSomething(agent) {
 //   "input needed"      the agent finished its turn and is waiting for a human
 //                       to say something next. A message IS that human turn.
 //                       Proven on this machine 2026-08-16: a message written
-//                       to a live session's socket arrived, was read as her
-//                       turn, and the agent went back to work.
+//                       to a live session's socket arrived, was read as the
+//                       human turn, and the agent went back to work.
 //
 //   "permission prompt" the agent is frozen on a box asking to approve a tool
 //                       call. A message queues BEHIND that box. Sending one
 //                       would look like it worked and change nothing, which is
 //                       the failure this codebase cares about most: the system
-//                       swallowing something she said.
+//                       swallowing something the user said.
 //
 // So a reply box appears on the first and never on the second, and the second
 // says out loud that it has to be answered where it is running.
@@ -105,7 +103,7 @@ export function replyReaches(agent) {
 // there was nothing there to answer. That sentence was wrong.
 //
 // MEASURED 2026-08-17, not reasoned: a throwaway session was left sitting at
-// its prompt with nothing asked — the exact state of the card she sent — and
+// its prompt with nothing asked, the exact state of the card in question, and
 // the same line `reply` writes was written into its socket. It arrived, the
 // session read it and went back to work and answered it. An idle session is
 // listening; idle is what a session at its prompt IS.
@@ -142,12 +140,12 @@ export function replyIsSwallowed(agent) {
 // because a timer here ran out.
 //
 // The comparison is `>`, against the stamp and not the status alone, because
-// the session is still idle for the moment or two between her pressing send and
-// it picking the message up. Reading the status alone would send the row
-// straight back to the inbox, which is the bug she reported wearing a hat.
+// the session is still idle for the moment or two between the user pressing
+// send and it picking the message up. Reading the status alone would send the
+// row straight back to the inbox, which is the original bug wearing a hat.
 //
 // AND THE ONE SESSION THIS CANNOT PROMISE ANYTHING ABOUT: one that publishes no
-// status at all (1 of her 16, an older CLI). Agentbox cannot see that one work
+// status at all (an older CLI). Agentbox cannot see that one work
 // and cannot see it stop, so it is not moved anywhere and the reply is still
 // delivered. A promise that could never be kept is worse than no promise.
 export function tookHerReply(agent) {
@@ -193,7 +191,7 @@ export function agentKey(agent) {
   return `pid:${agent?.pid ?? 0}:${agent?.startedAt ?? 0}`;
 }
 
-// The moment she said she would deal with it. A past moment is not a deferral:
+// The moment the user said they would deal with it. A past moment is not a deferral:
 // once it passes the row is back, which is the same predicate rule work items
 // follow. So a missed one comes back late rather than being lost, and nothing
 // has to fire at 8am.
@@ -214,7 +212,7 @@ export function putOff(agent, now = Date.now()) {
 // session exists. WHAT THIS COSTS, stated rather than hidden: a session she
 // closes while it is working will not return to her inbox when it later stops
 // and asks something. That is the same sentence read the other way, and it is
-// the one she wrote.
+// the one that was chosen.
 //
 // "UNLESS ASKED OTHERWISE" IS THE UNDO, and it is why this stays a number in
 // the file instead of becoming a boolean: `close(key, 0)` clears it, which is
@@ -229,8 +227,8 @@ export function putAway(agent) {
 }
 
 /* -------------------------------- the words ------------------------------ */
-// Plain sentences, no jargon, no metaphor (hers, 2026-08-16), and the first
-// line of the body is the one thing she has to do about it, in bold, one
+// Plain sentences, no jargon, no metaphor, and the first line of the body is
+// the one thing the user has to do about it, in bold, one
 // sentence, under fifteen words (instructions.md). The row clips at
 // SUMMARY_BUDGET = 112 characters on the last full stop inside it, so that
 // sentence has to carry the whole point on its own.
@@ -260,7 +258,7 @@ export function whereItRuns(agent) {
 // goes because a card is not a diff viewer.
 //
 // Split out from `oneSentence` when `howItEnded` needed the same cleaning from
-// the other end of the message. One copy, so a quote of hers and a quote of its
+// the other end of the message. One copy, so a quote of the user's and a quote of its
 // answer can never be tidied by two different rules.
 function readableWords(raw) {
   return String(raw ?? '')
@@ -331,26 +329,25 @@ function saidWhen(agent, now) {
   return `**It answered ${when}:**`;
 }
 
-// THE LAST THING SHE TYPED INTO IT. Read straight off the session's own
-// `last-prompt` line, so it is her turn and never a tool result wearing a user
+// THE LAST THING THE USER TYPED INTO IT. Read straight off the session's own
+// `last-prompt` line, so it is the user's turn and never a tool result wearing a user
 // message's clothes.
 export function lastAsk(agent, budget = 180) {
   return oneSentence(agent.lastAsked, budget);
 }
 
 /* ------------------------------- what it IS ------------------------------ */
-// (hers), about a card whose loudest word was `session-71`. A session name is a
+// A card whose loudest word is `session-71` says nothing. A session name is a
 // handle, not a memory.
 //
 // Every Claude Code session writes a one-line title of ITSELF into its own
-// transcript and keeps it current. Measured across her machine 2026-08-17: 14
-// of her 14 outside sessions had one, and session-71's was "Agentbox product not
-// displaying in the app" — the sentence she said she could not remember, three
-// days old, sitting in a file Agentbox was already reading and throwing away.
+// transcript and keeps it current. Every outside session measured had one, and
+// it is usually the very sentence a person would use to recall the work,
+// sitting in a file Agentbox was already reading and throwing away.
 //
 // So the title of the row is what the work IS, with the session's name in front
-// of it because she has two of them running in the same folder and the name is
-// how she tells them apart. When a session has no title of its own the row says
+// of it because two sessions can run in the same folder and the name is how
+// they are told apart. When a session has no title of its own the row says
 // what it used to say, which is better than a blank.
 export function whatItIs(agent) {
   return String(agent?.about ?? '').replace(/\s+/g, ' ').trim();
@@ -361,57 +358,56 @@ export function agentTitle(agent, now = Date.now()) {
   if (about) return `${agent.name}: ${about}`;
   if (replyReaches(agent)) return `${agent.name} is waiting for you`;
   if (asksSomething(agent)) return `${agent.name} needs you where it is running`;
-  // NOT "QUIET" ONCE SHE HAS SPOKEN TO IT. Without this the row she just
+  // NOT "QUIET" ONCE THE USER HAS SPOKEN TO IT. Without this the row just
   // replied to sat in In progress under a heading saying it had been quiet for
-  // three days, which is the same sentence it wore before she said anything.
+  // three days, which is the same sentence it wore before anything was said.
   if (tookHerReply(agent)) return `${agent.name} is working on what you told it`;
   return `${agent.name} has been quiet for ${howLong(now - (agent.lastActiveAt ?? agent.startedAt ?? now))}`;
 }
 
 /* ------------------------------ RECALLING IT ----------------------------- */
-// Hers, 2026-08-17, about a card that already carried the title and the last
-// thing she typed.
+// A card that carries only the title and the last thing typed is not enough to
+// recall a session.
 //
 // WHAT WAS MISSING WAS THE BEGINNING, and it is the one thing on a transcript
-// that never changes. Measured over all 16 of her live sessions on 2026-08-17:
-// her FIRST message is the ask in 16 of 16, and no card had ever shown it.
-// `last-prompt` is the LAST thing she typed, and five days into a session that
-// is "okay no worries. just make sure that auth persists across sessions" —
-// perfectly true, and no help whatsoever in remembering what the thing is for.
+// that never changes. In every live session measured, the FIRST message was
+// the ask, and no card had ever shown it. `last-prompt` is the LAST thing the
+// user typed, and days into a session that is usually a short follow-up that
+// is perfectly true and no help whatsoever in remembering what the thing is for.
 //
-// Her side of a conversation is also small enough to just print: 155 turns
-// across 16 sessions, median 6 per session, median 131 characters each. The
-// megabytes in a transcript are the agent's half, not hers. So the recall is
-// her own words, read off the file, and no model sees any of it.
+// The human side of a conversation is also small enough to just print: a
+// handful of turns per session, a sentence or two each. The megabytes in a
+// transcript are the agent's half. So the recall is the user's own words, read
+// off the file, and no model sees any of it.
 //
 // ONE SHAPE, NOT THREE, AND IT IS NOT CONFIGURABLE.
 //
-// So the card does the same thing on every session: the message she started it
-// with, up to three later messages of hers, where it stopped, and where it is
-// working. `ask` and `trail` are gone, and there is deliberately no setting for
-// this — deciding per session which of them a card deserves is exactly the
-// judgement she said she did not want made, whether by a model or by a knob.
+// So the card does the same thing on every session: the message the user
+// started it with, up to three later messages of theirs, where it stopped, and
+// where it is working. `ask` and `trail` are gone, and there is deliberately no
+// setting for this: deciding per session which of them a card deserves is a
+// judgement that should not be made, whether by a model or by a knob.
 
-// The messages she typed, oldest first, with the newest ones kept whole and the
+// The messages the user typed, oldest first, with the newest ones kept whole and the
 // opening always present.
 //
 // AN EMPTY LIST IS NOT A FALLBACK TO `lastAsked`, and the difference is the
 // whole point of this change rather than a nicety. A session whose transcript
-// could not be read has exactly one thing she typed on record, and it is the
-// LAST one. So the caller is told which of the two it has. WHAT SHE SAID FROM
-// AGENTBOX IS ALSO WHAT SHE SAID.
+// could not be read has exactly one thing the user typed on record, and it is
+// the LAST one. So the caller is told which of the two it has. WHAT THE USER
+// SAID FROM AGENTBOX IS ALSO WHAT THE USER SAID.
 //
-// So the card went on saying only what she started the session with.
+// So the card went on saying only what the session was started with.
 //
 // `spoke` is the other half, written by main/agent-schedule.mjs at the moment
 // of delivery. It is a RECORD, not a guess: Agentbox does not try to work out
-// which wrapped peer message in a transcript was hers, because another of her
-// sessions pinging this one is a real peer and drawing that as her words would
-// put a sentence she never typed on the one card built to be trusted.
+// which wrapped peer message in a transcript was the user's, because another of
+// their sessions pinging this one is a real peer and drawing that as the user's
+// words would put a sentence they never typed on the one card built to be trusted.
 //
 // Merged by time, so the thread reads forwards however it arrived, and deduped
-// on the text because a session that DOES record her injected turn as its own
-// (a future Claude Code, or one she typed into directly) must not show it
+// on the text because a session that DOES record the user's injected turn as
+// its own (a future Claude Code, or one typed into directly) must not show it
 // twice.
 export function herWords(agent) {
   const asked = (agent?.asked ?? []).filter((t) => t && t.text);
@@ -434,11 +430,11 @@ export function herWords(agent) {
   return first ? [first, ...rest] : [];
 }
 
-// WHICH OF HER MESSAGES ACTUALLY RECALL ANYTHING, and the cheapest honest
-// answer is how long they are. Half of what she types while an agent works is
-// driving it, not describing it: measured across her 155 real turns, "restart
-// it", "move forward", "lgtm!", "copy it to clipboard", "oh that works got it"
-// and "open again" are all under sixty characters, and her median turn is 131.
+// WHICH OF THE USER'S MESSAGES ACTUALLY RECALL ANYTHING, and the cheapest
+// honest answer is how long they are. Much of what a person types while an
+// agent works is driving it, not describing it: short nudges to restart,
+// carry on or approve are almost always under sixty characters, while a turn
+// that describes the work typically runs well past a hundred.
 //
 // So the long ones are preferred, and the short ones are still there when
 // there is nothing longer, because a card that drops to silence is worse.
@@ -459,7 +455,7 @@ function ago(at, now) {
   return `${howLong(gap)} ago`;
 }
 
-// The rest of the context, in her sentences: what she asked for, where the
+// The rest of the context, in the user's sentences: what they asked for, where the
 // thread got to, what it last said back, and what it has had its hands on.
 function context(agent, now = Date.now()) {
   const words = herWords(agent);
@@ -472,13 +468,13 @@ function context(agent, now = Date.now()) {
     const when = ago(opening.at, now);
     lines.push(`**You started it${when ? ` ${when}` : ''} with:**\n\n“${oneSentence(opening.text, 420)}”`);
   } else {
-    // No history, so the only thing on record is the LAST thing she typed, and
+    // No history, so the only thing on record is the LAST thing the user typed, and
     // it gets the label that is true of it.
     const last = lastAsk(agent);
     if (last) lines.push(`**The last thing you told it:**\n\n“${last}”`);
   }
 
-  // Everything else she typed, oldest first, so the thread reads forwards.
+  // Everything else the user typed, oldest first, so the thread reads forwards.
   // Three of them; more than that is the transcript rather than a card.
   if (rest.length) {
     const recent = worthRecalling(rest).slice(-3);
@@ -586,10 +582,10 @@ export function reachesInbox(agent, now = Date.now(), mode = 'all') {
 // argument is not taken because a reply cancels a deferral (`replyClearsSchedule`
 // does the same for work items) — she spoke to it, so it is not put off any more.
 //
-// THIS IS NOT `reachesProgress`, WHICH SHE KILLED, and the name is different on
-// purpose. It stays dead: a working session she has not spoken to is in her
-// inbox, exactly as she left it. What moves a row here is HER, and only her —
-// the reply she wrote.
+// THIS IS NOT `reachesProgress`, WHICH WAS REMOVED, and the name is different
+// on purpose. It stays dead: a working session the user has not spoken to is in
+// the inbox, exactly as they left it. What moves a row here is THE USER, and
+// only the user: the reply they wrote.
 export function progressAfterReply(agent, now = Date.now(), mode = 'all') {
   if (agent.startedByZero) return false;
   if (mode === 'off') return false;
@@ -603,7 +599,7 @@ export function listed(agent) {
 }
 
 /* --------------------- ACTIVE AGENTS, IN THE SIDEBAR --------------------- */
-// Then her pick of the design at 18:17: one line per session in its own words,
+// The design: one line per session in its own words,
 // the clock on the right, and no dot, mark, colour, wash, edge or line of any
 // kind.
 //
@@ -611,8 +607,8 @@ export function listed(agent) {
 // where the rule lives, because it decides what the rule can be: nothing
 // FINISHED is ever on this list and never has been. `main/agents.mjs` drops any
 // record whose process is gone, so a session that finishes exits and disappears
-// by itself. Measured on her machine that evening, ten sessions alive and six
-// of them her own terminals sitting at a prompt for between two and seven days.
+// by itself. Measured: most live sessions were terminals sitting at a prompt
+// for between two and seven days.
 // So length comes from sessions that are alive and forgotten, and a day is
 // where the app's own clock (`format.ts`) stops saying hours and starts saying
 // `1d`. The panel therefore holds exactly what the clock beside each row can
@@ -649,21 +645,19 @@ export function byRecency(a, b) {
 }
 
 /* --------------------------- THE CONVERSATION ---------------------------- */
-// Hers, 2026-08-17. Her "go ahead" on the same row, an hour later.
-//
-// THE CARD IS THE RECALL AND THIS IS THE REST OF IT. The card is drawn for her
-// whether she asked or not, so it is four sentences; this is only ever drawn
-// because she pressed something, so it can be the conversation.
+// THE CARD IS THE RECALL AND THIS IS THE REST OF IT. The card is drawn for the
+// user whether they asked or not, so it is four sentences; this is only ever
+// drawn because they pressed something, so it can be the conversation.
 //
-// STILL NO MODEL, AND NOW NO COST AT ALL UNTIL SHE PRESSES IT. Measured on her
-// machine 2026-08-17: the readable conversation is 0.6% of a transcript's
-// bytes, and the worst single file on the disk — 160MB — carries 3,800 readable
-// turns, 2.6MB of text, 729ms to pull out. That last number is why the read is
-// streamed and never happens on a draw.
+// STILL NO MODEL, AND NOW NO COST AT ALL UNTIL IT IS PRESSED. Measured: the
+// readable conversation is 0.6% of a transcript's bytes, and the worst single
+// file measured (160MB) carries 3,800 readable turns, 2.6MB of text, 729ms to
+// pull out. That last number is why the read is streamed and never happens on
+// a draw.
 //
 // WHY IT IS A WINDOW AND NOT THE WHOLE FILE. 3,800 turns is not a conversation
-// she can get up to speed on, it is a scroll bar. So it is the opening, which
-// is the ask in 16 of her 16 sessions, and the end, which is where it got to,
+// anyone can get up to speed on, it is a scroll bar. So it is the opening,
+// which is the ask in every session measured, and the end, which is where it got to,
 // and one plain line saying how many are in between rather than pretending
 // there are none.
 export const TRAIL_OPENING = 3;
@@ -681,12 +675,11 @@ export function conversationWindow(turns, { opening = TRAIL_OPENING, keep = TRAI
 // because "some messages" is the kind of sentence that makes her wonder what
 // else the app is rounding off.
 //
-// She is right and it is not rare. Measured over her own Agentbox store the same
-// day, rebuilding every row's thread the way the pane draws it: 267 rows have a
-// conversation, 123 of them hide part of it, and 97 hide messages SHE wrote.
-// 550 of her own messages were behind this line, and the line was a plain div
-// with nothing to press. "Not shown" was true and it was also the end of the
-// road, so a thread that had eaten her follow-up simply said so and stopped.
+// And it is not rare. Rebuilding every row's thread the way the pane draws it,
+// nearly half the rows with a conversation hide part of it, many of them
+// hiding messages the user wrote, and the line was a plain div with nothing to
+// press. "Not shown" was true and it was also the end of the road, so a thread
+// that had eaten a follow-up simply said so and stopped.
 //
 // So the words say what pressing does. The window itself is untouched: it still
 // opens on the end of a long conversation, because an 18,100px page is the
@@ -700,17 +693,17 @@ export function conversationGap(omitted) {
 // So the item is the conversation, and each thing the agent ran sits on its own
 // quiet line between the messages, in the order it happened. This half of the
 // file decides what one of those lines SAYS. What it looks like is the frosted
-// treatment she picked in round two and lives in the stylesheet.
+// treatment chosen in round two and lives in the stylesheet.
 //
-// WHY IT IS BOUNDED THREE WAYS, all measured over the 40 largest transcripts on
-// her machine, 2026-08-19:
+// WHY IT IS BOUNDED THREE WAYS, all measured over the 40 largest transcripts
+// available:
 //
 //   * one session held 6,070 tool calls and 8MB of output. So output is capped
 //     per line (WORK_CHARS) rather than sent whole.
 //   * the longest unbroken run of tool calls between two messages was 111, and
 //     the median session's longest run was 25. So a run is capped (WORK_RUN)
 //     and says how many it is not showing, because 111 quiet lines standing
-//     between her question and its answer is her original complaint wearing a
+//     between a question and its answer is the original problem wearing a
 //     different hat.
 //   * a windowed thread of 40 messages could still carry thousands of work
 //     lines, so the whole thread is capped too (WORK_TOTAL), oldest first.
@@ -723,12 +716,12 @@ export const WORK_RUN = 20;
 export const WORK_TOTAL = 200;
 
 // WHAT A TOOL CALL SAYS lives in its own file now (`shared/work-lines.mjs`),
-// because her 2026-08-20 report on the imported threads turned one rule into
+// because a report on the imported threads turned one rule into
 // three: the verb, the subject and the fold. It is re-exported here so that
 // nothing that already reads this file has to learn a second import.
 export {
-  workVerb, workSubject, fullSubject, shortPath, plainCommand,
-  groupWork, runSummary, runFailures, RUN_MIN,
+  workVerb, workSubject, fullSubject, shortPath, plainCommand, commandWork,
+  groupWork, runSummary, runFailures, RUN_MIN, isBookkeeping,
   changedFile, fileInChange, CHANGES_A_FILE,
 } from './work-lines.mjs';
 
@@ -755,8 +748,8 @@ export function outputCut(shownLines, allLines) {
 //
 // `whole` IS WHAT THE GAP LINE PRESSES. Every message stands, and nothing else
 // changes: the work is still capped by `capRuns` below, because 530 tool calls
-// is not a conversation and she asked for her follow-ups, not for the output
-// under them. Opening it is her decision and it lasts until she leaves the row,
+// is not a conversation and what is wanted is the follow-ups, not the output
+// under them. Opening it is the user's decision and it lasts until they leave the row,
 // so no thread is ever born at this size.
 export function threadWindow(events, { opening = TRAIL_OPENING, keep = TRAIL_TURNS, whole = false } = {}) {
   const all = (events ?? []).filter((e) => e && (e.kind === 'work' ? true : !!e.text));
@@ -884,15 +877,14 @@ export function saidCount(events) {
 // A provider writing a tool call sometimes emits its closing tags as ordinary
 // text, and the field it was writing then holds the answer with the machinery
 // of the call still stuck to the end. On w-b108b1d596 the result that reached
-// her pane ended "7,369 tests both times.</result>\n</invoke>" and she read it.
-// Measured across her store, 2026-09-23: 49 field writes on 27 rows carry it,
-// and 50 messages on screen.
+// the pane ended "7,369 tests both times.</result>\n</invoke>" and was shown as
+// is. Measured: dozens of field writes across dozens of rows carried it.
 //
 // IT ALSO BREAKS THE FOLD THAT SAYS ONE THING ONCE. That run noticed the leak
 // and wrote its result again, clean. The fold keeps the FULLER of two copies of
 // one answer, and the junk made the broken copy the fuller one, so the leak was
 // what stayed on the screen and the good rewrite was the copy thrown away. That
-// is the row she photographed, and it is why the cut happens before anything
+// is what happened on that row, and it is why the cut happens before anything
 // compares two messages.
 //
 // The cut runs from the first tag to the end, because nothing after one is

package/shared/analytics-events.mjs

@@ -25,6 +25,15 @@ export const EVENTS = {
   task_opened: 'A task was opened',
   reply_sent: 'A reply was sent',
   task_finished: 'A task finished',
+  // REAL USE, NOT ONLY THE WALKTHROUGH (2026-10-06). Every "task finished" on
+  // the day downloads opened was somebody closing practice rows in setup; there
+  // was no count of an agent doing real work, of where setup was left, or of an
+  // install being used on a day, which is what retention is read from.
+  day_active: `${Name} was used today`,
+  first_run_step: 'A setup step was reached',
+  task_written: 'A task was written',
+  run_started: 'An agent started work',
+  run_finished: 'An agent stopped work',
 };
 
 export const EVENT_NAMES = Object.keys(EVENTS);
@@ -39,11 +48,15 @@ export const ALLOWED_PROPS = new Set([
   'count',          // how many of a thing, never which ones
   'kind',           // -> KINDS below, an enum and nothing else
   'fromAgent',      // whether an agent or the founder did it
+  'failed',         // whether an agent's run ended in failure
+  'practice',       // whether it happened in setup's practice project
+  'engine',         // -> ENGINES below, which coding agent ran
 ]);
 
-// `kind` is the one property that is not a number, so it is a closed list. A
-// value outside it is dropped, not passed through.
+// `kind` and `engine` are the properties that are not numbers, so each is a
+// closed list. A value outside it is dropped, not passed through.
 export const KINDS = new Set(['task', 'question', 'review', 'directive', 'agent', 'digest']);
+export const ENGINES = new Set(['claude', 'codex']);
 
 // Refuse an event nobody approved; drop a property nobody approved. Returns the
 // payload that may be sent, or null when the event itself is not one of hers.
@@ -56,6 +69,10 @@ export function sanitize(name, props = {}) {
       if (typeof value === 'string' && KINDS.has(value)) out.kind = value;
       continue;
     }
+    if (key === 'engine') {
+      if (typeof value === 'string' && ENGINES.has(value)) out.engine = value;
+      continue;
+    }
     if (typeof value === 'number' && Number.isFinite(value)) out[key] = value;
     else if (typeof value === 'boolean') out[key] = value;
   }

package/shared/answers.mjs

@@ -78,3 +78,15 @@ export function answerSettled(item) {
 export function answerTs(item) {
   return item?.wrote?.answer?.ts ?? 0;
 }
+
+// SHE STOPPED THIS ROW AND HAS NOT SPOKEN SINCE. Stop writes `blocked` in her
+// hand (zero:stop-session), and it promises the row stays in her inbox until
+// she replies, resumes it or sends it back. A reply she wrote BEFORE the stop
+// is not one of those, though a kill hands it back to the queue: that is how a
+// stopped run came straight back ten seconds later (2026-10-01).
+// tests/a-stopped-agent-stays-stopped-until-she-resumes-it.test.mjs
+export function stoppedByHer(item) {
+  const status = item?.wrote?.status;
+  return item?.status === 'blocked' && status?.source === 'founder'
+    && answerTs(item) <= (status.ts ?? 0);
+}

package/shared/bridge-map.d.mts

@@ -0,0 +1,12 @@
+// Types for shared/bridge-map.mjs, for the window side.
+//
+// EVERY ONE OF THESE IS A PHONE BOOK AND IS TYPED AS ONE. Naming the hundred
+// and thirty keys over again here would be a second copy of the list the file
+// exists to be the only copy of, and the first one to fall behind it. What the
+// screen needs from a type is that a channel is a string and a wrap is a list
+// of argument names; which names exist is checked against preload.cjs at test
+// time instead (tests/both-front-doors-offer-the-same-bridge.test.mjs).
+export declare const REQUEST_CHANNELS: Readonly<Record<string, string>>;
+export declare const PUSH_CHANNELS: Readonly<Record<string, string>>;
+export declare const WRAPPED_ARGS: Readonly<Record<string, string[]>>;
+export declare const DESKTOP_ONLY: readonly string[];

package/shared/bridge-map.mjs

@@ -13,7 +13,10 @@
 /** Asked, and the screen waits for the answer. */
 export const REQUEST_CHANNELS = {
   terminal: 'zero:terminal',
+  agentUpdate: 'zero:agent-update',
   snapshot: 'zero:snapshot',
+  // The next page of old finished threads, at the foot of Done and All.
+  olderItems: 'zero:older-items',
   dashboard: 'zero:dashboard',
   commandCatalog: 'zero:command-catalog',
   remoteControl: 'zero:remote-control',
@@ -21,8 +24,32 @@ export const REQUEST_CHANNELS = {
   compact: 'zero:compact',
   compactionStatus: 'zero:compaction-status',
   answer: 'zero:answer',
+  sendNow: 'zero:send-now',
   compose: 'zero:compose',
   schedule: 'zero:schedule',
+  // Feedback to the Agentbox team, from the sidebar's Feedback card.
+  sendFeedback: 'zero:send-feedback',
+  // The team version: signing in, the team, sharing, routing a given task.
+  teamSignIn: 'zero:team-sign-in',
+  teamSignInCancel: 'zero:team-sign-in-cancel',
+  teamSignInReopen: 'zero:team-sign-in-reopen',
+  teamSignOut: 'zero:team-sign-out',
+  teamSignInEmail: 'zero:team-sign-in-email',
+  teamSignUp: 'zero:team-sign-up',
+  teamCreate: 'zero:team-create',
+  teamInvite: 'zero:team-invite',
+  teamRename: 'zero:team-rename',
+  teamRemoveMember: 'zero:team-remove-member',
+  teamLeave: 'zero:team-leave',
+  teamCancelInvite: 'zero:team-cancel-invite',
+  teamAcceptInvite: 'zero:team-accept-invite',
+  teamStatus: 'zero:team-status',
+  teamShare: 'zero:team-share',
+  teamSync: 'zero:team-sync',
+  teamRoute: 'zero:team-route',
+  teamReact: 'zero:team-react',
+  teamMessage: 'zero:team-message',
+  threadEdit: 'zero:thread-edit',
   repeats: 'zero:repeats',
   composeRepeat: 'zero:compose-repeat',
   setRepeat: 'zero:set-repeat',
@@ -50,6 +77,7 @@ export const REQUEST_CHANNELS = {
   updateInstall: 'zero:update-install',
   notify: 'zero:notify',
   stopSession: 'zero:stop-session',
+  runNow: 'zero:run-now',
   reopen: 'zero:reopen',
   instructionRead: 'zero:instruction-read',
   instructionWrite: 'zero:instruction-write',
@@ -62,11 +90,14 @@ export const REQUEST_CHANNELS = {
   settingsRead: 'zero:settings-read',
   claudeRecheck: 'zero:claude-recheck',
   codexRecheck: 'zero:codex-recheck',
+  engineSetup: 'zero:engine-setup',
   codexAddAccount: 'zero:codex-add-account',
   claudeAddAccount: 'zero:claude-add-account',
   setProjectSetting: 'zero:settings-set-project',
   setWorkspaceSetting: 'zero:settings-set-workspace',
   projectRename: 'zero:project-rename',
+  projectArchive: 'zero:project-archive',
+  projectSeenBy: 'zero:project-seen-by',
   projectIcon: 'zero:project-icon',
   projectIconClear: 'zero:project-icon-clear',
   projectInstructionsRead: 'zero:project-instructions-read',
@@ -78,6 +109,7 @@ export const REQUEST_CHANNELS = {
   sessionTrace: 'zero:session-trace',
   itemHistory: 'zero:item-history',
   openArtifact: 'zero:open-artifact',
+  folderPictures: 'zero:folder-pictures',
   readDoc: 'zero:read-doc',
   codeChange: 'zero:code-change',
   codeFile: 'zero:code-file',
@@ -125,4 +157,8 @@ export const WRAPPED_ARGS = {
 // Electron can tell you the real path of a file somebody dropped onto the
 // window. A browser cannot, by design, and no server can answer it either, so
 // this one is absent there rather than wrong. The screen already reads null.
-export const DESKTOP_ONLY = ['pathForFile'];
+//
+// `onWriteHeld` is the desktop's ⌘R asking the page to write what the undo
+// window holds before it reloads (main/write-before-reload.mjs). A browser
+// reload asks nobody; the page writes on `pagehide` there instead.
+export const DESKTOP_ONLY = ['pathForFile', 'onWriteHeld'];

package/shared/claude-commands.generated.mjs

@@ -10,8 +10,8 @@
 // build time, rather than typing them into a file, is the only way the list
 // cannot rot quietly.
 
-export const READ_FROM = "2.1.283";
-export const READ_AT = "2026-09-29";
+export const READ_FROM = "2.1.289";
+export const READ_AT = "2026-10-07";
 export const CLAUDE_COMMANDS = [
   {
     "name": "model",

package/shared/claude-models.generated.mjs

@@ -11,14 +11,14 @@
 // number typed into a file of ours would look authoritative while being a
 // guess. Running an old model by mistake is the failure being avoided.
 
-export const READ_FROM = "2.1.283";
-export const READ_AT = "2026-09-29";
+export const READ_FROM = "2.1.289";
+export const READ_AT = "2026-10-07";
 
 export const CLAUDE_MODELS = [
   {"alias":"opus","id":"claude-opus-5-5","label":"Opus 5.5","defaultLevel":"medium"},
   {"alias":"claude-opus-5","id":"claude-opus-5","label":"Opus 5","defaultLevel":"high"},
-  {"alias":"sonnet","id":"claude-sonnet-5","label":"Sonnet 5","defaultLevel":"high"},
-  {"alias":"claude-sonnet-4-6","id":"claude-sonnet-4-6","label":"Sonnet 4.6","defaultLevel":null},
+  {"alias":"sonnet","id":"claude-sonnet-5-5","label":"Sonnet 5.5","defaultLevel":"medium"},
+  {"alias":"claude-sonnet-5","id":"claude-sonnet-5","label":"Sonnet 5","defaultLevel":"high"},
   {"alias":"haiku","id":"claude-haiku-4-5","label":"Haiku 4.5","defaultLevel":null},
   {"alias":"claude-3-5-haiku","id":"claude-3-5-haiku","label":"Haiku 3.5","defaultLevel":null},
   {"alias":"fable","id":"claude-fable-5-1","label":"Fable 5.1","defaultLevel":"high"},