Skip to content

v0.6.32

Choose a tag to compare

View all tags
@github-actions github-actions released this 14 Oct 22:49
· 39 commits to main since this release
v0.6.32
b6cf703
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

A project's new folders join it by themselves (SB-121, operator 2026-10-14). A worktree of a
project repository, another clone of it, or a new repository of the project's source is added to
the project at once, and you get one notification: “app-2 is now part of App.” No question, no
banner. A folder you later remove from the project stays out. Agents' scratch worktrees in
temporary and cache folders are never added. Questions left from 0.6.30 are answered by the first
pass after the update; only a folder Switchboard cannot add (it overlaps another project, say)
still asks.
Going back to 0.6.31 or older after this release makes the project-suggestions file unreadable to
that version; delete project-suggestions.json in Switchboard's data folder if you do.

Launched sessions reach the Fabric project board (SB-20). Sessions Switchboard launches run
with their own Claude Code or Codex home, so the board server you registered (fabric) never
reached them. Now it is carried in — its command and arguments, never its environment.

Hand a workflow to Fabric's console by hand: switchboard continue <wf> --account <id> --dir <folder> --to-console offers it and leaves the prepared session for the console, as the
automatic fallback does with Open hand-overs in Fabric on (SB-108).

A second switchboard serve --data-dir no longer writes into the installed app's log; it logs in
its own data folder (SB-112).

A project whose folder was deleted from disk (a removed worktree) can be saved again: the vanished
folder is dropped instead of refusing every change to the project — renaming it, adding folders or
moving accounts into its pool (SB-128).

Added

  • Launched sessions reach the Fabric project board (SB-20). A managed or isolated session has a home of its
    own, so the board server (fabric) the operator registered for Claude Code or Codex never reached it. Launch now
    carries that one server in beside Switchboard's own: its command and arguments only, never its environment. No
    board registered means none carried; the launch never fails over it.

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

Assets 27
Loading