From the Inside Claude Code - The Claude Code Ecosystem architecture map
Day 1: start with marketplace.json, the contract everything else serves
observation · high · verified
The Marketplace Catalog is the most connected part of the system. Claude Code installs from it, it lists every first-party, channel and integration plugin by source path or pinned git SHA, and three of the four CI jobs read or rewrite it. Reading .claude-plugin/marketplace.json first explains why the rest of the repo exists.
Look at one local entry (./plugins/...), one external entry (git-subdir with ref and sha), and the renames map. Those three shapes cover how every plugin reaches users.
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
- 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
- Skip for now: config-only integrations, CI plumbing and single-file plugins
- External-PR workflows never execute contributor code
- Channel servers keep bot tokens owner-only and refuse injected pairing requests