v0.6.6

Signing in again to an account you already saved no longer renames it or copies it into another
pool. 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.

Signing in

• Try again in the sign-in banner repeats the same sign-in. Before, it lost the account's name
  and pool and started over in the default pool: finishing it renamed a saved account to its email,
  or added a second copy of an account saved in another pool — including an account reserved for a
  project, which then showed up for switching Claude Code.
• Signing in to an account you already saved updates it where it is, from its row, from
  + Add account or from Try again: its name and pool stay, every saved copy gets the new
  sign-in, and the notice says it is signed in again. A new account is added only when it is not
  saved anywhere yet.

Under the hood

• The local proxy checks an agent's key in constant time, so response timing cannot reveal which
  key matched.
• The MCP tool descriptions for switchboard_usage and switchboard_project_apply now describe
  what the tools return.

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