parent_agent_id is null on all 336 registry records — list_agents(mine:true) returns 0 while ten of the lead's workers are live

[EtanHey]

A lead cannot see its own workers: parent_agent_id is null on EVERY record in the registry

Etan, 2026-08-19, watching ~10 live worker panes in one workspace: "List agents shows you 0 when there are actually, like, almost 10 of yours… What the actual fuck?"

Measured on this machine, same minute:

list_agents({mine:true})                            -> count: 0
list_agents({parent_agent_id:"cmuxlayerClaude"})    -> count: 0

registry on disk (~/.local/state/cmux-agents/**/*.json):
  total records                    336
  records with ANY parent_agent_id   0     <-- all 336 are parentless

Meanwhile six of this lead's workers have open PRs (#478 #483 #486 #487 #489 #494) and their panes are visible on screen. Every one of them was created by spawn_agent from this seat, and several spawn receipts returned parent_agent_id:"cmuxlayerClaude" at the time — the value is returned to the caller and then not persisted, or is dropped on the next reconcile/rewrite.

Why this is load-bearing, not cosmetic

• mine:true is the documented way a lead enumerates its workers. It returns nothing, so a lead has no tool-level answer to "what did I spawn?" — it must track PR numbers by hand, which is exactly the coordination the layer exists to provide (AGENTS.md: "orc, the leads, and the other workers know what each other are doing… without anyone opening a pane").
• Halt escalation walks the parent chain. nearestLiveHaltAncestor and the idle_without_done notification need a parent; with none stored, escalations have nowhere to go — which matches the fleet-wide inbox_monitor_not_alive and the "worker finished into silence" class this whole sprint is about.
• U6 (record the parent at spawn) is a ratified contract. The P12 evaluation already flagged one instance (parent_agent_id:null on a spawned child, attributed to caller resolution filtering a stale-done record — F1: one stale registry done state silently voids FOUR ratified contracts on the default path (U6, U8/#404, P11 closure, #378 guard) #457). This measurement shows it is not one instance: it is 336 of 336.
• It compounds renaming a pane mints a PHANTOM agent with an invented repo, and crash_recover respawns the pane when the operator closes it #493: parentless + title-derived identity is how phantom agents get minted and then respawn panes nobody asked for.

Asks

1. Persist parent_agent_id at spawn and preserve it across reconcile, repair, discovery and revive — a value returned in a receipt but absent from the record is the same class of lie this repo has been fixing all week.
2. Make mine:true / parent_agent_id filters work off that stored value, and add a regression test that spawns a child and asserts the parent is present AFTER a sweep (not only in the spawn receipt).
3. Backfill where derivable (surface lineage, spawn events) or state plainly that historical records cannot be attributed.
4. Cross-check with F1: one stale registry done state silently voids FOUR ratified contracts on the default path (U6, U8/#404, P11 closure, #378 guard) #457's caller-resolution fix: if the caller is resolved but the value is then dropped downstream, both halves need the test.

— cmuxlayerClaude (lead) · claude-code/claude-fable-5

[EtanHey]

Severity escalation: an unattributable agent made live changes to two machines

Live, 2026-08-19, on the same build. A brainlayerClaude pane was asked who spawned it. Its answer, verbatim from the pane:

"Who spawned me: I don't know, and I'm not going to guess. There's no spawn record in ~/.cmux/agents/brainlayerClaude-c0ccdbb7/ — just a contract file, an empty inbox, and a heartbeat, all stamped 21:29 today. The collab file is untracked in git, so there's no author to trace either. Best available inference: it came through cmuxlayer with an orchestrator-authored collab, so most likely orc — but that's inference, not evidence."

In that same session it: merged homebrew-layers#31, ran a live brew install --cask --force brainbar on both Macs, and opened brainlayer#729.

The operator approved the brew step by voice. But as that agent itself put it: "if the spawn itself wasn't yours, then you approved a live change from an agent you didn't authorize, which is a different problem and a real one."

That is the cost of this issue stated precisely. parent_agent_id: null on 336/336 records is not a missing column — it means a privileged action on the operator's machines cannot be traced to who initiated it. U6 exists for exactly this.

Raising the ask accordingly:
5. Treat spawn provenance as an audit record, not a convenience field: persist parent_agent_id AND the caller's identity/session at spawn, and make it survive reconcile/repair/discovery. An agent must be able to answer "who spawned me" from its own record, without inference.
6. Where provenance is genuinely unknown (adopted/discovered panes), say provenance: "unattributed" explicitly rather than leaving a null that reads like "no parent".

Related: #493 (renaming mints agents with invented identity), #492 (respawn without operator intent). Together they mean an agent can exist, act, and be unattributable — which is the trust boundary, not a UX nit.

— cmuxlayerClaude (lead) · claude-code/claude-fable-5