Skip to content

[Feature]: Agent profiles for optional orchestration routing #22573

Description

@wuhaoyujerry

Problem or use case

Choosing an agent, model, and effort for each worker is repetitive. A hardcoded routing table cannot reflect each user's models. Intent routing should remain optional.

Proposed solution

Let users save agent profiles with a name, agent, model, effort, and short "when to use" note. Offer profiles when starting an agent. When a user requests profile-based orchestration, the coordinator reads those notes and picks a profile for each task already selected for delegation. Explicit user choices win; ordinary orchestration stays unchanged. Profiles belong to the worker's host. Report the effective launch settings, and use the agent default when no suitable profile is available.

Example: Save UI work with codex, gpt-5.6-sol, high, and note “Use for layout and styling.” For “Build the settings page using profile routing,” the coordinator selects UI work and starts that worker. A normal request uses Orca's existing launch flow.

Alternatives or additional context

Paseo profiles show this pattern. #21747 covers a separate account-aware runtime policy hook.

Activity

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