Repository navigation
Switchback 1.6.0
Added
- Start from your OpenCode setup. On a first run, when an OpenCode config is found,
switchback initfirst asks whether to start from it: its models (the main one stays current), MCP servers, and permissions come over and are shown before anything is written; API keys stay where OpenCode keeps them, and setup names the environment variables Switchback needs.--from opencodedoes it unattended (ADR 0022)
Fixed
- Config changes made outside a running engine take effect. The shared engine reloads
~/.switchback/config.jsonand the project's config files when they change, soswitchback initin a terminal,switchback config edit, and editor saves apply without closing every client first. A file that doesn't parse is reported and the config in effect stays switchback doctorpoints out~/.config/switchbackand~/.local/share/switchbackleft from before 1.1.0, which nothing reads- Setting the current model during setup (
--current) no longer leaves it on the escalation ladder too - VS Code webview tests no longer fail depending on which test file loads the Markdown renderer first
Install
On macOS and Linux: curl -fsSL https://switchback.sh/install.sh | sh (add -s -- --vscode after sh for the VS Code extension too). On Windows, in PowerShell: irm https://switchback.sh/install.ps1 | iex. Or download the binary for your platform, verify it against SHA256SUMS, make it executable, and put it on your PATH as switchback. Then run switchback init.
Install the VS Code extension from the Marketplace or Open VSX (code --install-extension isaiah-harville.switchback), or from the switchback-vscode-1.6.0-<platform>.vsix here. Each platform's extension includes the engine, so no separate install is needed; the universal .vsix uses switchback from your PATH.
Binaries are not yet signed or notarized (#33). On macOS, clear the quarantine flag with xattr -d com.apple.quarantine switchback.