Let Cursor Auto handle a narrow coding checklist

A poster found Cursor Auto useful for tightly defined coding jobs and, with enough direction, for running a longer coordinated session.

Done with Cursorยท Intermediate

What they did
They experimented with Cursor Auto using APM v0.4 prompts and guidance, first on small build tasks and later in a role where it acted like a session manager. That larger run began with a manager-agent kickoff and a bootstrap prompt. Whenever Auto got stuck on a bug, they started a separate debug agent in Auto to work through it.
How it went
According to the poster, Auto did well when the work stayed tightly scoped and could manage a full session if the instructions were detailed enough. The example they showed used 113,163 tokens plus another 5,922, or about 119,085 altogether, and they called that fairly token-hungry.
Tips
Break the work into compact pieces if you want Auto to stay on track. For bugs, use a separate debugging pass rather than letting the main session wander.

Try it yourself with Cursor

In Cursor Auto, work through these implementation items in [repo/project]: [item 1], [item 2], [item 3]. For the current item, outline the plan briefly, make the change, run [test command], and tell me what changed. Before any destructive step such as deleting, submitting, or sending, stop and ask for my approval. After each item, give a short recap and wait for me to confirm before moving forward.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on reddit.com โ†—

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.