Overseer worker titles (how a spawned worker is named)
When an Overseer spawns a worker session, that session is titled in one fixed shape — a category, the role, a never-repeating number and the task — so you can tell at a glance which Overseer started it and what it is for. Covers what the parts mean and why the number never restarts.
On this page
What it is
What it is — When an Overseer spawns a worker session
When an Overseer spawns a worker session, that session is titled for it, in one fixed shape:
[<Category>] <Role> <N>: <Task>
For example [Verdict] Fixer 1: Fix the flaky auth test, or [WT Lifecycle] Red Teamer 2: Attack the lander contract.
The point is the session list. An Overseer runs several workers at once and they all look alike — a wall of "Session 47"-ish rows tells you nothing about who sent them, what they are for, or which one you are looking at. The title answers all four questions at a glance:
[Category]— what the Overseer is managing, in its own one-or-two-word tag (Verdict,WT Lifecycle). It is what groups a crew together in the sidebar and separates it from everyone else's work.<Role>— the worker type's label, so it always matches what was actually asked for (Fixer,Auditor,Red Teamer, …).<N>— that role's running count under that Overseer: the 46th Fixer is numbered 46.<Task>— the job the Overseer wrote, shortened to fit.
Where to find it
The title appears on the spawned worker's own session row — in the session list, the inbox, and anywhere else that session is listed. There is no screen to open: the Overseer writes the title when it spawns the worker.
A worker belongs to its Overseer, so its row stays out of your Needs You and inbox while that Overseer is still live: the report goes to the Overseer, which answers it or passes it on to you. That holds past the half-hour point a routed card normally returns at — while the Overseer is there, the hold is renewed, and a worker whose own reply was addressed to you is handed to the Overseer too. The worker reaches your inbox once its Overseer is gone (switched off, deleted, no live session, or over its own spending breaker). So a row in Needs You is asking YOU; an Overseer's workers are visible under that Overseer in the sessions list. The same holds for a crew's helpers and foremen: while their crew lead is still there — even if it is only stopped — none of them appears in Needs You, in any Needs-You count, in a toast or on the dock badge, whatever state its row is in. The one exception is a permission request, which only you can click. A final the worker itself ended as a routine update is not handed on at all: it is parked quietly and costs its Overseer no turn, and it is only parked that way while the worker was not already holding something unread for you. Once the lead is archived or gone, its helpers come back within a minute.
A report the Overseer could not take still reaches you, as a card. A report or question reaches your inbox as a card ONLY when the hand-off to its Overseer did not land — the message was refused, or the delivery failed. Then you get one card per worker, titled Report from <worker> or Question from <worker>, carrying the worker's full message. A report the Overseer received raises no card: it is already being handled, and copying it to you would make your inbox a second reader of every report on the box. A newer undelivered report replaces the card in place, and the card clears itself once the worker is answered and carries on — so a card that stays is one nobody answered. Replying on the card sends your words to that Overseer, whichever of its sessions is running now. The setting is overseerWorkerReportCardsEnabled, on by default.
How it behaves
What you need to know
- The number never repeats, and it never resets. It comes from a stored counter per (Overseer, role), not a tally of the session rows — so archiving, deleting or retention-purging old workers cannot hand the same number out twice. "The 46th Fixer" always means one session.
- Numbering starts at 1 with no backfill. The worker type was never recorded on a session, so workers an Overseer ran before this shipped cannot be attributed to a role. Every (Overseer, role) pair begins at 1 and counts up cleanly from there.
- A title set this way is never rewritten. The AI auto-titler only acts on sessions still carrying a placeholder name, so a structured title is left alone.
- A gap is possible, a repeat is not. If a spawn fails after the number is handed out, that number is skipped. That is deliberate.
- Only Overseer spawns are affected. A cron spawn, an ordinary agent-driven spawn, and a session you start yourself keep exactly the naming they had.
Related
- overseers.md — the Overseer that spawns these workers and the fleet it runs.
- agent-status-board.md — the board where worker sessions show up.
Last verified 2026-10-14