v0.6.8

You choose which agents take over a task when an account runs out, and Switchboard follows that
order on its own. Nothing changes until you set a chain. If you run 0.6.1 or later, this version
arrives on its own. Signed by the same team (KJ35UYYL22).

Windows: windows_authenticode: NOT_SIGNED. The installer is built natively but not
Authenticode-signed until the organization's Azure signing account exists; SmartScreen may warn.

Fallback chains

• switchboard chain and the MCP tools switchboard_chain_get / switchboard_chain_set keep your
  order of agents for continuing work when an account runs out — for the whole machine, a project
  or a single task; the narrowest one applies, and none applies until you set one. A ready-made
  order: Claude Code → Codex → Kimi Code → Hermes. An agent can be pinned to an account or to a
  paid key named in Project Observatory's vault; other agents never get a Claude or ChatGPT
  subscription.
• When an agent's account runs out and a chain is set, its work moves on by itself. For a task
  recorded as a Project Observatory workflow, Switchboard hands it to the next agent of the chain
  that has an account with quota — Claude Code or Codex for now — and opens that session in the
  task's folder, starting from the last checkpoint. Without a chain nothing happens. Kimi Code and
  Hermes in a chain are skipped until paid-key ceilings are in place.

Verify

gpg --verify SHA256SUMS.asc SHA256SUMS      # key 63B30DC324BD697487AA31944FAFB8AEC803B6A7
shasum -a 256 -c SHA256SUMS --ignore-missing
gh attestation verify <file> --owner passioncode-ai --signer-repo passioncode-ai/.github

The organization's public key: https://github.com/passioncode-ai/.github/blob/main/release-signing/passioncode-release-signing.asc