[Feature]: Pin one Claude account as the advisor and another as the executor in one orchestration #25725

Problem or use case

Two managed Claude accounts can be signed in, and Orca can hot-swap which one is active. There is no way, inside one orchestration, to keep one account on the advisor and another on the executor.

Reported by @plainlogic24: https://x.com/plainlogic24/status/2105659420969758843

Steps

1. Sign in two managed Claude accounts.
2. Start an orchestration that uses one Claude session as the advisor and another as the executor.
3. Look for a setting or worker-start flag that assigns each role its own account.

Expected

The advisor stays on account A and the executor runs on account B for that orchestration, including restarts, without a global account switch.

Actual

orca orchestration worker-start takes --agent, --model, and --effort. It has no account role. Switching accounts changes which account new sessions use. Sessions already running keep the account they started on until restarted.

Proposed solution

Pin one Claude account as the advisor and another as the executor in one orchestration.

Alternatives or additional context

Related

• Docs cover hot-swap only: https://www.onorca.dev/docs/agents/claude-code
• [Feature]: Select the Claude account for headless/agent spawns via CLI (--account / orca account list) #8770 and open PR feat(claude-accounts): launch a Claude agent on a specific managed account with --account #22691 add a per-launch --account. That flag is not this role pin, and it is not merged.
• [Feature]: Per-worktree account pinning — run different Claude/Codex accounts concurrently #9496 is a per-worktree pin. [Feature]: Per-project Claude account (ask on launch, remember per project) #23227 is a per-project account.