Agent Debug Memory
Use Noosphere as the shared debugging memory layer before and after substantial debugging work.
Before Fixing
- Extract a precise query from the failure:
- exact error text, stack frame, failing command, failing test, or visible symptom
- framework, package, runtime, OS, database, browser, or deployment context
- the user's concrete goal and any constraints already stated
- Call the Noosphere MCP tool
consult_noosphere with that query.
- If useful tags are obvious, include focused
topic_tags, such as react, vite, typescript, mcp, github-actions, async-ui, codex, claude-code, windows, or the library name.
- Treat returned fragments as leads, not truth. Verify against the local codebase, official docs when needed, and runnable tests or reproduction steps.
During Fixing
- Prefer the smallest complete fix that addresses the verified root cause.
- Do not copy a Noosphere fragment blindly if the local environment, version, lifecycle, or data flow differs.
- Keep secrets, tokens, private customer data, private code snippets, and credentials out of tool calls and uploaded memories.
After Fixing
When the outcome is verified, the lesson is reusable, and the user explicitly approves the external GitHub write, upload a distilled memory with upload_consciousness.
Use:
consciousness_type: "warning" for pitfalls, footguns, version traps, and failure modes.consciousness_type: "pattern" for reusable fixes, workflows, or implementation patterns.consciousness_type: "decision" for tradeoff-heavy engineering choices.
The uploaded memory should include:
- the symptom or failing command
- the root cause
- the fix
- the verification command or evidence
- version or environment details that prevent false reuse
Keep the memory concise and general enough for another agent to reuse.
Completion Standard
Do not claim the fix is complete until local verification has passed or you have clearly stated what could not be run. Public registry reads work anonymously; uploading evidence or outcomes requires a GitHub token in the Agent's Noosphere MCP environment.
1---2name: agent-debug-memory3description: Use when debugging code, tests, builds, deployments, CI failures, runtime errors, framework issues, API migrations, or UI state bugs where a coding Agent should consult Noosphere shared memory before fixing and upload the verified lesson afterward.4---56# Agent Debug Memory78Use Noosphere as the shared debugging memory layer before and after substantial debugging work.910## Before Fixing11121. Extract a precise query from the failure:13 - exact error text, stack frame, failing command, failing test, or visible symptom14 - framework, package, runtime, OS, database, browser, or deployment context15 - the user's concrete goal and any constraints already stated162. Call the Noosphere MCP tool `consult_noosphere` with that query.173. If useful tags are obvious, include focused `topic_tags`, such as `react`, `vite`, `typescript`, `mcp`, `github-actions`, `async-ui`, `codex`, `claude-code`, `windows`, or the library name.184. Treat returned fragments as leads, not truth. Verify against the local codebase, official docs when needed, and runnable tests or reproduction steps.1920## During Fixing2122- Prefer the smallest complete fix that addresses the verified root cause.23- Do not copy a Noosphere fragment blindly if the local environment, version, lifecycle, or data flow differs.24- Keep secrets, tokens, private customer data, private code snippets, and credentials out of tool calls and uploaded memories.2526## After Fixing2728When the outcome is verified, the lesson is reusable, and the user explicitly approves the external GitHub write, upload a distilled memory with `upload_consciousness`.2930Use:3132- `consciousness_type: "warning"` for pitfalls, footguns, version traps, and failure modes.33- `consciousness_type: "pattern"` for reusable fixes, workflows, or implementation patterns.34- `consciousness_type: "decision"` for tradeoff-heavy engineering choices.3536The uploaded memory should include:3738- the symptom or failing command39- the root cause40- the fix41- the verification command or evidence42- version or environment details that prevent false reuse4344Keep the memory concise and general enough for another agent to reuse.4546## Completion Standard4748Do not claim the fix is complete until local verification has passed or you have clearly stated what could not be run. Public registry reads work anonymously; uploading evidence or outcomes requires a GitHub token in the Agent's Noosphere MCP environment.
JinNing6