strategies

Run the bundled script — POST /v2/control/strategies behind it — and report the strategies it prints in the user's own terms: what the pattern is, and what it was inferred from. Ask for a small number and report all of them; a wall of generalisations is less useful than three good ones.

node ${CLAUDE_PLUGIN_ROOT}/bin/admin.mjs strategies --data-dir "${MUBIT_CC_DATA_DIR:-${CLAUDE_PLUGIN_DATA}}" --max 5
node ${CLAUDE_PLUGIN_ROOT}/bin/admin.mjs strategies --data-dir "${MUBIT_CC_DATA_DIR:-${CLAUDE_PLUGIN_DATA}}" --max 8 --types failure,rule

--data-dir "${MUBIT_CC_DATA_DIR:-${CLAUDE_PLUGIN_DATA}}" is not optional. A Bash tool call does not inherit CLAUDE_PLUGIN_DATA — it arrives empty — so without the flag the script has to guess which of several mubit-memory* directories the host is using, and either refuses with no_run or acts on a run this session's hooks never touch. The host substitutes ${CLAUDE_PLUGIN_DATA} into this file before you read it, and the shell default around it lets a session that pins MUBIT_CC_DATA_DIR keep its pin — the same order every hook resolves in. Pass the whole expression straight through. Do not turn it into an ENV=… node … prefix: that is no longer a node command and will stop for a permission prompt.

Neither command here is an MCP tool: mubit_strategies and mubit_lessons left the default tool surface so that a session pays nothing to list them, and this script reaches the same two routes.

The one thing to be clear about

strategies is the pattern across lessons. lessons reads the individual lessons themselves.

Every other retrieval verb answers with entries. mubit_recall finds the lessons that match a question, admin.mjs lessons lists the catalogue, mubit_diagnose matches an error's shape, mubit_dereference fetches the one whose reference_id you already hold. This is the only one that answers with a shape over many of them: it clusters stored lessons into emergent strategies, so what comes back is a generalisation the server derived, not a record anybody wrote. Each line names the lesson ids the strategy was inferred from; mubit_dereference reads any of them.

That makes the choice easy in both directions. "Why do we keep breaking the build the same way?" and "what has this project learned about testing?" are strategy questions. "What did we decide about the recall budget?" is not — that has one answer, and mubit_recall finds it faster and quotes it. Do not reach for this for a single lesson; it will hand back a summary of a cluster the lesson happens to sit in. For the lessons themselves:

node ${CLAUDE_PLUGIN_ROOT}/bin/admin.mjs lessons --data-dir "${MUBIT_CC_DATA_DIR:-${CLAUDE_PLUGIN_DATA}}" [--scope run|session|global] [--limit N]