Agent Studio
Workforce Sensemaking CLI

Use a CLI to Understand Parallel Tasks

Inspect the repository, logs and task results in a separate CLI session while Agent Studio keeps the work visible.

Begin with a focused question and read-only access. Check the cited records before turning an answer into a task update.

Read the full guide Back to patterns
Problem

Find the Relationship Between Tasks

A board shows task state, but a review may need more detail: which changes overlap, why a task is blocked or which checks are missing. A separate CLI session can inspect the relevant records while work continues.

Example: Workforce Sensemaking CLI

Example · schematic workflow
Studioworkforce board
CLIanalysis
humanfinal judgement
WorkforceAgent Studio keeps tasks, lanes, evidence and review state visiblerunning
HumanBuilds understanding while the work continues in parallelthinking
CLIReads the same context, explains traces and can create or update tasksbeside
MapDiagrams, summaries and follow-up tasks turn activity into orientationclear

While Agent Studio runs tasks, a second CLI with permitted project context can explain logs, draw diagrams and propose follow-up work.

Approach

Inspect First, Then Propose an Update

Ask one question about the current work. Require references to the relevant tasks, revisions and results. Check the answer before using it to create or change a task.

Use this session to investigate existing work. If the CLI should implement a change itself, give it a separate task with its own write scope.

Preparation

Define What the CLI May Read

Choose the project, task IDs and source revision. Supply the logs, diffs and recorded results needed for the question, and state what information is missing.

  • Start with read-only access.
  • Ask for observations and assumptions to be distinguished.
  • Decide separately whether API writes are permitted.
Workflow

Check the Answer and Record the Decision

Compare the explanation with its sources. If it reveals a missing check, conflicting change or unclear requirement, record a specific correction or follow-up with the task.

Example: Workforce Sensemaking CLI

Example · schematic workflow
Studioworkforce board
CLIanalysis
humanfinal judgement
WorkforceAgent Studio keeps tasks, lanes, evidence and review state visiblerunning
HumanBuilds understanding while the work continues in parallelthinking
CLIReads the same context, explains traces and can create or update tasksbeside
MapDiagrams, summaries and follow-up tasks turn activity into orientationclear

While Agent Studio runs tasks, a second CLI with permitted project context can explain logs, draw diagrams and propose follow-up work.

  • Ask for a task-and-file map when several changes overlap.
  • Use a diagram when it makes dependencies easier to inspect.
  • Keep the source revision with the saved explanation.
When it fits

Use It When the Board Leaves a Question Open

Try this during a migration, refactor or several related reviews. It works best when you can identify the relevant records and have time to verify the explanation.

Limits

Treat Summaries as Review Aids

A second CLI can misread a dependency or omit a relevant fact. Diagrams and summaries help organize the review, but their conclusions still need source checks. Broad task edits require their own explicit scope.