Tasks, agent runs and review in one workbench
Assign work to Codex, Claude Code or Gemini, then review changes and evidence with the task that requested them.
Prepare the scope, select an agent and host, then inspect the result. Accept the work, request a revision or create a follow-up. Start with one repository before adding hosts or parallel tasks.
Claude Code A coding-agent CLI that remains the execution engine for its assigned task.
Codex A coding-agent CLI that Agent Studio can run in an isolated task worktree.
Gemini A coding-agent CLI that returns its work to the same task and review surface.
Read the result beside the task
Open a task to see its execution, recorded checks, token usage and integration state together. This completed task shows its history beside the result and passed checks.
A completed task with its result, checks and integration state. Detail from the live product, captured 26 September 2026. Original interface in English.
Inspect changed files beside the task
Open the branch, commits and diff alongside logs, checks and screenshots. Managed coding runs use isolated worktrees, including single-slot execution, resume and reissue. The platform captures and integrates their changes.
Decide what to accept
Automatic review can request rework or escalate a finding. After delivery gates pass, integration can occur before human review. Inspect the resulting revision and evidence, then accept the task or request a specific follow-up.
Exception example: an unresolved finding remains after the reissue budget is exhausted. The available options are focused rework, acceptance as-is or abort.
Use configured coding-agent CLIs
Codex, Claude Code and Gemini execute the coding work. Authentication, model access and provider terms belong to the CLI and account you configure. The Studio records the selected agent and reported usage with the task.
CLI configuration, model choices, usage limits and reported account usage. Historical workspace capture from July 2026; values describe the captured date.
A dated model snapshot
The table records models offered by the installed Codex CLI 0.153.4 and Claude Code 2.1.269 on 12 September 2026. It preserves retired model IDs for historical records. Check your installed CLI and account for today’s availability.
| Model ID | Installed CLI | Generation | Status | Verified |
|---|---|---|---|---|
claude-sonnet-5 | Claude Code 2.1.269 | Claude 5 | current | |
claude-opus-5 | Claude Code 2.1.269 | Claude 5 | current | |
claude-fable-5-1 | Claude Code 2.1.269 | Claude 5.1 | current | |
gpt-6-astra | Codex CLI 0.153.4 | GPT-6 | current | |
gpt-5.6-sol | Codex CLI 0.153.4 | GPT-5.6 | current | |
gpt-5.6-terra | Codex CLI 0.153.4 | GPT-5.6 | current | |
gpt-5.6-luna | Codex CLI 0.153.4 | GPT-5.6 | current | |
| ||||
| ||||
| ||||
| ||||
| ||||
Prices and benchmark scores: Token Economy benchmark and pricing evidence — retrieved September 11, 2026.
Choose a mode for the work
Implementation, review and documentation need different instructions. Select a configured mode, keep the scope explicit and compare the returned work and follow-up effort.
Historical seven-day usage example from July 2026, grouped by project and operating mode. These are captured values, not the current workspace total.
Start on a machine you control
Run the Studio and an execution host locally for a small trial. Configure repository access and CLI accounts, create one task in the browser and inspect the result. Change durable task state through the Studio or its API.
Coordinate through a Task Server
A reachable Task Server stores tasks, context, run records and review decisions for its clients. Execution hosts hold the repository access and CLI accounts. Configure authentication and network exposure before enabling shared access.
Example: Workspace Projects
Execute on a remote host
A configured remote host runs the CLI and task worktree while you review in the browser. Follow the host guide for provisioning, credentials and repository access. Recorded end-to-end validation used Ubuntu 24.04; evaluate other environments before relying on them.
Start shared use with a small trial
Several clients can use one Task Server. Name who may create work, operate hosts and accept results. Most recorded use has been solo; shared access still needs validation of permissions, ownership and review responsibilities.
Keep repositories distinct
Use related projects for product code, a website or documentation in separate repositories. Workspace views bring their activity together while tasks, settings and decisions remain attached to the relevant project.
Example: Workspace Projects
Find previous decisions
Read related prompts, logs, Git evidence and review notes before opening another task. The history can explain what was tried, why it was accepted and what remained unresolved.
Activity across projects: a queryable ledger of signals, decisions, and actions with per-project and event-class filters.
Inspect documented product states
The visual documentation pairs product captures with their purpose and source. Where a capture recipe is available, use its route, data state and viewport to reproduce the image and assess later changes.
Discuss a project or task
Project orchestrator and task conversations can refer to tasks, context, usage and review state. Choose the CLI, model and thinking level in the composer. Recorded model switches and source links help reconstruct a conversation’s decisions.
Turn a finding into follow-up work
Inspect a quality or documentation mismatch beside its source. Decide whether the change is required, record the evidence and create a task with a bounded correction.
Example: Drift Findings
Keep work reviewable
A task should have enough context to execute and enough evidence to review. Keep its request, runs, changed files, usage and decisions together; give remaining work a specific next action.