Engines & providers · Feature

Run on the Studio Engine. Or bring your own.

Every install ships with the bundled Studio Engine - no API key, no setup. On Pro and Max, plug in any external CLI agent (BYOC) or connect via your own API key (BYOK), and bind specific engines to specific pipeline roles.

Request access →
Three engine types

Bundled, BYOC, BYOK.

Studio talks to every engine through the same adapter contract - events, tool calls, and approvals look identical no matter which engine ran them.

Bundled
Studio Engine
Included

A curated, ready-to-run model bundled with every install. No API key, no signup.

Setup
Zero - works on install
Quota
Generous on Free · increased on Pro · unlimited on Max
Best for
Daily-driver task running
Free · Pro · Max
BYOC
Custom CLI agent
Pro

Plug in any external agent CLI on your PATH. Studio drives it through the same adapter contract.

Setup
Point Studio at the binary
Auth
Whatever the CLI already uses
Best for
Existing agent workflows you already trust
Pro · Max
BYOK
Your API key
Pro

Connect any major provider via your own API key. Studio handles the adapter; you control the cost.

Setup
Paste API key in Settings
Storage
Local · OS keychain
Best for
Heavier usage or specific models
Pro · Max
Per-role binding

Bind a specific engine to a specific role.

On Pro and Max, mix engines across the pipeline. A heavier model for planning, a faster model for parallel workers, and a different one for the final review - all in one task.

  • Per-task overrides without changing workspace defaults
  • Per-role defaults saved in workspace config
  • Failover to Studio Engine if a custom engine is unreachable
  • Health-checked at task start — no failed runs from a stale binary
Pipeline binding · task-2af469overrides
Orchestrator
Studio Engine
Planner
BYOK · large-model
Workers
Studio Engine · ×3
Worker review
BYOC · my-reviewer-cli
Final review
BYOK · large-model
Reporter
Studio Engine
$ studio doctor
✓ Studio Engine     v1.4
✓ BYOC my-reviewer  v0.9
✓ BYOK large-model  api.example.com
Health & readiness

Know an engine is ready, before the run starts.

Studio runs a health check at every task start. Stale binaries, missing keys, and unreachable endpoints surface as fix hints - not silent failures.

Engine readiness1 ready · 2 fix hints
Studio Engine Included
studio-engine v1.4 · ready
Healthy
my-reviewer-cli BYOC · Pro
v0.9 · /usr/local/bin/my-reviewer-cli
Binary is 3 versions behind. Run studio engines update my-reviewer-cli.
Stale
large-model BYOK · Pro
api.example.com · key-…7f2c
401 from api.example.com. Update the API key in Settings → Engines.
Unreachable
Related features
Studio pipeline
Engines bind to specific pipeline roles.
Live visibility
Every engine emits the same uniform event stream.
Approval gates
Approvals look identical regardless of which engine ran.
Request access

Start with the Studio Engine. Bring your own when ready.

Agent Studio is in private alpha. Drop your email for a build and setup guide.