* feat(new-workspace): add "None" agent option that opens only the setup script
New workspaces previously required choosing an agent or a blank terminal,
so a setup script that launches its own agent always ran next to an extra
shell. The quick-create agent picker and Settings > Agents now offer
"None (setup script only)": when setup runs, the workspace opens with just
the Setup tab focused; without a setup script it falls back to a blank
terminal.
The default is stored as defaultTuiAgent 'blank' plus a new optional
newWorkspaceSetupOnly flag, so clients and servers that only know 'blank'
degrade to a blank terminal instead of rejecting an unknown value.
Closesstablyai/orca#25247
* fix(new-workspace): honor the "None" default for CLI-created workspaces
"None (setup script only)" only took effect in the new-workspace dialog.
A workspace created with `orca worktree create` still opened a blank
terminal first and left it selected, because the main process builds
those tabs and never read the setting.
The main-process tab provisioning now skips the blank terminal when the
default is "None" and a setup script runs in its own tab, so Setup is the
only tab. The same rule applies to CLI creates that activate the
workspace, and to dialog creates the user navigated away from before
they finished. A split setup or repo default tabs still get their shell.
The setup-only check moved to src/shared so main and renderer share it.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(new-workspace): register the CLI activation caller and stay under the line limit
The CLI activation path now passes providesInitialSurface for the "None"
default, so it has to appear in the test that lists every caller using
that option; the full test run failed without it.
Merging main pushed worktree-creation-flow-execute.ts to 301 lines against
the 300-line limit. Naming the background-create condition brings it back
to 300 with no behavior change.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(new-workspace): open a blank terminal when the setup-only Setup tab fails to spawn
The "None" default skips the blank shell because the Setup tab will be the
only surface. If that spawn fails, the workspace was left with no terminal.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* style: format the setup-only fallback terminal call
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
* fix(workspace): save None through host settings and honor per-create choices
* fix(settings): clear None when legacy clients choose a blank terminal
* fix(settings): clarify None with split or skipped setup
---------
Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
Co-authored-by: Neil <neil@stably.ai>
Each native Claude and Codex chat now has its own permission mode (Ask for approval, Accept edits for Claude, Approve for me, Full access), shown and changed from a button right after "+" in the composer. A change takes effect before the next message: the agent restarts quietly and resumes the same conversation, never interrupting a reply or background work. New chats start from Settings → Chat → Permissions, which is seeded once from Agent Permissions. The mode is stored as an ordinary chat option, and the restart reuses the existing "replace the agent before the next message" step.
Neil
Brennan Benson