Agent Studio
External CLI on the Side

Work with an External CLI

Keep working in your terminal or editor while Agent Studio records the task, context, checks and review decision.

Use this workflow when you want to implement a change in an existing CLI session and retain a task record that other people can review.

Back to patterns Product workflow
Starting point

Use the Tool You Already Work In

An existing terminal or editor session may already have the context for a change. Before continuing there, decide how its scope, result and checks will be recorded in Agent Studio.

Example: External CLI on the Side

Example · schematic workflow
CLIfamiliar execution
APItask creation
Studioreview surface
DeveloperWorks in VS Code, terminal or a preferred coding-agent CLIfamiliar
AgentCan create or update a task through the Agent Studio APIbridge
StudioKeeps status, context, evidence, tokens and review visiblecontrol
ReviewThe outcome returns to the shared board instead of staying in a chatdone

Illustrative workflow. The pattern keeps the familiar CLI or VS Code workflow alive while Agent Studio provides the task, context, evidence and review surface around it.

Responsibilities

Connect the CLI Session to a Task

Use the CLI for implementation or exploration. Use the Agent Studio task to record the agreed scope, relevant context, result and review. An API handoff connects the two when the external tool has the required access.

  • Name the task before starting implementation.
  • Keep API permissions limited to the intended actions.
  • Record the revision and checks that belong to the delivered result.
API handoff

Provide an Explicit Task Scope

Give the CLI the project identity, requested outcome, permitted paths and acceptance criteria. Ask it to create or update the corresponding task through the API, then inspect that task in Agent Studio.

Example: External CLI on the Side

Example · schematic workflow
CLIfamiliar execution
APItask creation
Studioreview surface
DeveloperWorks in VS Code, terminal or a preferred coding-agent CLIfamiliar
AgentCan create or update a task through the Agent Studio APIbridge
StudioKeeps status, context, evidence, tokens and review visiblecontrol
ReviewThe outcome returns to the shared board instead of staying in a chatdone

Illustrative workflow. The pattern keeps the familiar CLI or VS Code workflow alive while Agent Studio provides the task, context, evidence and review surface around it.

  • Check the project and repository before allowing a write.
  • Distinguish recording an external result from starting a new runner task.
  • Include missing checks or known limitations in the handoff.
When it fits

Use It for an Existing CLI Workflow

This fits solo developers and teams who want task and review records while continuing to use an external coding tool. It needs a controlled handoff and a tool that can access the relevant repository and API.

Trade-offs

Keep the Handoff Reviewable

The extra handoff can leave the task out of date if results stay only in the terminal. Before closing the session, check that the task identifies what changed, which checks ran and who needs to review it.

  • Keep the CLI workflow you already know.
  • Expect to maintain the task record as well as the code.
  • Repository and API permissions remain your responsibility.