You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.
8000
You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
New agents never start on first boot: --resume <name> opens a picker, and the session is never named #23
boot-agents.sh runs claude --resume <name> || claude. On a brand-new agent --resume does not fail; it opens an interactive "No sessions match" picker, so the || claude fallback never runs. Even when it does, the session has no name until the user runs /rename <name> by hand, which is what later resumes depend on. The script's own comment assumes --resume exits non-zero; with current Claude Code it does not.
Evidence
Seen in test: two freshly created agents both got stuck at the picker; the base README notes the rename gap and create-agent.sh does not close it; run log rows "boot-agents with a real CLI" and "New agent" cover the same failure.
Fix
Pin a session id per agent: if ~/agents/<name>/.session-id exists, claude --resume <id>; otherwise generate a UUID, write it, and launch claude --session-id <id> -n <name>. Decide behaviour when the pinned session's transcript is gone (should start a fresh named session, not the picker; needs testing). Optional migration: look up existing named sessions once and write .session-id. Update the stale comment in boot-agents.sh and the base README.
Acceptance criteria
On a clean machine a newly created agent boots to a ready prompt with its name on the prompt border, no /rename and no picker.
A second boot-agents.sh run after tmux kill-server resumes the same session.
boot-agents.test.sh covers both paths plus the missing-transcript case.
Activity
New agents never start on first boot: --resume <name> opens a picker,…