Agent Studio
Best Practices + Patterns

Workflows You Can Try

Choose a workflow for connecting an existing CLI, reviewing parallel tasks or maintaining project checks.

Start with a situation you recognize. Check the required context and permissions, then decide what result should return to the task.

Patterns

Start Now, Review Later

Run a scoped task asynchronously and inspect its diff and checks when it finishes.

Relate Usage to Results

Compare recorded token usage with completed and accepted tasks. Missing usage data remains a limitation.

Repository Structure as Context

Use project rules, architecture decisions and feature boundaries to prepare each task.

Bring Work into the Task Board

Create a scoped task from external work and attach the result and checks to it.

Turn Drift Findings into Tasks

Investigate differences between documentation and behavior, then create a specific correction task.

Capture a Spoken Request

Turn a spoken idea into a written task and check the scope before starting it.

One Reviewable Change

Keep each task small enough to test and accept independently.

Choose the Execution Mode

Choose a configured mode for implementation, review, documentation or repository analysis.

Work with an External CLI

Keep using your editor or CLI while Agent Studio records the task and review.

Open pattern

Understand Parallel Tasks

Use a separate CLI session to inspect related tasks, compare changes and ask questions.

Open pattern

Work Alongside Agent Tasks

Run scoped tasks while you review the design, dependencies and results.

Open pattern

Best Practices

Separate Development and Reference

Keep an independent checkout for reviewing a known revision. This reference checkout is distinct from a published Stable release.

Name the Allowed Checkout

Tell runners where to work and which reference checkout must remain unchanged.

Update the Reference Deliberately

Update a clean reference checkout to a selected revision, using a repeatable script. Record that revision for reviews.

Identify the Project and Write Scope

Name the repository and permitted paths for every task in a workspace with several projects.

Configure Frontend Checks

Run lint, formatting and component checks before reviewing visual changes.

Angular Website Checks

Run TypeScript, template and SCSS checks, then inspect component boundaries and rendered pages.

Open guide

Keep Tasks Independently Reviewable

Give each task a clear input, output and acceptance criterion.

Review Architecture Decisions

Review feature boundaries and shared components as agents implement changes.

Keep Checks with the Task

Attach screenshots, test results, diffs and review notes so another reviewer can follow the decision.

Choose a Workflow

The patterns below describe recurring situations. Their detail pages explain how to prepare the work, carry it out and review the result.

Prepare the Repository and Checks

Use the recommendations below to define write boundaries, keep tasks small and record the checks needed before accepting changes.

Turn the Workflow into Task Requirements

For example, an external CLI workflow needs a named project, a task scope and an agreed API handoff. Put those requirements into the task before work starts.