URL copied — paste it as a website source in a new notebook
Summary
Boris Cherny, creator and head of Claude Code at Anthropic, shares a comprehensive thread revealing 15 hidden and under-utilized features of Claude Code that he uses daily in his own workflow. The thread has generated significant viral buzz in the developer community, with industry observers calling it a "watershed moment" for AI-powered development tools.
Cherny emphasizes that Claude Code ships with powerful features that many developers don't know exist or underutilize. Rather than requiring extensive customization, he argues that Claude Code "works great out of the box," but knowing these advanced features can dramatically enhance productivity. The features range from mobile access and cross-device session management, to advanced automation with loops and scheduled tasks, to sophisticated development patterns like parallel git worktrees and verification loops.
The most striking feature Cherny highlights is the ability to give Claude ways to verify its own output—whether through browser automation, test suites, or end-to-end testing. He claims this verification loop improves code quality by "2-3x," fundamentally changing how developers should think about AI-assisted coding: not as a text generator, but as a testing and iterating agent that can write, execute, and refine its own work until it's production-ready.
Cherny's personal workflow, also shared in earlier threads, demonstrates the power of these features: he runs 5 parallel Claude instances simultaneously, each in separate git worktrees, shipping 20-30 pull requests per day. This approach has resonated deeply with the developer community, with VentureBeat describing it as turning "coding into a real-time strategy game," where the engineer acts as a fleet commander rather than a typist.
The thread sparked a broader conversation about the future of software engineering, with developers sharing implementations of Cherny's advice and creating tools (like "howborisusesclaudecode.com") to aggregate and teach his workflows to others.
Key Takeaways
Claude Code includes a native mobile app (iOS/Android) that allows developers to write and edit code from their phones, with seamless /teleport integration to move sessions between mobile, web, desktop, and terminal environments.
/loop and /schedule are powerful features for automating repetitive tasks—Cherny uses loops to continuously babysit PRs, gather slack feedback, clean up post-merge code review comments, and prune stale PRs, with loops running for up to a week at a time.
Hooks enable deterministic logic execution at key points in the agent lifecycle (SessionStart, PreToolUse, PermissionRequest, Stop), allowing developers to dynamically load context, log commands, route permissions, or keep Claude actively working.
Verification loops—where Claude automatically tests its own output via browser automation, test suites, or end-to-end testing—improve code quality by 2-3x and are the 'real unlock' for AI-generated code, fundamentally changing how to approach AI-assisted development.
Git worktrees are essential for parallel work: Cherny runs dozens of Claude instances simultaneously, each in a separate worktree, enabling massive throughput. The /batch feature can fan out work to dozens or hundreds of parallel agents for large code migrations.
The Chrome extension for frontend work is critical for web development: it provides browser access so Claude can write code, test the UI, iterate, and verify that the UX feels good—something impossible without direct verification.
Custom agents and slash commands can be checked into a project repository and used dozens of times daily, automating complex multi-step workflows like /commit-push-pr or specialized subagents for code simplification and verification.
/btw enables side queries while the main agent continues working, providing a lightweight way to ask quick questions without interrupting ongoing tasks.
The --bare flag accelerates SDK startup by up to 10x in non-interactive usage by skipping automatic discovery of CLAUDE.md files, settings, and MCPs—important for scaling to hundreds or thousands of parallel agents.
Cowork Dispatch is a secure remote control for Claude Desktop that can manage Slack, emails, and computer tasks from anywhere, blurring the line between coding and task automation for a truly distributed workflow.
About
Author: Boris Cherny
Publication: X (Twitter)
Published: 2026-03 (early March 2026)
Sentiment / Tone
Professionally enthusiastic and matter-of-fact; Cherny adopts an educator's tone rather than a salesperson's pitch. He consistently emphasizes that "there is no one right way to use Claude Code" and encourages experimentation, avoiding dogmatism. His writing reflects confidence born from hands-on daily use—he presents features not as theoretical possibilities but as practical tools he personally relies on, often citing specific automation routines (like /babysit and /pr-pruner) he runs constantly. There's an underlying current of excitement about the paradigm shift from developer-as-typist to developer-as-orchestrator, but it's grounded and pragmatic rather than hype-driven. The tone is also inclusive and encouraging—Cherny positions himself as sharing learnings from the team, not gatekeeping expertise.
Pragmatic Engineer: Building Claude Code with Boris Cherny Deep technical discussion with Gergely Orosz covering how Claude Code's architecture actually works, Cherny's parallel agent workflow, and his learnings from 5 years as Principal Engineer at Meta
Developing.dev: Boris Cherny on How His Career Grew Career retrospective explaining how Cherny went from startup founder at 18 to Principal Engineer at Meta to creator of Claude Code, with insights on earning promotions and building credibility
How Boris Uses Claude Code (Interactive Collection) Comprehensive aggregation of all 42+ tips Cherny shared across five Twitter threads (January-February 2026), organized by theme with direct links to each tip's original thread
Research Notes
**Author credibility**: Boris Cherny is exceptionally well-positioned to speak about Claude Code—he created it from a side project in September 2024 and is now the head of the product at Anthropic. He previously spent five years at Meta as a Principal Engineer (IC8, the second-highest individual contributor level), leading major projects and eventually managing infrastructure for hundreds of engineers. He's also the author of "Programming TypeScript" (published 2019, well-regarded in the community), demonstrating deep expertise in both developer tools and communication. Notably, Cherny has no computer science degree—he studied economics and dropped out to pursue startups—which gives him a different perspective on how to build tools for developers. **Reactions and impact**: The thread went viral within the developer community, generating 1.6K+ upvotes on Reddit's r/ClaudeAI, with developers calling it "game-changing" and "watershed moment" content. The enthusiasm led to third-party projects like howborisusesclaudecode.com aggregating all his tips, and developers openly discussing how they've restructured their workflows around his advice. Multiple major tech publications (VentureBeat, Pragmatic Engineer, Lenny's Newsletter) have since produced in-depth analysis or interviews. **Broader context**: This thread is part of a series—Cherny has shared 40+ tips across five threads from January through February 2026, with themes ranging from basic workflow setup to advanced customization (hooks, permissions, agents). The recurring message is that Claude Code's power lies not in requiring deep customization but in understanding how to leverage built-in features for parallel work, verification loops, and automation. **Limitations and caveats**: The thread focuses on power-user features that require some technical comfort (git worktrees, terminal commands, settings configuration). Cherny himself notes these are advanced techniques, not required to use Claude Code effectively. Some features mentioned (like hooks and custom agents) require familiarity with Claude Code's configuration system. The thread is aspirational—achieving his 20-30 PRs/day workflow requires significant setup and infrastructure thinking, not just knowledge of individual features.
Topics
Claude CodeAI-assisted developmentdeveloper productivityautomation workflowssoftware engineeringAI agents