Use cases

Small Migrations and Cleanups, Delegated

Delegate repetitive, well-defined changes to agents, and review the proposed pull requests in pieces.

Repetitive Changes Nobody Wants to Make

Replacing a deprecated call, renaming an API, or moving to a new config format is easy to describe and slow to do across many files and services. It's the kind of work that sits in the backlog for months.

Agents Do the Repetition, People Review the Result

Describe the change and split independent work into separate tasks. Ask agents to apply the change, run the checks, and prepare pull requests. Your team reviews each one and controls what merges.

services/billingPR opened
services/authPR opened
services/searchIn progress

Common Questions

What size of migration fits?

Small, well-defined changes with a clear pattern, such as replacing deprecated calls or updating a config format. Large architectural migrations still need an engineer to lead them.

Can several agents work on it at once?

Yes. Agents can work in parallel. Subagents share their root session's workspace, so separate independent changes into tasks with different file scopes. Confirm your plan's concurrency limits before scheduling simultaneous runs.

How do we review it?

As pull requests, the same way you review any other change.

Which models can it use?

Any major provider, plus local and private models. Bring your own keys or subscription, and there's no markup on tokens.

Related: Many at once, Tickets to tested PRs.

Keep Your Attention for the Hard Problems

Start with one repo and one recurring task.