Skip to content

Add user-confirmation gate for MEMORY_INSTRUCTIONS in managed-memory skill - #261

Open
chvlsea wants to merge 1 commit into
databricks:mainfrom
chvlsea:managed-memory-confirm-instructions
Open

Add user-confirmation gate for MEMORY_INSTRUCTIONS in managed-memory skill#261
chvlsea wants to merge 1 commit into
databricks:mainfrom
chvlsea:managed-memory-confirm-instructions

Conversation

@chvlsea

@chvlsea chvlsea commented Aug 19, 2026

Copy link
Copy Markdown

What

Adds a step to the managed-memory skill (SKILL.md) requiring the agent to confirm the MEMORY_INSTRUCTIONS text with the user before proceeding to the Test phase.

After adding MEMORY_INSTRUCTIONS, the agent now:

  • Shows the user the full MEMORY_INSTRUCTIONS text it added.
  • Explains in a sentence or two what it controls — when memory is recalled (personalized questions) and what is saved (durable preferences, facts, and decisions, not passing chatter).
  • Asks via AskUserQuestion whether to keep it as-is or change it (options like "Looks good", "Adjust when it saves/recalls", "I'll rewrite it").
  • Applies whatever the user asks for, matching the wording to the scope chosen in Step 1.
  • Does not proceed to Test until the user has signed off.

Why

Memory instructions materially shape agent behavior (what it stores and surfaces about the user). Giving the user an explicit review-and-confirm gate before finalizing avoids silently baking in defaults they didn't intend.

Scope

The change is applied to the canonical root skill and all five per-template copies (byte-identical, generated by .scripts/sync-skills.py):

  • .claude/skills/managed-memory/SKILL.md (root)
  • agent-langgraph/, agent-langgraph-advanced/, agent-openai/, agent-openai-advanced/, agent-openai-agents-sdk/

This pull request and its description were written by Isaac.

…skill

Step 5 defined MEMORY_INSTRUCTIONS and jumped straight to Test, so agents
running the skill routinely skipped surfacing the memory prompt to the user.
Add an explicit confirmation step after the prompt, mirroring the Step 1
pattern that agents already honor: a bolded imperative, a mandated
AskUserQuestion, and a gate that blocks the Test step until the user signs
off. Synced to all five agent-* template copies.

Co-authored-by: Isaac
```

**Then confirm the instructions with the user before moving on — don't skip this.** Show them the full `MEMORY_INSTRUCTIONS` text you added and explain in a sentence or two what it controls: when the agent *recalls* memory (personalized questions) and what it *saves* (durable preferences, facts, and decisions — not passing chatter). **Ask with `AskUserQuestion`** whether to keep it as-is or change it — offer options like *"Looks good"*, *"Adjust when it saves/recalls"*, and *"I'll rewrite it"*. Apply whatever they ask for, matching the wording to the scope you chose in Step 1. **Don't proceed to Test until they've signed off.**

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If they pick either change option, can you continue in a normal chat message so it back and forth refines what the user wants?

nit but ...don't skip this. and Don't proceed to Test until they've signed off. say the same thing - keep the second one

@jennsun jennsun left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you confirm the workflow for updating instruction prompts is as intended after adding this skill? if you could include a recording/screenshots in PR description that would be great :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants