Tier 1 · Claude Code internals Claude Code internals · fetched 2026-07-02

claude-code-book (SCUTBrothers)

A second book-length Chinese treatment of Claude Code's source ('Understanding Claude Code In Depth') with a compiled PDF and LaTeX sources. Focuses on turning the complex system into reusable engineering knowledge: source structure, runtime mechanics, permissions and extension points, security and context strategy.

View source on GitHub

Key takeaways

01
Dedicated chapters on the permission model and extension points
02
Treats security and context strategy as first-class harness concerns
03
Complements the Orange Book with a different chapter decomposition

Flows built on this research

Harness Engineering

Hook a Permission Layer onto Dangerous Tools

Intercept dangerous tool calls with a hook layer: pattern rules, approval gates, and blocks that the model cannot talk its way past.

4 steps · 60-90 minutes

Harness Engineering

Design the Permission Approval UX

Design approval prompts users actually read: diffs, risk framing, scoped grants, and pacing that prevents approval fatigue.

4 steps · 60-90 minutes

Harness Engineering

Sandbox Untrusted Code Execution

Contain what your agent runs: isolated execution environments with resource limits, network policy, and workspace mounting done right.

4 steps · 120-180 minutes

From the archive

Verbatim excerpts mined from our local archive of this repository — the prompts, schemas, and patterns worth stealing.

Prompt

A system prompt for verifiable technical writing

You are contributing to a technical book based on the Claude Code source. Your primary goal is not to 'write like a book' but to write things that are verifiable, mergeable, and reviewable.

Strictly follow:
1. Answer only from this round's provided source scope, the established glossary, and archived material.
2. If evidence is insufficient, explicitly write 'to be verified' - never fill in implementation details that don't exist.
3. Tag every key claim with [S]/[I]/[E]/[Q] (source/inference/experience/question).
4. Output outline, plan, material needs, and citation points BEFORE the body text.
5. Explain engineering implementation; no marketing language, no vague praise.

[translated] An anti-hallucination prompt for long-form generation: evidence tags on every claim and a mandatory 'to be verified' escape hatch.

README.md