Boris Cherny (created Claude Code) just posted a thread on the features he uses day to day. Half of these I had no idea existed. Here’s all 15 with the commands.
- Mobile app. Full Claude Code experience in the iOS/Android Claude app (Code tab, left sidebar). Boris writes a lot of his code from his phone.
- Session teleportation. claude --teleport or /teleport pulls a cloud session to your local terminal. /remote-control goes the other way, control a local session from your phone or browser. He keeps “Enable Remote Control for all sessions” on permanently in /config .
/loop and /schedule . Tell Claude to run a task on repeat, at a set interval, for up to a week. His actual setup: /loop 5m /babysit handles code review, rebases, shepherds PRs to production /loop 30m /slack-feedback creates PRs from Slack feedback automatically /loop /post-merge-sweeper catches code review comments missed after merge /loop 1h /pr-pruner closes stale PRs His advice: turn workflows into skills, then loop them. 4. Hooks. Deterministic logic that fires during the agent lifecycle: SessionStart dynamically loads context each time PreToolUse logs every bash command PermissionRequest routes permission prompts to WhatsApp Stop pokes Claude to keep going when it stops early If Claude stopping mid-task has been driving you crazy, the Stop hook alone is worth it. 5. Cowork Dispatch. Secure remote control for the Claude Desktop app. Uses your MCPs, browser, and computer (with permission). Boris uses it daily for Slack, emails, and file management when he’s away from his laptop. 6. Chrome extension. His #1 tip: give Claude a way to see what it’s building. Without this, Claude is coding blind on frontend work. The extension lets it look at the browser and iterate until the UI looks right. He says it outperforms equivalent MCPs. Desktop app web server testing. Desktop auto-starts your dev server and tests it in a built-in browser. CLI/VSCode can get close with the Chrome extension, but Desktop bundles it natively. 8. Session forking. Two ways: /branch from inside a session (creates a branch, resume original with claude -r <session-id> ) claude --resume <session-id> --fork-session from CLI 9. (I always use that one) /btw for side queries. Quick question without derailing the agent mid-task. /btw how do I spell dachshund? and it answers, then picks up where it left off. Git worktrees ( -w ). Run dozens of parallel Claude sessions in the same repo. claude -w spins up a new worktree automatically. 11. /batch . Fan work out to hundreds or thousands of worktree agents. Migrations, bulk refactors, mass test generation. Anything parallelizable, one command. 12. –bare flag. Skips auto-loading CLAUDE.md , settings, and MCPs on startup. Up to 10x faster init. Good for scripting and pipelines where you don’t need the full context. 13. CLAUDE.md tips. Keep it under 1,000 tokens. Only include what Claude needs on literally every turn. Use CLAUDE.md files in subdirectories for context that only loads when relevant. 14. Custom agents ( –agent ). Define agents in .claude/agents/ with restricted tools, custom descriptions, and specific models. Run with claude --agent=<name> . Good for read-only agents, specialized reviewers, domain-specific workflows. 15. /voice . Boris says he does most of his coding by talking to Claude. /voice in CLI (hold space to speak), voice button on Desktop, or just iOS dictation. YOURS TRULY 🙇 (Full thread available here: https://x.com/bcherny/status/2038454336355999749 ) Edit : improved readability submitted by /u/quang-vybe
Originally posted by u/quang-vybe on r/ClaudeCode
You must log in or # to comment.