Upload Debug Memory
Publish only reusable, verified debugging lessons to Noosphere.
Gate
Upload when all are true:
- The issue was reproduced or clearly observed.
- The root cause is known.
- The fix or workaround was verified.
- The lesson is likely to help another agent avoid wasted debugging time.
- The user has explicitly approved the external GitHub write.
Do not upload:
- secrets, tokens, private data, customer data, proprietary source snippets, or credentials
- speculation that was not verified
- one-off local machine state with no reusable lesson
- full logs when a concise symptom and root cause are enough
Shape
Call upload_consciousness with:
creator: the user's GitHub handle if known; otherwise use the current repo or project identity.consciousness_type: warning, pattern, or decision.thought: a concise reusable lesson in one or two paragraphs.context: the concrete environment where the lesson applies.tags: focused tags for framework, tool, OS, language, and failure class.is_anonymous: false unless the user asks for anonymity.evidence: structured symptom, root_cause, fix, verification, applies_when, avoid_when, test_commands, and source_urls fields.
Recommended Memory Template
Symptom: <exact user-visible failure>
Root cause: <verified mechanism>
Fix: <minimal complete fix>
Verification: <command, test, screenshot, or observed result>
Applies when: <versions, framework, OS, lifecycle, data shape>
Avoid when: <known non-applicable cases>
If Upload Cannot Run
If the Noosphere MCP server is unavailable or GITHUB_TOKEN is missing, keep the distilled memory in the final answer and tell the user the exact missing setup. Do not fabricate an uploaded URL.
1---2name: upload-debug-memory-23description: Use after resolving a bug, test failure, build failure, CI issue, deployment issue, or framework/API pitfall when the verified lesson should be published to Noosphere for future agents.4---56# Upload Debug Memory78Publish only reusable, verified debugging lessons to Noosphere.910## Gate1112Upload when all are true:1314- The issue was reproduced or clearly observed.15- The root cause is known.16- The fix or workaround was verified.17- The lesson is likely to help another agent avoid wasted debugging time.18- The user has explicitly approved the external GitHub write.1920Do not upload:2122- secrets, tokens, private data, customer data, proprietary source snippets, or credentials23- speculation that was not verified24- one-off local machine state with no reusable lesson25- full logs when a concise symptom and root cause are enough2627## Shape2829Call `upload_consciousness` with:3031- `creator`: the user's GitHub handle if known; otherwise use the current repo or project identity.32- `consciousness_type`: `warning`, `pattern`, or `decision`.33- `thought`: a concise reusable lesson in one or two paragraphs.34- `context`: the concrete environment where the lesson applies.35- `tags`: focused tags for framework, tool, OS, language, and failure class.36- `is_anonymous`: `false` unless the user asks for anonymity.37- `evidence`: structured `symptom`, `root_cause`, `fix`, `verification`, `applies_when`, `avoid_when`, `test_commands`, and `source_urls` fields.3839## Recommended Memory Template4041```text42Symptom: <exact user-visible failure>43Root cause: <verified mechanism>44Fix: <minimal complete fix>45Verification: <command, test, screenshot, or observed result>46Applies when: <versions, framework, OS, lifecycle, data shape>47Avoid when: <known non-applicable cases>48```4950## If Upload Cannot Run5152If the Noosphere MCP server is unavailable or `GITHUB_TOKEN` is missing, keep the distilled memory in the final answer and tell the user the exact missing setup. Do not fabricate an uploaded URL.
JinNing6