Skip to main content
The Startup Ideas Podcast

Claude Code's Creator Reveals "Claude Cowork"'s Setup

42 min episode · 2 min read

Episode

42 min

Read time

2 min

Topics

Productivity, Leadership, Artificial Intelligence

AI-Generated Summary

Key Takeaways

  • Parallel Task Workflow: Run five to ten Claude sessions simultaneously across terminal, web, and mobile apps. Start tasks in separate tabs, let Claude develop plans, then switch between them to approve plans and enable auto-accept mode. This multiplies productivity by managing multiple AI agents rather than working sequentially on single tasks, fundamentally changing work from deep focus to orchestration.
  • Opus 4.5 Selection Strategy: Always use Opus 4.5 with thinking enabled despite being larger and slower than Sonnet. The smarter model uses fewer total tokens because it requires less steering and correction, making it faster and cheaper overall. Once the plan is solid, Opus 4.5 executes code nearly perfectly, eliminating the back-and-forth iterations required by smaller models.
  • Team Knowledge Base Maintenance: Maintain a shared Claude.md file checked into Git that the entire team updates multiple times weekly. Whenever Claude makes an error, immediately add correction instructions to prevent repeating the same issue. Use the GitHub action to tag Claude on pull requests to automatically update the knowledge base, implementing compound engineering principles where no correction happens twice.
  • Output Verification Setup: Always provide Claude with tools to verify its own work, like the Chrome extension for testing web applications or running test suites for code. Without verification capability, Claude operates like a blindfolded painter or engineer who never sees results. Self-verification dramatically improves output quality as the model iterates based on actual results rather than assumptions.
  • Plan Mode First Approach: Start most sessions in plan mode and iterate with Claude until the plan is comprehensive and accurate before writing any code. Switch to auto-accept edits mode only after plan approval, allowing Claude to execute without interruption. Good planning eliminates most errors upfront, making plan quality the primary determinant of code quality in the final implementation.

What It Covers

Boris, creator of Claude Code, demonstrates Claude Cowork's capabilities and best practices. He shows how the desktop app automates file management, spreadsheet creation, browser control, and email tasks through a virtual machine interface. Boris shares his personal Claude Code setup, including parallel task management, Opus 4.5 usage, and team knowledge base maintenance strategies.

Key Questions Answered

  • Parallel Task Workflow: Run five to ten Claude sessions simultaneously across terminal, web, and mobile apps. Start tasks in separate tabs, let Claude develop plans, then switch between them to approve plans and enable auto-accept mode. This multiplies productivity by managing multiple AI agents rather than working sequentially on single tasks, fundamentally changing work from deep focus to orchestration.
  • Opus 4.5 Selection Strategy: Always use Opus 4.5 with thinking enabled despite being larger and slower than Sonnet. The smarter model uses fewer total tokens because it requires less steering and correction, making it faster and cheaper overall. Once the plan is solid, Opus 4.5 executes code nearly perfectly, eliminating the back-and-forth iterations required by smaller models.
  • Team Knowledge Base Maintenance: Maintain a shared Claude.md file checked into Git that the entire team updates multiple times weekly. Whenever Claude makes an error, immediately add correction instructions to prevent repeating the same issue. Use the GitHub action to tag Claude on pull requests to automatically update the knowledge base, implementing compound engineering principles where no correction happens twice.
  • Output Verification Setup: Always provide Claude with tools to verify its own work, like the Chrome extension for testing web applications or running test suites for code. Without verification capability, Claude operates like a blindfolded painter or engineer who never sees results. Self-verification dramatically improves output quality as the model iterates based on actual results rather than assumptions.
  • Plan Mode First Approach: Start most sessions in plan mode and iterate with Claude until the plan is comprehensive and accurate before writing any code. Switch to auto-accept edits mode only after plan approval, allowing Claude to execute without interruption. Good planning eliminates most errors upfront, making plan quality the primary determinant of code quality in the final implementation.

Notable Moment

Boris reveals that half his coding now happens on his phone using the Claude iOS app. He kicks off three to five Claude Code sessions each morning from bed while checking Twitter, then checks progress throughout the day. This mobile-first coding workflow represents a fundamental shift he never predicted a year ago when Claude Code launched in the terminal.

Know someone who'd find this useful?

Episode Transcript

Claude Cowork is here. And if you understand how to use it, you're gonna be able to outperform 99% of people on this planet. It is an easy way for you to use Claude Code. You might have heard of Claude Code. It's gone viral, but the problem is it feels technical. You have to go into the terminal, and it's not fun for a lot of beginners. So Cloud has come up with Cowork, and it's a brand new product that harnesses the power of Claude Code in a UI that is simple, that anyone could use, that your dad can use, your mom could use, hey, even you can use. So in this episode, I brought on Boris, the maker of this product. I'm so excited that he shows you the best practices for how to use Claude Cowork and, at the end, how he sets up his Claude code to get the most out of it. You're gonna love this episode. We are lucky. We've got Boris. He's the creator of Claude Code and I would say the co creator of Claude Cowork today. And today, what I wanna get accomplished is everyone's talking about Cowork, and I wanna best understand what are the use cases? How can we get started? What are some non obvious ways I can use it? So, Boris, thank you so much for coming on the show. And I have one question for you. By the end of this episode, what are people gonna get out of it? Oh, I think people are gonna start to get some more ideas for how to use Cowork. And hopefully they're going to tweet about it and maybe they'll even reach out to me so I could learn how they want to use cowork. It's funny. I feel like, quad code from the beginning, it was sort of built to be It wasn't actually built to be a product at all. But when we first started thinking about it as a product, we thought that the thing people would use it for is coding. But we've learned very quickly that people didn't just use it for coding. They used it for like all sorts of stuff. So I kind of feel the journey of quad code has been very surprising. And I have been learning so much just watching how people use the product and how they abuse it and kind of like what they actually want to use it for. And even if it's not designed for that. So I kind of feel the same way about coworker. You know, I have some ideas about what people are going to use it for. I kind of view these as hypotheses. And so, you know, happy to talk about it, happy to maybe I'll do a quick demo to show you kind of some of the things that we use it for. But I think that it's going to be pretty surprising. And I hope …

Get the full transcript (8,529 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all The Startup Ideas Podcast transcripts →

You just read a 3-minute summary of a 39-minute episode.

Get The Startup Ideas Podcast summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

Books, tools, and gear mentioned in this episode

SignalCast may earn commission on purchases via these links.

Tools

  • Claude CodeRecommended

    by Anthropic

    Boris, creator of Claude Code, demonstrates Claude Cowork's capabilities and best practices. He shows how the desktop app automates file management, spreadsheet creation, browser control, and email tasks through a virtual machine interface.
  • Claude Opus 4.5Recommended

    by Anthropic

    Always use Opus 4.5 with thinking enabled despite being larger and slower than Sonnet. The smarter model uses fewer total tokens because it requires less steering and correction.
  • Claude iOS appRecommended

    by Anthropic

    Half his coding now happens on his phone using the Claude iOS app. He kicks off three to five Claude Code sessions each morning from bed while checking Twitter.
  • Chrome extensionRecommended
    Always provide Claude with tools to verify its own work, like the Chrome extension for testing web applications or running test suites for code.
  • Claude CoWorkRecommended

    by Anthropic

    Boris, creator of Claude Code, demonstrates Claude Cowork's capabilities and best practices.
  • GitHub ActionsRecommended

    by GitHub

    Use the GitHub action to tag Claude on pull requests to automatically update the knowledge base.
  • GitRecommended
    Maintain a shared Claude.md file checked into Git that the entire team updates multiple times weekly.

More from The Startup Ideas Podcast

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Startup Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's AI & Machine Learning Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into The Startup Ideas Podcast.

Every Monday, we deliver AI summaries of the latest episodes from The Startup Ideas Podcast and 192+ other podcasts. Free for one show.

Start My Monday Digest

No credit card · Unsubscribe anytime