Repository navigation
docs: call pin_map only when a turn needs memory - #262
Merged
Merged
Conversation
Reword the pin_map tool description, CLI/help text, README, guides and in-repo skills: call only when a turn needs memory, with a real cue; ask for the empty-cue outline once at job start. Behaviour unchanged.
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.
Why
Owner ask: bots call
pin_mapevery turn, usually with an empty cue, and get only a session outline back. That costs a round trip and tokens for nothing they use. The cause is the tool description and matching in-repo advice ("each turn call this with a cue, or empty-q outline"). This PR rewords that advice: callpin_maponly when a turn needs something from memory, always with a real cue; if an outline helps, ask for it once at job start.Wording only. Empty cue still returns the 0.11 session outline (MN-REQ-04.9 unchanged). No requirement ids or implemented flags changed.
What changed
pin_mapMCP docstring (the live tool description), CLIquery pin-mapdocstring,help_text.py.parts/memnet-mcp/README.md, AGENTS.md, LLM-GUIDE, SHAPE, gql-wire-profile, multi-agent-sessions, application notes, in-repo.cursor/skills.[Unreleased]### Changednote.tests/test_mcp.pynow asserts the new phrases and fails if the old advice returns.Live MCP clients see the new text only after a package release and a roll of memnet-mcp.
Old pin_map description
New pin_map description
Tests
pytest tests/test_session_outline.py tests/test_mcp.py tests/test_goldfish_caller.py tests/test_goldfish_paradox.py tests/test_pin_map_export.py tests/test_identity_cut.py: 47 passed.pytest: no failures.ruff checkandruff format --checkon engine, MCP and tests: clean.