Inspired by Manasvi Kapoor (@void_exception), Day 2 on Cursor Ultra — Auto + Composer + Grok at 3% usage — 24 August 2026. First-party from client repos and WordPress desks. Not a reprint.
His useful trade: spec the work, split the scopes, hand-guide Grok and Composer. Usage barely moves. The con is you babysit. Opus-style swarm would one-shot more of it. You would also own a diff you cannot explain.
We take the babysit.
A restoration page, a franchise sitemap, a live Fluent Form is not a weekend demo. Four agents on one post ID already taught us what unattended speed does to a CMS. Same pattern in Cursor: a swarm that “just finishes” is four writers with no lock.
How the day actually runs
- Voice or chat writes one ticket. One done-when.
- A human splits the scopes before Cursor touches the tree.
- Auto / Composer / Grok runs inside that fence.
- One writer commits. Live URL is the check, not the agent’s “done.”
That is slower than a clip. It is how you still have a site in the morning. Related: Voice writes the ticket and one WordPress lock.
Usage theater is a different game. Burning a high-end pool to look busy is not throughput. Manasvi’s 3% day is the receipt that a split spec is cheaper than a swarm you have to unwind.
Will Tygart — Tygart Media.
Split it. Then watch it.
Leave a Reply