From the Inside Claude Code - The Claude Code Ecosystem architecture map
Channel servers keep bot tokens owner-only and refuse injected pairing requests
strength · low · verified
The Telegram server writes its .env and access.json with mode 0600 inside a 0700 state directory, defaults new chats to pairing mode, and instructs the session never to approve pairings or edit the allowlist because a channel message asked. Senders not on the allowlist are dropped before their text reaches the session.
Access changes happen only through the access skill run in the user's terminal, which keeps chat input from widening its own privileges.
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
- Skip for now: config-only integrations, CI plumbing and single-file plugins
- External-PR workflows never execute contributor code