# Rationale — "How do you keep track of multiple coding agents?"

FRE-199 item 1, page 1 of the second pair. Drafted 2026-11-05 by CMO (internal
target Mon 2026-11-09, beaten by four days — the backlog held, so drafting
early cost nothing).

## The phrase

Primary: **"how do you keep track of multiple coding agents running in
parallel"** (variants: "how many sessions before you become the bottleneck",
"which agent is waiting", "agent tracking dashboard").

## Why this phrase won the slot

- **Strongest recurrence in the backlog.** Seven independent threads across
  nine scans state the multi-agent attention problem in their own words — more
  than any other cluster after the pair-1 phrases. It is the natural next page:
  the pair-1 pages answer *one* agent's silence (done-signal) and *one*
  permission wait (waiting-on-permission); this is the fleet-scale version of
  the same pain, and the buyers are already at fleet scale.
- **Buying intent.** Every quoting operator is running multiple agents *now*
  and losing time to supervision, not exploring.
- **Answerable honestly, generically.** The mechanism (per-session hook events
  with `session_id`, typed notifications, the status line) is documented in the
  agent's own reference; every claim traces to it. No product needed.
- **Distinct from pair 1.** Done-signal owns "one agent, is it finished";
  waiting-on-permission owns "one agent, why is it blocked". This page owns
  "several agents, which one needs me" — the phrase, the evidence, and the
  mechanism (typed Notification matchers, `session_id`, status line) do not
  overlap pair 1's.

## Evidence trail

| Thread | Date | What it showed |
|---|---|---|
| r/ClaudeAI 1xmzp2n — "How do you keep track of multiple coding agents running in parallel?" | 2026-11-03 | The exact question as a fresh thread: "How do you notice when one is waiting, done, or stuck?"; two commenters independently: agents "sat waiting on a permission prompt while I was deep in the third", idle "long enough that I lost the thread of what I had asked it to do" |
| r/ClaudeCode 1xh5cum — "Four months of 50+ parallel agent threads a day" | 2026-10-27 | "The limit moved from tokens to my attention"; "fifty a day add up to something I could feel by Friday" |
| r/ClaudeCode 1xdjb2g — "How many sessions can you run before you become the bottleneck?" | 2026-10-23 | 72 comments; the thread went to compute and left the attention half open |
| r/ClaudeCode 1xipsk0 — "~40 Claude Code agents unattended for a month" | 2026-10-29 | "The six hours of silence was the real problem, not the dialog itself" |
| r/ClaudeCode 1xk0ghj — "multiple agents working on multiple projects" | 2026-10-31 | "If every decision routes through you, you're the bottleneck agents were meant to eliminate" |
| Hacker News 50298436 (herdr launch) | 2026-10-30 | A 30-year tmux user's stated switch reason: "visual indication which agent is working and which is waiting for an input" — used in rationale only; the page does not name any tool |

All rows live in `drafts/listening.md` (The-Nook local master line, single
canonical copy per FRE-748) with URLs and verbatim quotes.

## Gates before this page ships

1. **Sponsor fact-check** of the claims table in `copy.md` (owner: Michael
   Freno). Page moves `drafts/` → `pending/` → `approved/` on his read, per
   the marketing tree's hard rule.
2. **CTO eyes on the agent-behaviour claims** — five doc-sourced claims
   (hooks reference ×4, statusline doc ×1), all re-read 2026-11-05. Routed to
   the CTO per the FRE-199 plan.
3. **Publish path:** `approved/` → a human places it on nook.freno.me.
   Nothing posts itself.

## Ban compliance (FRE-199 + positioning.md rule 1)

- The Nook: not named. The notch, the island, the companion: not mentioned.
- Competitors: not named. The herdr evidence is rationale-only; the page's
  "what to check" recommends no tool at all — states and wiring, not products.
- Claude Code is named only as the subject whose documented behaviour the page
  explains, with its own docs as the source — same status as pair 1.
- No superlatives, no benchmark numbers, no invented testimonials, no price,
  no roadmap dates. Anecdotes are real threads, described without handles.

## Cadence note

Second pair. Queue behind it: the run-without-asking cluster (same pair), the
fan-control phrase, and the invisible-permission variants — above the
three-candidate floor. Two a week holds.