The Claude Code Founder Reveals The Workflow He Learned The Hard Way

Quick Overview

Boris Cherny, the creator of Claude Code, details his advanced workflow which emphasizes giving Claude a verification feedback loop, utilizing subagents for automation, sharing configuration files like CLAUDE.md and .mcp.json with his team, employing Plan Mode for complex tasks, and utilizing hooks to enforce code quality standards automatically.

Key Points: The most critical factor for great results with Claude Code is providing a verification feedback loop, which can 2-3x the quality of the final result (00:25). Cherny runs 5-10 Claudes in parallel, numbering terminal tabs 1-5 and using system notifications to track when input is needed (05:21). He heavily uses subagents like code-simplifier and verify-app to automate common workflows, viewing them as essential for most Pull Requests (08:50). For team consistency, a single CLAUDE.md file containing project instructions, structure, and conventions is checked into Git and shared across the team (02:38). For long-running tasks, he avoids and instead uses permission rules in to pre-allow safe commands (03:26). He starts complex sessions in 'Plan Mode' (shift+tab twice) to iterate on the plan with Claude before switching to 'auto-accept edits mode' for execution (05:05). He prefers using the larger Opus 4.5 model for thinking/planning because it is faster overall than smaller models like Sonnet due to less steering required (06:15).

Context: This video features Boris Cherny, the creator of Claude Code, detailing the advanced, power-user workflow he developed for using Claude as an AI coding assistant effectively. The context revolves around maximizing productivity, ensuring code quality, and enabling team-wide consistency when integrating AI into software development processes, often through custom configurations and multi-agent orchestration.

Detailed Analysis

Boris Cherny, the creator of Claude Code, outlines several advanced techniques for maximizing productivity and quality when using Claude for coding. The cornerstone of his success is providing Claude with a verification feedback loop (Tip 13, 00:25), which he states increases final output quality by 2-3x. This verification can range from running a simple bash command to testing an entire application. He runs 5-10 Claude sessions in parallel, managing them via numbered terminal tabs and system notifications (05:21). For automation, he relies on subagents like and to handle repetitive tasks common in PR workflows (08:37). Team consistency is enforced by checking a shared file into Git, which dictates project structure, tech stack, and development workflows (02:38). For security, he explicitly avoids and instead configures specific allowed commands in (03:26). When tackling large tasks, he initiates 'Plan Mode' (shift+tab twice) to collaboratively refine the plan with Claude before switching to 'auto-accept edits mode' for execution (05:05). He also notes a preference for the larger Opus 4.5 model for complex planning because, despite being slower initially, it requires less steering, resulting in a faster overall completion time compared to smaller models (06:15). Finally, he uses a hook to automatically run formatters like after code edits, ensuring code style compliance in CI (07:31).