Repository navigation
Description
Problem or use case
Each CLI harness can only appear once in Settings → Agents. I use one harness (e.g. Codex) against several different models — OpenAI's hosted models, third-party providers, and locally-deployed open-source models. The CLI invocation is identical; only the model / base URL / API key differs. Today the only per-agent customization is agentCmdOverrides, agentDefaultArgs, and agentDefaultEnv, all keyed by a single TuiAgent id, so I can configure exactly one Codex profile and have to hand-edit settings whenever I switch models.
Locally I already distinguish these combinations with shell aliases — one alias per model × reasoning-effort pair, all wrapping the same CLI. Orca can't see them: a shell alias isn't on PATH as a binary, and detectCmdAliases in TUI_AGENT_CONFIG works the other way around — it collapses several command names into a single catalog entry rather than surfacing them as separate ones. So the distinction I maintain in my shell is flattened away the moment I'm in Orca.
Proposed solution
Let one harness back multiple named catalog entries. Each entry would have its own label, args, and env, and would show up as a separate row in Settings → Agents and in the agent picker — so Codex (gpt-5), Codex (local qwen), Codex (vendor X) can be enabled, disabled, and set-as-default independently.
claude-agent-teams is already exactly this shape by hand: a distinct id whose expectedProcess is claude and which requires claude on PATH. Generalizing that into user-definable entries with a baseAgent: TuiAgent field would cover it.
Concretely, an entry should be able to override the launch command itself, not just args and env — that's what lets codex-high and codex-local-qwen be two rows backed by one harness, mirroring the aliases I already have.
Alternatives or additional context
- Workaround today is editing
agentDefaultEnvper switch, or shell wrappers on PATH that Orca can't detect as agents. - Main blockers:
TuiAgentis a closed union (src/shared/types.ts:2397) and every table isRecord<TuiAgent, …>;isTuiAgentvalidates by membership inTUI_AGENT_CONFIG;normalizeDisabledTuiAgents(src/main/persistence.ts:5274) silently drops unknown ids. A parallelcustomAgentslist withbaseAgentwould avoid widening the union. - The commit-message flow already has a scoped
CUSTOM_AGENT_IDescape hatch (src/shared/commit-message-agent-spec.ts:673), but it never reaches the launchable catalog.
Activity
AmethystLiang commentedon Jul 17, 2026
it's coming :-D
s546126 commentedon Jul 17, 2026
@AmethystLiang Can't wait to try out this new feature!
Dhi13man commentedon Sep 4, 2026
#17668 runs multiple named Codex profiles on my fork. Is that what you had in mind?
wrightbuilt commentedon Sep 9, 2026
Adding my upvote. I want multiple named Codex entries in Orca—such as a default model, a high-effort reviewer, and an alternate-provider model—each with its own model, CLI arguments, and optional environment.
In Orca 1.4.198,
worktree create --agent codexselects Codex but does not allow choosing a model or effort per launch.worker-startsupports model/effort overrides, but there is still no reusable named profile in the normal launcher. Editing global Codex defaults or manually creating terminal commands is awkward when running several variants in parallel.PR #17668 looks like exactly the right direction. I’d appreciate seeing this prioritized or merged.
harisonw commentedon Sep 25, 2026
I would use this to create multiple named entries backed by GitHub Copilot, for example
Copilot Lunalaunchingcopilot --yolo --model=gpt-5.6-luna. This would provide a quick, lower-cost model window alongside the normal Copilot configuration, without manually editing settings between launches.iHusk commentedon Oct 2, 2026
This still in the pipeline? I/my team manage multiple separate billing profiles for different clients and being able to dispatch these as custom agents would be a huge boon.
nwparker commentedon Oct 18, 2026
Consolidating #25661’s matching Claude use case here: named entries such as
claude-code,claude-docsandclaude-reviewcan wrap the same Claude harness while loading different plugins and choosing different entry agents. Each should remain a separately selectable launch option with its own command and a Claude base type, rather than requiring a raw terminal or repeatedly changing one global Claude command. This fits the command override plus baseAgent model proposed here. The original request remains at #25661.danchamorro commentedon Nov 3, 2026
I would also find this useful, particularly in Chat UI.
I use separate Pi profiles for personal work and different businesses. Each profile has its own models, extensions, settings, and account configuration. I also use separate personal and work Claude Code subscriptions.
I would like to add named instances such as
Pi Personal,Pi Work 1,Pi Work 2,Claude Personal, andClaude Work, then choose the right instance when starting a chat or terminal session without changing a shared agent configuration.Each instance should have its own executable path, launch arguments, and environment variables. For Pi, that includes a separate
PI_CODING_AGENT_DIR. Existing sessions should remain associated with the instance they started with, and credentials and configuration should remain separate between instances.T3 Code's provider settings illustrate the experience I mean. The screenshot below shows multiple named instances of the same agent, with separate runtime configuration. Connection names are anonymized and the account identity is redacted.
This would help avoid accidentally using the wrong account or Pi profile when switching between personal and work projects. Account switching alone does not cover profiles with different extensions and settings.
eltria commentedon Nov 7, 2026
A concrete case for named entries backed by the Claude harness, and what a plugin can and can't cover today (Orca 1.4.251, macOS).
I run Claude Code through several wrappers. Each is a small script that exports
ANTHROPIC_BASE_URL, a token and the model mapping for one API gateway, then doesexec claude --dangerously-skip-permissions "$@". One more entry is a managed launcher with its own subcommand (<launcher> launch claude). I'd like to pick one of these by name when starting an agent, like a terminal-profile list (name + command).What this needs beyond today's single Claude command override:
<launcher> launch claudeis three words; Orca's own args (--prefill, permission flags, the prompt) go after it. The launcher already forwards unknown flags toclaude.claudeprocess, so prompt injection, status hooks, trust preflight and resume should work exactly as for Claude. A rule like "changing the executable drops the provider identity" (feat: add custom agent launch profiles #17668) would turn all of them into plain terminals.Meanwhile I use a local plugin: an
agent.launch.beforehook swaps the program at the head of Claude's command for the wrapper picked in four status bar items. It covers new launches from every launcher, but:contributes.agentHarnessesis still reserved),agent.launch/terminal.createfrom a plugin always open in the background, so a "start this profile now" command can't bring the new tab forward.Happy to test #8337 or a follow-up with this setup on macOS.
cfqlilei commentedon Nov 8, 2026
Adding a concrete Claude-only case from the terminal new-agent path (Orca 1.4.251, macOS 15.5, Apple Silicon).
Setup. One Claude CLI, several model aliases. The only difference between them is the model flag:
claude --model opusversusclaude --model sonnet. I want each variant to be a named entry I pick when I open an agent tab.What 1.4.251 gives me today
Argumentsstring per agent, so switching models means editing that field before each launch, every time.Argumentsfield for terminal launches, but it is a per-launch draft: not saved, not named, and not selectable next time.orca agent launch --modelandorca worktree create --agent --modelchoose a model for one launch, but there is no reusable named entry, and neither takes arbitrary extra arguments.Proposed
Named entries under an existing harness, each with a label, command, arguments and environment, selectable everywhere an agent starts (new-tab terminal picker, Create worktree,
worktree create --agent), persisted across restarts, and still treated as the base harness so prompt injection, status hooks and resume keep working.Related: #36236 (the Claude-only preset request filed earlier).
feat(agents): add chat-list view, composable filters, and Search as C…
Stardust0831 commentedon Nov 13, 2026
I'd like to add a concrete Codex use case: run multiple configurations concurrently, each selectable by a custom alias in Orca's native agent picker.
Each configuration should support:
CODEX_HOME, including an existing user-managed directory.Codex Personal,Codex Work, orCodex Local.For example, I use separate API keys for different purposes and would like to launch both configurations side by side without changing a global Codex setting. Separate homes would also let me keep their configuration and history apart.
This should work for native chat and terminal sessions. Follow-up messages and resumed sessions, including after restarting Orca, should keep the configuration they started with.
Could this be covered by the named-entry support proposed here? Related: #10366 for importing an existing
CODEX_HOME.Stardust0831 commentedon Nov 13, 2026
I've implemented and locally validated a Codex-focused prototype for this: implementation, based on
c75b43bc8666.The configuration is a named entry with
{ id, label, homePath, modelProvider, model? }. Multiple entries can use the same home with different providers, or different homes with the same provider ID. For example,Codex WorkandCodex Personalcan select two providers in oneconfig.toml, including different API keys for the same endpoint; another entry can select a separate home.The main implementation choices are:
codex, with a separate stable entry ID. Settings → Agents manages the entries, and the picker exposes their aliases for native chat and terminal launches.CODEX_HOMEand pass-c model_provider="…"per process. Credentials remain in Codex configuration or the host environment. Named launches use their own model/configuration instead of inheriting global Codex model/argument defaults.Validation used real Codex 0.167.2, isolated homes and a localhost Responses SSE server with three dummy keys at the same endpoint:
pnpm check:changed --maxWorkers=2 --timeout=3passed 36 of 37 checks; its broad affected-unit-test selection timed out at 180 seconds, so I am not claiming a full-suite pass. The UI also reportedUnknown method: linear.onLinkedIssueUpdatedfrom an unchanged web bridge path; feature assertions passed with that error recorded separately.This is a prototype with explicit remaining scope: native macOS/Windows, SSH, Electron and mobile interaction still need validation; Windows-host → WSL launches are refused pending proper host routing. Profile-specific model discovery before launch is not implemented yet (an entry can specify a model or use its home's default). Per-alias default/disable controls and other harnesses are also still outside this Codex slice.
For attribution, I adapted the normalization/deduplication and draft ID/upsert excerpts from @brennanb2025's #5728, commits
fa4631b435566andf0b92dfc9ef9. The implementation commit records the source paths and retains the original co-author credits. #5754's separate profile identity / canonical harness approach also informed the design; no code was copied from #5754, #8573 or #17668.Would the separate entry identity plus a persisted launch descriptor be a useful foundation to integrate into the existing named-entry work, particularly for native chat and restore behavior?