Source: raw/Getting_started_with_Claude_Code_Projects.md — official Claude YouTube channel (@claude), Getting started with Claude Code Projects, video ID omihvjf0A2k (https://www.youtube.com/watch?v=omihvjf0A2k), auto-caption transcript fetched 2026-10-30, about 880 words.

Product: Claude Code Projects · Status: beta, rolling out gradually to Pro and Max plans

Anthropic’s own walkthrough of redesigned projects in Claude Code. A project is one ongoing conversation where Claude coordinates the work: you give it a goal and tasks, and it starts a thread for each task. Each thread is its own session on its own branch in the cloud, so work continues with your laptop closed. Until now the wiki’s coverage of the redesign was second-hand (Matt Wolfe reading the launch post, Robo Nuggets’ desktop tour, both in Projects); this is the first-party version, with the tab layout and three usage tips from the Claude Code team.

Key Takeaways

  • One conversation, many threads. The main project conversation is where you talk to Claude and where it coordinates. You don’t create subagents, manage sessions or set up worktrees; Claude splits the goal into tasks and assigns threads to run them in parallel.
  • A thread is a full Claude Code cloud session on its own branch. When a task needs your local files or tools, ask Claude to run that thread on your computer instead.
  • Use it for goals that span many sessions or repos, such as migrating off a deprecated package, or updating an endpoint across API, web and mobile repos.
  • Threads own their PRs. A thread opens a pull request on its own when it has a concrete change (or when you ask), then keeps watching it: it pushes fixes when CI fails and addresses review comments. To merge, ask Claude.
  • Four places to look: the main conversation (next steps on each PR), the Threads tab (threads waiting for you), the Pull requests tab in Overview (all PRs and statuses), and the Library tab (the project’s shared folder of artifacts and your own files, readable by every thread).
  • Routines close the loop. Connect a monitoring service and ask Claude to set up a daily routine; when it finds a regression it opens a thread to investigate, waiting for you next time you check in.
  • Cost tip from the team: projects use plan limits faster than a single session. Leave the coordinator on low effort (it mostly routes work), default threads to a smaller model, and switch to a larger one inside a thread for complex tasks.
  • Threads share memory. Tell Claude to remember a preference for all future threads; edit that memory in project settings.

Try It

  1. Create the project. Open the Claude tab on desktop or the web app (as the captions render it), create a project, and give it a name, a goal and the relevant repos or folders.
  2. Start with exploration. In the main conversation, share context (the video shares performance metrics and user feedback) and ask Claude to explore the codebase and suggest what to do. Agree on the work before it starts threads.
  3. Let threads run. Click a thread card to follow it, steer by talking in the thread, or stop it. Check the Threads tab for anything waiting on you.
  4. Ask for an artifact to share. The video asks for a summary of the changes with before-and-after performance metrics. It lands in the Library, so the next performance pass can update the same report.
  5. Add a guard routine. Connect your monitoring service, then ask Claude for a routine that runs every day and checks for regressions.
  6. Set working rules once. Tell Claude how many threads to run at once, how often to update you, or to show you a plan before it starts.

Implementation

Tool/Service: Claude Code Projects (beta), from the Claude desktop app or web app.

Setup: project name, goal, and repos or folders. Project settings hold the model and effort level, and the shared memory.

Cost: each thread is a full Claude Code session drawing on your plan’s limits; several run at once. No separate price is given in the video.

Integration notes:

  • Threads run in the cloud by default, so they need what any cloud session needs (GitHub App access to the repos, an environment that can run your checks).
  • The field guide says projects “can start up to 200 threads a day”; the video gives no number.
  • Recommended effort split, per the video: coordinator low; threads on a smaller model by default, larger model for big tasks.

Open Questions

  • The captions say to “open the Claude tab on desktop or the web app”; Robo Nuggets found projects under “More” in the sidebar. The exact entry point may differ by app version.
  • How a thread is switched to run on your computer (a setting, or only by asking) is not shown.
  • What “smaller model” the team means is not named.