Skip to content

docs(factories): document agentDefaults.computerUseModel (unreleased feature) #581

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
warp-agent-staging wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs(factories): document agentDefaults.computerUseModel (unreleased feature) #581

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 18 additions & 2 deletions src/content/docs/factories/factory-as-code.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -194,6 +194,22 @@ MCP servers for agents that don't declare their own, in the same form as [`mcpSe

Where runs execute: `warp` for Warp-hosted compute, or the ID of a connected [self-hosted worker](/platform/self-hosting/).

### `agentDefaults.computerUseModel`
Comment thread
warp-agent-staging[bot] marked this conversation as resolved.

Optional. The model the computer use subagent runs with, as a `model_id`. When unset, Warp chooses the computer use model automatically.

```yaml
agentDefaults:
model: auto
computerUseModel: claude-4-5-sonnet
```

Applies only to runs on the Warp Agent harness (`type: oz`); a third-party harness ignores it. It's also ignored when computer use is disabled for the run. Unlike `model`, this key isn't mutually exclusive with `harness` — it selects the model for the computer use subagent, not the model the agent itself runs on.

Computer use supports a restricted set of models. See [model choice for agents](/agents/inference/model-choice/) for the full catalog Warp supports; not every listed model supports computer use.

A managed [self-hosted worker](/platform/self-hosting/) needs an up-to-date worker and agent CLI version that supports `computerUseModel`.

## `agents/<name>/agent.md`

One file per agent. The YAML frontmatter configures how the agent runs, and the Markdown body is the agent's prompt: the durable instructions for its role. The agent's name comes from its directory.
Expand All @@ -213,7 +229,7 @@ The frontmatter accepts:
* `description` - Optional. What the agent does.
* [`agentType`](#agenttype) - Optional. The agent's role.
* `credentialStrategy` - Optional. Overrides the factory-level [`credentialStrategy`](#credentialstrategy) for this agent's runs.
* `model` or `harness`, `runner`, `environmentId`, `secrets`, `mcpServers`, `workerHost` - Optional. The same keys as [`agentDefaults`](#agentdefaults); a key declared here overrides the default for this agent.
* `model` or `harness`, `runner`, `environmentId`, `secrets`, `mcpServers`, `workerHost`, `computerUseModel` - Optional. The same keys as [`agentDefaults`](#agentdefaults); a key declared here overrides the default for this agent.

### `agentType`

Expand Down Expand Up @@ -281,7 +297,7 @@ triggers:

### Execution overrides

An automation may also declare `model` or `harness`, `runner`, `environmentId`, `secrets`, `mcpServers`, and `workerHost` (the same keys as [`agentDefaults`](#agentdefaults)) to override the target agent's settings for the runs it starts.
An automation may also declare `model` or `harness`, `runner`, `environmentId`, `secrets`, `mcpServers`, `workerHost`, and `computerUseModel` (the same keys as [`agentDefaults`](#agentdefaults)) to override the target agent's settings for the runs it starts.

## `runners/<name>.yaml`

Expand Down
Loading