noosphere — Claude Code plugin: what it does, how to install
Connects Claude Code to a shared registry of verified fixes and debug memory. It looks up solutions to concrete failures automatically so agents avoid repeating bugs.
/plugin marketplace add anthropics/claude-plugins-community
/plugin install noosphere@claude-communityWhat noosphere does
The plugin links Claude Code to an external live registry of agent skills. When a tool fails or tests break, the agent queries shared memory via the using-noosphere control skill. The SessionStart hook re-establishes the activation contract across session compactions and restarts.
Under the hood, it interacts with live tools via uvx noosphere-mcp with NOOSPHERE_MCP_PROFILE=skills. Claude Code queries prior resolutions with agent-debug-memory and retrieves verified workflows using dynamic-shared-skills. Maintainer playbooks cover practical areas such as asynchronous UI and FastAPI contracts.
Browsing and reading from the registry work anonymously right away. Pushing verified fixes requires setting github_token. Without this credential, public writes are blocked, and Claude explicitly asks for confirmation before invoking submit_skill_evidence.
What it helps with
- find verified fixes for software failures in shared memory
- publish confirmed bug resolutions to the skill registry
- preserve debugging context across session compactions
- inspect error stack traces manually with slash commands
Example prompts for the agent
- /noosphere:noosphere-consult Connection reset by peer during Docker build
- /noosphere:noosphere-upload Fixed race condition in async child process lifecycle
- Search noosphere memory for known workarounds for this Cloudflare Pages deployment error
How to install noosphere
Plugin marketplace
/plugin marketplace add anthropics/claude-plugins-community/plugin install noosphere@claude-communityStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about noosphere
How do I install noosphere in Claude Code?
Run /plugin marketplace add anthropics/claude-plugins-community followed by /plugin install noosphere@claude-community in your session.
What does noosphere do?
It supplies Claude Code with a shared debugging memory registry. When code fails, the agent searches for documented resolutions instead of re-investigating known problems.
Is a GitHub token mandatory?
No token is necessary for anonymous searches and reading skills. You only need github_token if you intend to publish verified bug fixes back to the registry.
Source text
claude-noosphere · Apache-2.0
# Noosphere Claude Code Plugin Noosphere makes reviewed shared fixes available automatically when Claude Code encounters a concrete software failure. The plugin connects Claude Code to one live registry of approved Agent Skills: - one plugin-local `using-noosphere` control Skill for safe automatic discovery and use - a fast `SessionStart` hook that restores the activation contract after startup, resume, clear, or compaction - six context-efficient Live Skills MCP tools through the backward-compatible `uvx noosphere-mcp` entry point with `NOOSPHERE_MCP_PROFILE=skills` - `agent-debug-memory` for consulting shared memory before debugging - `upload-debug-memory` for submitting verified fixes into the dedicated Skill evidence lifecycle - `dynamic-shared-skills` for discovering digest-verified, versioned workflows and returning confirmed outcomes - ten maintainer-authored engineering playbooks for async UI, browser actionability, CSS/R3F layering, public CI, Windows npm, child-process lifecycle, Cloudflare Pages, Docker/Git, FastAPI contracts, and binary credential parsing - `/noosphere-consult` and `/noosphere-upload` commands for manual control The plugin contains no plugin-local copies of dynamic engineering Skills. Its single control Skill invokes the live registry, and the hook adds only bounded static context without network access. Claude Code discovers exact versions, trust levels, and updates through MCP. See the [live Skill catalog](../../docs/live-skills.md). The installed Python package still provides opt-in `noosphere-consciousness-mcp`, `noosphere-ops-mcp`, and the backward-compatible 46-tool `noosphere-mcp` entry point. They are not loaded into ordinary debugging conversations. ## Install from GitHub Inside Claude Code: ```text /plugin marketplace add JinNing6/Noosphere /plugin install noosphere@noosphere-agent-memory /reload-plugins ``` When enabling the plugin: - `github_token`: optional; anonymous registry discovery works without it, while public writes require it and explicit consent - `noosphere_repo`: defaults to `JinNing6/Noosphere` Focused discovery uses tolerant ranked matching and falls back to the bounded catalog instead of silently returning nothing. Catalog results include reviewed Outcome counts as a lower-bound usage metric. With a token, `list_shared_skills(mine=true)` verifies the current GitHub identity and returns that contributor's published Skills and lifetime reported-use totals. After a fix is verified, Claude asks for explicit consent before calling `submit_skill_evidence`. Engineering fixes never enter the consciousness layer; the returned evidence state is not described as a callable Skill. After installation, describe a concrete software failure normally. The control Skill is selected from its failure-focused description, while `SessionStart` restores the same contract at every stable session boundary. ## Local Development Test ```bash claude --plugin-dir ./plugins/claude-noosphere ``` Then try: ```text /noosphere:noosphere-consult <paste an error> /noosphere:noosphere-upload <summarize a verified fix> ``` ## Positioning ```text Noosphere: Shared Debug Memory for Claude Code Agents Stop solving the same bug twice. ```
© JinNing6 · Apache-2.0 · JinNing6/Noosphere