Last updated:
Quick answer
Write the goal and what done looks like in 3 lines before the run. Every few steps, have the agent restate the goal, list what it changed, and compare against the goal. Set a step limit and a checkpoint where it stops for you before anything irreversible.
Free PDF
Get this setup as a PDF
Confirm your email and we'll open a print-ready copy of this setup you can save as a PDF. You also get the free starter pack and one setup a week. Unsubscribe anytime.
Already a subscriber? Unlock it on this device
At a glance
All outcome figures are estimates from cited sources, not independent verification by us.
- What it is allowed to do
- Read-only
Only reads, researches, or summarizes. It never drafts outbound content or changes anything.
- Time saved (estimate)
- Saves rework on long runs; about 10 minutes to set up.
- Difficulty
- Intermediate
- Tools needed
- Claude, ChatGPT, Grok Bot
- Typical cost
- Prices: Not stated in sources.
Reviewed Nov 2, 2026
Basis (estimate): Estimate only: based on the steps above, not timed.
What does this setup do?
Add a written goal, regular goal checks, a step limit and a stop-for-review checkpoint to long agent runs, so drift shows up mid-run instead of at the end.
Who is it for?
Owners running agents on long tasks, such as cleaning a list, building a report or updating many records, who find the final result is not what they meant.
How do you set it up?
Tools
- Your agent's task instructions
- A 3-line goal
- A step or time limit
Steps
- Before the run, write the goal, what done looks like, and what must not change, in 3 lines.
- Add the checkpoint rules from the prompt below to the task.
- Set a stopping condition, such as a maximum number of steps. Anthropic's guide to building agents describes checking progress against real results at each step, pausing for human feedback at checkpoints, and using stopping conditions like iteration limits.
- At each checkpoint, read the agent's goal check. If it has drifted, stop and restate the goal.
- When a tool or setting changed recently, run a small test task first and compare with a past result.
- Keep the 3-line goal with the output so you can check the end result against it.
Example output
Illustrative. Your results will differ.
- Check at step 10: goal = remove duplicate customers. Changed: merged 14 records (yes), reformatted all phone numbers (NO, not part of the goal). Pausing for you.
Where to paste this prompt
Claude → Project knowledge & custom instructions
Copy-paste prompt
Adapt bracketed fields to your situation.
Add these rules to this task:
Goal: [ONE LINE]
Done looks like: [ONE LINE]
Must not change: [ONE LINE]
1. Every [5] steps, stop and report: the goal in your own words, what you changed since the last check, and whether each change serves the goal (yes or no, with a reason).
2. If any answer is no, or you are unsure, pause and ask me before continuing.
3. Stop after [30] steps in total and report, even if not finished.
4. Before anything that cannot be undone, stop and ask.Newsletter
Get the free starter pack
Free starter pack with five beginner copy-paste prompts after you confirm, plus one researched setup in your inbox each week. Unsubscribe anytime.
What usually goes wrong?
Where agents tend to stall on this job. More patterns in Where AI gets stuck.
- No written goal, so there is nothing to check against.
- Reading only the final output.
- Letting the agent judge its own drift without evidence of what it changed.
Which chat tools work with this prompt?
Paste the prompt into any of these assistants (free or paid tiers).
- Claude
- ChatGPT
- Grok Bot
Common questions
- Why does my agent drift on long tasks?
- Small reasonable steps add up to a result you did not want, especially without a written goal to check against.
- How do I catch it early?
- Have it restate the goal and list its changes every few steps, and pause when something does not serve the goal.
- Should it stop on its own?
- Yes: set a step limit and a stop before anything irreversible.
What tips make it smoother?
- The 'must not change' line catches the most drift.
- Short checkpoints early, longer gaps once it is on track.
- A tool update can change behavior with no error; test small first.
Where do the claims come from?
Summaries use public sources linked below, not independent verification. How setups are picked.
- Read Anthropic’s write-up (www.anthropic.com)
Anthropic: Building effective agents: agents check progress against ground truth such as tool results at each step, can pause for human feedback at checkpoints or when blocked, and use stopping conditions such as a maximum number of iterations (read 2026-11-02 from a search result summary of the page)
Related setups
- Check your agent did the follow-up it promised
Turn every follow-up your AI agent promises into a dated task, run a daily check of what was due, and get a short list of anything that slipped.
- Set guardrails before an AI agent gets access
Write a one-page rulebook for an AI agent before it touches your accounts: what it can read, what it can only draft, what always needs your approval, and what it must never do.
- Clean up your agent's long-term memory
Review your AI agent's long-term memory monthly, delete stale facts, date the ones you keep, and stop task details from leaking into new work.