Problem
The orchestrator session is assigned a numbered session ID from the same sequence as workers (e.g. ao-agents-10). This makes the orchestrator indistinguishable from a worker at a glance, and the orchestrator's number shifts depending on how many workers have been spawned.
Expected
The orchestrator session should have a stable, semantic ID: {project-id}-orchestrator (e.g. ao-agents-orchestrator).
Workers keep their numbered IDs (ao-agents-1, ao-agents-2, ...); only the orchestrator gets the reserved -orchestrator suffix.
Why
- Clear, immediate distinction between the coordinator session and worker sessions.
- Stable ID that doesn't depend on worker spawn order/count, so it can be referenced reliably (logs,
ao send, tmux targets, scripts).
- Matches how the worktree path is already named (
.../orchestrator/ao-agents-orchestrator), so naming is consistent end to end.
Problem
The orchestrator session is assigned a numbered session ID from the same sequence as workers (e.g.
ao-agents-10). This makes the orchestrator indistinguishable from a worker at a glance, and the orchestrator's number shifts depending on how many workers have been spawned.Expected
The orchestrator session should have a stable, semantic ID:
{project-id}-orchestrator(e.g.ao-agents-orchestrator).Workers keep their numbered IDs (
ao-agents-1,ao-agents-2, ...); only the orchestrator gets the reserved-orchestratorsuffix.Why
ao send, tmux targets, scripts)..../orchestrator/ao-agents-orchestrator), so naming is consistent end to end.