From the Inside Claude Code - The Claude Code Ecosystem architecture map
Skip for now: config-only integrations, CI plumbing and single-file plugins
observation · low · verified
Newcomers can safely ignore the MCP Integration Plugins (each is a few lines of .mcp.json), the shared community actions and the vendor servers, which live outside this repo. Of the 27 first-party plugins, 22 are prompt-only command or skill bundles with no code paths worth tracing.
Return to these only when touching that specific plugin or integration; none of them affects how the others work.
The trail
Open on the mapMore from this board
- Optional SessionStore methods raise instead of being absent, so a change in Types reaches 13 modules
- The Lowerer is one struct spread over 38 files and 29,700 lines with no unit tests
- Day 1: start with marketplace.json, the contract everything else serves
- Every SDK module imports its exceptions from one file, _errors.py
- Partner MCP plugins launch unpinned packages on every user's machine
- PR-controlled agent config is restored from the base branch before Claude starts
- Control-protocol failures escape the SDK exception hierarchy
- Both public entry points share one control-protocol engine
- The triage and dedupe agents are boxed in identity, tools and network
- Label decisions by the triage agent leave no reason a maintainer can see
- Spend and run length are bounded at the transport
- The subprocess transport carries five responsibilities in one file
- Command-line construction is hardened against argument injection
- Every agent-driven closure has a human override before it happens
- External-PR workflows never execute contributor code
- Channel servers keep bot tokens owner-only and refuse injected pairing requests