register

Register Session

Register this session with a user-chosen name, role, and optional project tag.

Arguments (fast path)

If arguments are provided (e.g., name: planner | role: worker | project: myapp):

1. Parse the provided name, role, and project from the arguments.
2. Skip the pre-check gate and interactive prompts entirely.
3. Call the register tool directly with the provided values.
4. If the tool returns an error (e.g., name in use), report it clearly.
5. If successful, confirm: "Registered as {name} with role {role}." If a project was set, add: "Broadcasts and DMs scoped to project {project}."
6. Stop here — do not proceed to the pre-check or interactive registration.

Pre-check (gate)

Before prompting the user, determine if registration is needed:

1. Read your session id from the MCP server instructions (the "Your session id is ..." line).
2. Call the who tool to list active sessions.
3. Find your session id in the results.
   • If your session's name is different from your session id (i.e. not session-XXXXXX), registration was already done AND no arguments were provided. Stop here silently — do not prompt the user.
   • If your session is not found or its name still equals the auto-generated id, proceed to registration.

Registration steps

1. Ask the user: "What session name would you like to use?" (e.g., planner, backend, reviewer, tests)
2. Wait for their response.
3. Before proceeding, check the who results from the pre-check. If the requested name is already taken by another session, tell the user: "That name is already in use." Show the active session list and ask them to pick a different name. Repeat until available.
4. Ask the user: "What role should this session have?" (e.g., orchestrator, worker, reviewer, specialist)
5. Wait for their response.
6. Ask the user: "What project tag should this session use? (optional — if set, broadcasts will be scoped to this project only)"
   • If there are active sessions with non-empty project tags, list the distinct project tags: "Active projects: myapp, api-server. You can pick one of these or enter a new one."
   • The user can leave this blank for no project (global broadcasts).
7. Wait for their response.
8. Call the register tool with the provided name, role, and project (if given).
9. If the tool returns an error about the name being in use, it may be a stale session from a previous /resume or /clear. Tell the user: "That name is held by a stale session that will expire within 60 seconds. Wait and retry, or pick a different name." Show the active session list.
10. Confirm success: "Registered as {name} with role {role}." If a project was set, add: "Broadcasts and DMs scoped to project {project}."

If registration fails for any other reason, report the error clearly.