Fix and enrich the orchestrator coordinator system prompt so it matches the current CLI and teaches harness selection + command discovery

[VenkataSakethDakuri]

Fix and enrich the orchestrator coordinator system prompt

Change the orchestrator coordinator system prompt so it matches the current CLI and teaches harness selection plus command discovery.

Files changed

• backend/internal/session_manager/manager.go (orchestratorPrompt)
• backend/internal/session_manager/manager_test.go (TestSpawnOrchestrator_UsesCoordinatorPrompt)

What changed in the prompt

• Added the now-required --name flag to the spawn example:

  ao spawn --project <p> --name "<label, max 20 chars>" --prompt "<clear worker task>"

• Added a note that --project and --name are both required.

• Added guidance for choosing a worker's agent: --agent <name> (an alias for --harness), for example --agent codex or --agent claude-code.

• Clarified that if --agent is omitted, the project's default worker agent is used.

• Added a discovery pointer to run ao spawn --help for the full list.

• Added a broader discovery pointer to run ao --help and ao <command> --help for other commands.

What changed in the test

• Updated the expected spawn-command substring to include --name.
• Added assertions that the prompt contains:
  • --agent <name>
  • ao spawn --help
  • ao --help

Why

• --name became required in #2302 on 2026-06-30, but the prompt still used the old command.
• That meant the orchestrator was being told to run a command that now fails with exit code 2 because --name is required.
• --harness / --agent was never mentioned, so requests to spawn a specific harness, such as codex, silently fell back to the project's default worker agent, claude-code.

[Vaibhaav-Tiwari]

noice