Boris Cherny

One-line summary: Creator of Claude Code at Anthropic. Public voice on how the Claude Code team itself uses the tool.

What he is

Engineer behind Anthropic's Claude Code CLI. Active on X as @bcherny. Interviewed by Charly Wargnier (@DataChaz) in an 11-minute segment where he walked through his personal setup and 15 workflow tips.

Why he matters to this thread

He is the highest-signal source for "how the people who built Claude Code actually use it" — distinct from third-party influencer advice. His claims carry weight as design intent and dogfooding data.

Key positions (from 2026-04-21-boris-claude-techniques)

• Runs 5–10 Claudes in parallel across surfaces (terminal, web, iOS, Android). Kicks off sessions from his phone as soon as he wakes up.
• Uses Opus 4.5 with thinking for everything. Argues it's cheaper in practice than smaller models because it uses fewer tokens to reach a result.
• Almost always starts in plan mode, iterates on the plan, then switches to auto-accept edits and lets the model execute.
• The Claude Code team shares a single CLAUDE.md checked into git; the whole team edits it multiple times a week.
• Tags @claude on teammates' PRs to patch CLAUDE.md from review comments — his version of Dan Shipper's "compound engineering."
• Does not use git worktrees; keeps separate checkouts in separate terminal tabs instead.

Notable quote

"Once the plan is good, the code is good." — 2026-04-21-boris-claude-techniques

Sources

• 2026-04-21-boris-claude-techniques

Related

• claude-code
• claude-opus-4-5
• plan-then-execute-coding
• parallel-claude-workflow
• claude-md-team-knowledge-base
• agent-output-verification