Use cases

Learn it in the order
you would use it

12 jobs, each with a brief or a command you can paste. Start with the first: each one builds on the ones before it.

Start with use case 1

First steps

Small jobs where you see every change and decide what stays.

  1. Understand a codebase you don't knowAsk how a project works before you change anything. In Ask mode the agent reads and answers.Ask mode · The task record
  2. Fix a small bug, with checksHand over a bug you can describe in two sentences, and say how you will know it is fixed.Agent mode · Done when · Approvals
  3. Review, keep or rewindDecide what stays. Keep or undo each file the task wrote, or take the whole task back to an earlier instruction.Changes · Keep and Undo · Rewind

Everyday work

The jobs you will hand it most: small, checked, reviewed.

  1. Change course while it worksCorrect the agent mid-run, or line up the next job, without stopping and starting over.Send now · Queue · Stop
  2. Teach it your conventionsWrite down the rules of your project once, so every task follows them without being told.Rules · Memory
  3. Let it check its own UIFor front-end work, have the agent start your dev server and look at the page in its own browser before it calls the job done.Terminal · Browser · Done when
  4. Chase a flaky test with a skillAdd a skill from Extensions and let it bring a proven method to a job, here a test that fails one run in five.Skills · Extensions

Bigger jobs

Work that splits, runs on its own branch, and ends in a pull request.

  1. Build a feature on its own branchRun a bigger task in its own git worktree, so your folder stays as it is until you merge.New worktree · Plan · Questions
  2. Split a job into parallel partsWhen a job has parts that do not depend on each other, the agent can run them at the same time as instances.Instances · Merge
  3. Open a pull request and fix CICommit the work, open a pull request from the task, and hand a failing check back to the agent in one click.Commit · PR tab · Hand to the agent

Hands off

Letting it run while you are away, and what keeps that safe.

  1. Keep it going until it is doneGive a task a standing goal, so it keeps working across turns, and set it up for a run nobody is watching./goal · Approvals
  2. Check on something on a scheduleRepeat an instruction on a timer, such as looking at a nightly build every half hour, and act when something changes./loop