“Delegating a whole ticket is a different category of tool”
Used daily for 6–12 months
I describe the change, go and review someone else's PR, and come back to a branch with passing tests. It explored parts of the codebase I had forgotten existed and matched conventions I never explained. The mental shift from "assistant" to "delegate" took about a week.
Pros
Genuine autonomy on feature-sized work. Runs the test suite without being asked and iterates on real failures.
Cons
Diffs get large. You must review properly or you are just accumulating debt faster.
Problems it solves
Small well-specified tickets now take a review pass instead of an afternoon.
D
David K.Validated Reviewer
CTO · SaaS · 11–50 employees
4.5
June 18, 2026
“Best on legacy code nobody remembers”
Used daily for 6–12 months
We inherited a large service with no documentation and no original authors. Pointing it at the repo and asking how the billing path works produced a better explanation than anyone on the team could have written. That alone justified the subscription.
Pros
Outstanding comprehension of unfamiliar codebases. Terminal-first means it fits our existing tooling.
Cons
Hit Pro limits regularly and moved to Max. No autocomplete, so I still run Copilot alongside.
N
Nadia P.Validated Reviewer
Program Manager · Financial services · 201–1,000 employees
4.5
May 15, 2026
“Powerful, needs discipline and a terminal habit”
Used daily for 6–12 months
Two of our four engineers took to it immediately and two bounced off — the ones who bounced wanted suggestions in the editor, not a agent in a shell. It is a genuinely different workflow and it is not for everyone on the team.
Pros
Very capable when instructions are specific. Excellent at working through failing builds.
Cons
Terminal-centric workflow does not suit every developer. Vague instructions produce confidently wrong work.
