From the Inside Claude Code - The Claude Code Ecosystem architecture map
Every agent-driven closure has a human override before it happens
strength · low · verified
Duplicate comments say the issue closes in 3 days, and auto-close-duplicates skips any issue whose author reacted thumbs-down. The sweep skips lifecycle closures when a human commented after the label, triage removes stale and autoclose on new human comments, and remove-autoclose-label clears autoclose on any comment.
Impact: Authors can stop a wrong closure with one reaction or comment.
The escape hatch depends on the author noticing within 3 to 7 days; it does not cover issues whose author has gone quiet.
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
- 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