Repository navigation
Switchya 0.1.0-preview.5 — Windows app and CLI
Pre-releaseSwitchya 0.1.0-preview.5 — Windows portable preview
This update adds opt-in automatic approval for projects you trust, refines the
workspace and fixes first-run and keyboard issues. The ZIP includes both the
native desktop app and the Switchya CLI.
Changes
- Opt-in automatic approval. Approval settings (select the approval note
beside the model picker) lets a trusted project apply file edits and/or run
shell commands without a prompt, and a session can override its project. It
is off by default. While it is on, the composer note turns amber or red and
the header reads Auto-approve on. - Automatic approval only replaces the click. Every operation is still
recorded and marked Auto-approved. Protected paths stay blocked, and edits
outside the project, to Switchya's own state, to gateway or agent account
settings, to files other programs load by themselves (shell profiles, Git,
editor and agent settings), or anywhere in a project that contains your home
folder still ask. - The same project setting covers complete Codex and Claude Code edit and
command requests in Existing agents, read when each request arrives, so
turning it off reaches runs already in progress. Deny-only requests and other
tools, including MCP and web tools, still wait for you. - From the terminal, use
switchya trust --edits on --commands on, or
--auto-approveonchatandrun. - The workspace is easier to read: transcript rows, notices and the composer
share one column, repeated agent notices appear once, and tool rows use
readable names. Pending approvals stand out, and the first-run screen offers
Connect a provider, Use an existing agent and Refresh models. - Existing agents says "No agent CLI found" and lists what it checked when
no Codex, Claude Code or Antigravity CLI is installed. - Keyboard focus no longer drops to the page after Allow once, Deny or Close
details. The provider form says why a configuration name is rejected, and
cancelled and timed-out commands say so in transcript rows. - Phone, keyboard and contrast fixes across the workspace: 44px touch targets,
an accessible agent-mode switch, text of at least 12px outside small labels,
and stronger dark-theme separation. - A failed Codex turn now says why, for example that the configured model is
not available for the account or that a usage limit was reached, instead of
stopping with only "Failed".
See CHANGELOG.md in the repository for the full list.
Install or update
Close any running Switchya desktop or browser host, then extract the entire
ZIP into a new folder. Open switchya-desktop.exe, or run
switchya.exe serve to use the browser workspace. Both executables report
0.1.0-preview.5.
The preview targets Windows 10/11 x64. Install the
Microsoft Visual C++ v14 x64 runtime
and, for the desktop, Microsoft Edge WebView2 Runtime. This portable preview
is unsigned and has no installer or bundled runtimes. Existing configuration,
accounts and session data remain under %LOCALAPPDATA%\Switchya; no
credentials are included in the ZIP.
Read docs/SWITCHYA.md for setup, approvals, automatic approval, account
selection and recovery, and docs/ACCOUNTS.md for sign-in methods and profiles.
Verification
- The full Rust workspace suite passes on Windows (3,788 tests), and CI passes
on Windows, Linux x64 and arm64, and macOS arm64 and Intel, with Clippy
warnings denied. The workspace UI (103 tests), dashboard, packaging and
website checks pass. - Automatic approval was checked with these release binaries against the real
Codex 0.163.0 and Claude Code 2.1.312 CLIs throughswitchya agent run. Each
CLI used an isolated home and a local mock model API that scripted its tool
calls, so these runs prove the approval path, not model quality. With a
project's edits and commands on, Switchya answered the real file-change and
command requests and the files appeared on disk. With the matching switch
off, or for a write to.vscode/settings.jsonwith both on, the same
requests were held for review and nothing was written. - A failed Codex turn was checked against the real CLI, which showed the
rejected model's reason. - No real model turn was run through automatic approval: the Codex and Claude
Code accounts on the test machine could not start one. Automatic approval
from the workspace's Approval settings with a real model, and the macOS and
Linux desktop, remain unverified.