Week 4 · Guide 1 of 5

Context & Memory

Fix a Mistake Your Agent Keeps Making

Field Guide

  • 20–30 minGuided walkthrough

When your agent makes the same mistake in chat after chat, correcting it again in the chat isn’t a lasting fix, because the chat doesn’t change your files. Find the one file where the fix belongs, change the smallest thing there and check it on the example that showed the mistake.

You’ll leave with

One fix in the file where it belongs, saved as your new master copy, and the example that showed the mistake coming back right.

What You Need for This Guide

  • A mistake your agent keeps making, and a request that showed it.
  • Your saved , Communication Style Guide, Safety & Security Rules and any Reusable Workflow Card, as many as you have.
  • Your approved AI tool, and My Agent Files or another folder you can find again.

Create your Agent Profile

Build your Communication Style Guide

Build your Safety & Security Rules

Build Your Reusable Workflow Card

Choose the tool you’re allowed to use

Your approved tool

The tool your company approved.

Pick your approved tool above to see the steps and screenshots for it.

Start guide
5 steps · At your own pace
About saved progress

No account needed. Checkmarks save on this browser and device when browser storage is available. If storage is blocked or full, new checkmarks last until you reload or close this page. Progress doesn’t sync to other browsers or devices. Clearing this site’s browser data removes it, and private browsing may not keep it after you close the window.

Step

Name the mistake and keep the example that shows it

Pick one mistake your agent makes again in new chats, even after you’ve corrected it. A correction in a chat only reaches that chat, and the next one starts from your files again. Even a correction your tool remembers on its own isn’t your master copy. It’s a second copy your files don’t show, and two copies of one rule eventually disagree. Your agent might keep:

  • signing off with “Best regards” when you always write “Thanks”
  • filling in an owner or a date your notes don’t give
  • describing your role as a manager when you coordinate the work
  • putting the summary of your weekly update at the end instead of the top

Note in My Agent Files what the agent does, what you want instead and the example that showed it: the request you sent and its source, prepared the way the data rules say. You’ll send the same example again in step 5.

If nothing comes to mind, look back through recent chats for a correction you typed more than once. If there isn’t one, your files are doing their job, so come back when you catch yourself correcting the same thing twice.

Step

Find what your files already say about it

Before you add anything, find out whether a file already covers the mistake. Often one does, with a line that’s vague, in the wrong file or contradicted somewhere else.

  1. Start a new chat in the Project or Notebook that holds your files, because that’s where an out-of-date copy would show up. If you attach your files to each chat instead, attach them to a new chat. Fill in the prompt’s three lines from your note and send it. The agent quotes what it finds and changes nothing.

    Find what my files say about a mistake
    My agent keeps making the same mistake. Before I change anything, I want to find where my files already deal with it.
    
    The mistake: [what the agent does, in a sentence]
    What I want instead: [what it should do]
    The request that showed it: [paste the request you sent, or describe it]
    
    Read my files attached to this chat or saved in this Project or Notebook: my Agent Profile, Communication Style Guide, Safety & Security Rules and any Reusable Workflow Card. First, list the files you can see, with each one's version number if it has one.
    
    1. Quote each line in my files that directly covers this mistake, word for word, most direct first, and name the file and section it's in. Leave out lines that only touch on it. If nothing covers it, say so.
    2. Quote anything in my request above that covers it too.
    3. Say whether any of these lines disagree with each other. If you can see two versions of the same file, say so.
    
    Use only what my files and my request say. Do not suggest a fix, and do not change any file.
  2. Find each quoted line in your master files yourself, because the agent can misquote a line or miss one. If it quotes wording your master file no longer has, lists two versions of a file or leaves out a file you saved there, your saved home is out of date, and that alone can explain the mistake. Put your master file there in its place, as in step 5, and send your example in a new chat. If it now comes back right, the fix was already in the right file and you’re finished.

  3. Otherwise, decide which case fits. Step 3 shows where each kind of line belongs.

    • Nothing covers it. You need one new line.
    • A line covers it, but vaguely or in the wrong file. Change or move that line.
    • Two lines disagree, such as five bullets in your card and ten in your request. Decide which one you want, keep that wording in its best home and delete the other copy, from its file or from the request you send.
    • A clear line covers it and the agent still missed it. Make that line more specific, such as naming the case it missed.

Step

Choose the one best home for the fix

Each instruction needs one best home, at the highest level where it’s reusable, so you only ever change it in one place. Ask what the fix is about:

  • Policy, privacy or security, or how information is handled, checked or approved: your Safety & Security Rules, in the section it fits, such as My Organization-Specific Rules. A fix here adds or tightens a rule.
  • Background about you and your work, such as your role, team or projects: your .
  • How you sound, such as tone, sign-offs, length and formatting: your Communication Style Guide.
  • How one recurring piece of work is done: that work’s Reusable Workflow Card, in the part that explains the miss, as step 5 of Build Your Reusable Workflow Card shows.
  • Only this one time: no file. It goes in that run’s Context Sandwich, the Task, Context, Constraints and Output Check you write for the work in front of you.

When a fix could fit two homes, choose the one that covers every time the mistake matters, and nothing it shouldn’t. If its file doesn’t exist yet, build it first with the guide linked at the top.

Write the smallest change in your note: one line to add, one line to change and what it should say, or one copy to delete. Word it as an instruction your agent can follow, such as “If my notes don’t name an owner, write Owner Needed”, rather than “Be more careful with owners.”

Step

Make the change in your master file

Make the change in the file itself, because that’s your master copy. If the file has its own VERSIONS section, such as the RULES VERSIONS you may have added to your rules in Week 3, the prompt follows it. Otherwise it changes only your line and the version number.

  1. Start a new chat outside your Project or Notebook, and attach or paste the file from My Agent Files, so the change starts from your master copy. Fill in the prompt’s lines from your note and send it.

    Update one file with one fix
    Give me the next version of one of my files, with one change.
    
    File: [the file's name, such as My Communication Style Guide]
    Change: [the line to add, the line to change and what it should say now, or the line to delete]
    Where: [the section it goes in, such as Output, if you know]
    Why: [the mistake this fixes, in a sentence]
    
    The file is attached to this chat or pasted at the end. It's my master copy, so put the change in the file, not in your memory.
    
    1. Make only this change, in my words, in that section, or where it fits best if I didn't say. If I asked you to add a line, add it as a new line and leave the lines around it as they are. Keep every other line and section word for word, in the same order. Do not add rules I didn't give you.
    2. If the change would contradict or weaken a line already in the file, other than a line I asked you to change or delete, stop before writing anything: quote both and ask me which one to keep.
    3. If the file has its own VERSIONS section, such as PROFILE VERSIONS, STYLE GUIDE VERSIONS or RULES VERSIONS, follow it to create the next version. If it has none, change nothing else except the version number: raise any number in its title by one, and name the new file with the next version number, one higher than the number in its title or filename, or v2 if it has none.
    4. Give me the entire file as one downloadable plain-text file. If you can't create files, put all of it in one code block with the filename above it.
    5. Show what changed in a table: Section, What changed, Why.
    
    Do not tell me my saved setup is updated. I'll replace the file myself.
    
    [paste the file here if it isn't attached]
  2. Before you save, scroll through the new file and check that every section of your old one is still there, because the table is the agent’s own account of what it did. Then check the What changed table. It should show your change, in your words and in the section it fits, and nothing else apart from a version line and history entry. If the agent quotes a line your change contradicts, tell it in the same chat which one to keep. If it changed anything else, ask for the file again with only your change.

  3. Save the new file in My Agent Files under the filename the agent gave, and keep the old one. The new file is your master copy now. To delete a copy from a second file, send the prompt again for that file.

Step

Replace the file and test the same example

  1. Put the new file wherever your agent reads it. In a Project or Notebook, remove the old file and add the new one the way you first added it, so only one version is there. If you attach your files to each chat, attach the new one from now on. If you’ve made a skill from your Workflow Card, it still holds the old card, so update it too before you test.

  2. Start a new chat in your Project or Notebook, or with your files attached, and send the same request with the same source from your note. That example showed the mistake, so it’s the one that shows whether your fix worked.

  3. Check for the mistake you named, and look over the rest too, because a fix shouldn’t make anything else worse. If the mistake comes back, check that only the new file is in your saved home, then make your line more specific and repeat step 4. If something else got worse, send the step 4 prompt again with your new file, and change your line to a smaller one.

Save both prompts in My Agent Files and edit your copies to fit how you work. The next time you type the same correction twice, run these steps again with the new mistake.

Fix a Mistake Your Agent Keeps Making

Confirm your result

Confirm the outcomes below to finish this guide.

Final checks

Your fix is in the one file where it belongs, saved in My Agent Files as your new master copy, with the old version kept.

The example that showed the mistake, sent again in a new chat, now comes back right.

Provide Feedback

Thanks. That went straight to the people who write these guides.

Next in Week 4

Keep Your Workflow Card and Skill in Step

Continue in the suggested order, or choose another guide for your task.

View Week 4 guides