How to use Claude Code in GODMODE

The creator of Claude Code just dropped 10 tips for achieving his workflow. I've already covered seven of them on TikTok and Substack, but there are three that I haven't talked about yet. So let's dive in. I'm Pete. I run a software development agency in New York City. We work with startups and Fortune 500 companies to bring their products to market. In the last two weeks, Boris, the creator of Claude Code, casually dropped two absolute bangers on X. First, he said in the last 30 days, 100% of the code he shipped to build Claude Code was written by Claude Code itself. Let that sink in for a second. That's wild. Second, as a follow up to that post, he shared his 10 tips for being most productive with Claude Code. If you've been following me for a while now, most of these are gonna sound familiar because I've already made videos about them. If you want the deep dives, just scroll my TikTok or check my Substack for more information about these seven. But now let's dive into his three tips that I've yet to post about. By the way, no need to take notes. I did a full deep dive on all three of these. Like, why they matter, how to do them? It's free and it's on my Substack. First, parallel browsers and local Claude. So this is Beast mode. He runs five local Claude code sessions. I typically run around four, but then he also runs five to 10 Claude sessions in his browser and parallel with his local sessions. He uses two commands to move work between them. The & prefix sends a task from your terminal to run on the web in the background, and then teleport pulls a web session back down into your local terminal with full context. That means you can kick off a long running task in the cloud, keep working locally, and then teleport it back when you need hands on control. You could even start something on mobile, let it run, and pick it up later on your laptop. So this is super useful. I'm gonna post a dedicated video on this later in the week. Make sure to follow along! Second, use post hooks for formatting. So we do this internally at my company already. You set up a hook that automatically runs your formatter after Claude edits files that handles last mile details like formatting, linting, style, so the output is closer to production ready by default. And third, updating Claud MD during PR review. So when Claude makes mistakes, you don't just fix the code, you teach it how to never make that mistake again. So you tag Claude and PRs to update the shared Claude Markdown file. Every correction compounds and future runs will avoid past failures again. I break down all three of these in detail on my latest Substack. It's free. There's a link in my bio.