v0.6.15

Fabric Switchboard on Linux (x64 and arm64) and on Windows on ARM, beside macOS (Apple silicon and
Intel) and Windows x64. Launching a session now picks its folder with the system picker and an
Isolated session box, a sign-in left waiting in Terminal ends with one Cancel, and the ordinary
Kimi Code sign-in on kimi.ai is read correctly.

Windows: windows_authenticode: NOT_SIGNED. Built natively for x64 and arm64; the installers are
not yet Authenticode-signed (the signing identity validation is in progress), so SmartScreen may warn.

Added

• Linux, x64 and arm64 (SB-88; operator decision 2026-10-09: every PassionCode.ai product runs
  on Apple silicon and Intel Macs, Windows and Linux). A .deb (app and switchboard on PATH), an
  AppImage that updates itself, and the CLI alone. Credentials live in the Secret Service (GNOME
  Keyring, KWallet, KeePassXC), never in a plain file; sessions open in your terminal app
  ($TERMINAL, then the common ones); the session scripts no longer need zsh. Tested in the release
  and nightly workflows against a real GNOME Keyring, with the app's smoke check under Xvfb.

• Windows on ARM (arm64): a native installer and CLI beside the x64 ones (SB-88).

• Launch any account in a folder you pick (operator decision 2026-10-09, SB-86): the row menu's
  Launch… replaces Launch isolated… and Launch managed…; an Isolated session box chooses the
  mode, ticked and locked when only an isolated session is possible. Every folder Switchboard asks
  for — launches, Kimi Code, agents, projects, project rules — is chosen with the system folder
  picker, never typed; the picker opens at the last folder chosen, remembered across restarts.

• A provider terms notice (operator decision 2026-10-08, SCN-049): Accounts shows it from the first
  start, while the first account is added, until you dismiss it; About shows it always. It says to
  use Switchboard in line with the terms of Anthropic and OpenAI, that breaking a provider's terms
  can get the account blocked, and that you are responsible for how you use your accounts.

Changed

• Kimi Code accounts use the same compact row as Claude Code and Codex: a small Launch… (or
  Sign in) and a ⋯ menu with Sign in again and Remove…; Add Kimi Code account and Refresh
  are small buttons (SB-86).
• A failed quota check logs the provider's HTTP status as a number (usage_check http_error
status), so a refusal (403) and an outage (502) are told apart (SB-85).

Fixed

• A CLI or agent request to the running app could fail as "Control request did not complete"
  with nothing sent (SB-90): the second request on the control connection went out before the
  connection was ready again. Seen on Linux in 12 of 44 requests; macOS's timing mostly hid it.
• Cancel ends a sign-in still waiting in Terminal instead of refusing until its window is closed;
  a refused Cancel no longer stops the banner from noticing Terminal, nor offers a Retry that
  meant finishing. The same for Kimi Code, whose sign-in now notices a closed Terminal (SB-83).
• The ordinary Kimi Code sign-in on kimi.ai read as signed out when an older kimi.com login or a
  stale region marker remained: Switchboard now reads the login slot config.toml names, as
  kimi does (SB-84).

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