Skip to content

Support multiple agent presets per provider (e.g. Claude Opus / Claude Sonnet) with their own arguments #36236

Open

Description

@loheiman

Problem

When I start agents from issues (Tasks → Start, or Create worktree with a linked issue), Orca launches the agent with a first prompt that already contains the issue number or link. The agent starts working immediately, so I can't run /model first. The model is fixed by the provider's single Arguments field.

I often want to start several agents from a list of issues and choose the model per issue. For example, Opus for the hard ones and Sonnet for the routine ones. Today I have to edit Settings → Agents → Arguments between launches, which is slow and easy to forget, and not workable when starting several in a row.

Proposed behavior

  • Let users create additional agent entries for a provider ("Duplicate" or "Add preset"). Each one has:
    • a name (e.g. "Claude Opus")
    • its own Command, Arguments and environment
    • its own Enabled/Disabled and Default state
  • Show the presets in the Agent dropdown of Create worktree, and wherever else an agent is picked when starting from an issue or PR. Group them under the provider's icon.
  • Remember the last-used preset per project, or let the user set a default.

Example

Preset Command Arguments
Claude Opus claude --model opus
Claude Sonnet claude --model sonnet

Why this matters

  • Choosing a model per issue is a common workflow when launching agents in bulk. Opus fits planning and hard problems, Sonnet fits cheaper, faster tasks.
  • The first prompt is sent at launch, so the model has to be chosen before the session starts. /model can't fix that.
  • "Claude Agent Teams" already shows Orca supports more than one launch configuration per provider. Users just can't define their own.

Alternatives considered

  • A per-launch override: the sliders icon next to "Agent" in Create worktree could accept one-off arguments. Helpful, but saved presets are faster when launching many agents.
  • A wrapper script per variant also needs the ability to add more than one entry.

Screenshots

(Settings → Agents with a single Arguments field per provider, and the Create worktree dialog's Agent dropdown.)

Image Image

Environment: Orca on Linux (Omarchy), Claude CLI.

Activity

  1. cfqlilei commented on Oct 31, 2026

    @cfqlilei

    Concrete use case: named Claude launch variants for different models.

    I use multiple Claude Code model configurations and want to select them directly when creating or launching an agent, for example:

    • Claude Sonnet → claude --model sonnet
    • Claude Opus → claude --model opus

    The desired behavior is:

    • create a named preset with a command, default arguments, and environment variables;
    • select that preset from every existing agent launch surface, including new worktrees and the terminal agent picker;
    • persist presets across Orca restarts;
    • keep presets available independently of installed-agent discovery;
    • preserve the built-in Claude integration and treat each preset as the same underlying Claude agent with different launch settings.

    To keep the initial UX simple, the main requirement is reusable Claude --model arguments. Separate controls for effort, permissions, or account management are not required for this use case.

    Environment: Orca 1.4.245 on macOS 15.5 (Apple Silicon), Claude Code 2.1.311.

  2. TomaszMarciniakHeroGaming commented on Nov 12, 2026

    @TomaszMarciniakHeroGaming

    +1. My main use is switching between two Claude models (Opus / Fable) when I create a worktree. Showing presets as one-click options in Create worktree, not only in the dropdown, would remove most of the friction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions