Repository navigation
fix(session): hide persisted reminders in resume history - #333
Merged
Brian Krabach (bkrabach) merged 1 commit intoSep 8, 2026
Merged
Conversation
Generated with Amplifier Co-Authored-By: Amplifier <240397093+microsoft-amplifier@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Persisted system reminders are needed for resumed context but should not appear as conversation history or consume the visible history window. Human-authored, malformed, mixed, and unflagged content remains visible.
Verification
uv run --with truststore==0.10.4 pytest -q— 2113 passed, 1 skipped, 13 deselected, 1 xfailed.amplifier session resumeand--replayexited 0; fixture-backed checks covered hidden identified reminders, visible human/unflagged quotes, default-window behavior, unchanged transcript bytes, and retained resume context. This validates the fixture-shim scope; it does not claim live vendor or full default-bundle coverage.Compatibility
No breaking changes. No provider requests, version changes, global CLI behavior, Foundation changes, or workspace-root changes.