Boris's 9 Practical Tips for Claude Code: It Turns Out the Expert's Setup is So "Plain" Boris Cherny has a nickname within Anthropic: the Father of Claude Code. He has been very active on X recently, so many people ask Boris: how do you actually use Claude Code? He just shared 9 practical tips on X. There aren't as many tips as you might think, and each one is quite straightforward. 【1】Core Idea: There is no standard answer for the best practices of Claude Code Boris starts by saying: > My setup might be surprisingly vanilla! Claude Code works great out of the box, so I personally don't customize it much. > My setup might be surprisingly "vanilla". Claude Code works well right out of the box, so I personally don't do much customization. It's understandable; those best practices, like Skills and Plugins, have already been built in as features by the Claude Code developers. There is no single correct way to use Claude Code. The team intentionally designed it to be flexible; you can use it however you want, modify it however you like. Everyone on the Claude Code team uses it completely differently. So there's no need to go to great lengths to find the "best practices"; finding a rhythm that suits you is the most important. 【2】Multi-Agent Task Parallelism: Running a dozen Claudes at the same time Boris's daily routine looks like this: he opens 5 instances of Claude Code in the terminal, numbered 1 to 5, with system notifications on, and switches to whichever one needs input. At the same time, he runs 5 to 10 tasks on the web version. The terminal and web can "hand off" to each other: using the & symbol to transfer local sessions to the web, or using --teleport to switch back and forth. Every morning and during the day, he starts several tasks from the Claude app on his phone and checks back later for results. The core logic of this "multi-threaded" work style is that Claude Code excels at autonomous execution; many tasks don't require your constant attention. You start a task, give it a direction, let it run, and busy yourself with other things. You can switch back when it needs your confirmation. This is a completely different rhythm from the traditional "human types a line of code, AI fills in a few lines". But it also places higher demands on the user; you need to be good at assigning tasks to Agents and be able to switch between multiple tasks at any time. For those used to traditional development with only one task at a time, this is a significant challenge. ...