Understand Tasks, Runs and Review
Learn how a task connects the requested outcome to a coding-agent run, its checks and your decision.
Start with the task, then follow execution, review and context. The first-task guide takes you through one small change.
Define a Result You Can Review
A task records the intended outcome, repository, constraints, agent run, changed files and review decision. Split work when it requires several independent decisions.
- State what should change and how you will check it.
- Keep acceptance criteria and relevant constraints with the task.
Check Task State and Process Activity
A board lane describes the task’s stage. It does not prove that a CLI process is currently running. Use live process information and the task history to understand the current state.
- A task waiting for execution needs a runnable scope and configuration.
- Review requires checking the result and recording a decision.
- An accepted task can still need a later correction.
Run the Configured CLI
Agent Studio prepares the task and starts the configured coding-agent CLI. Coding runs use task worktrees; the CLI and its account determine model access. Configure permissions separately: a worktree isolates files, but is not a security sandbox.
Check the Result Against the Task
Use diffs, test results, builds and screenshots to check the requested outcome. A completion message alone does not establish that the change works.
Exception example: DEMO-9 is escalated. One commit and two changed files are recorded; integration into develop and main is still pending.
- Choose checks that match the risk and user impact.
- Use screenshots to inspect visual behavior alongside relevant tests.
- Record why you accept the result or what needs rework.
Provide the Context This Task Needs
Give the run repository rules, acceptance criteria and relevant decisions. Keep older protocols and results in the task history, and retrieve them when they answer a current question.
A real workspace wiki: 384 knowledge pages under categories, a generated Pulse entry view, the recent-change feed and an unfiled inbox.
Begin with One Small Change
State a visible outcome, select the configured CLI and run the task. Inspect the changes and checks, then accept the result or describe the required correction before adding parallel work.