> ## Content Index
> Fetch the complete content index at: https://claudefox.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# Claude Code Projects as a home for your Conductor workflow
- URL: https://claudefox.com/claude-code-projects-as-a-home-for-your-conductor-workflow/
- Published: 2026-11-08T08:56:00.000Z
- Updated: 2026-11-20T02:54:21.000Z
- Description: Claude Code Projects, in beta on Pro, Max and Ultra, is one ongoing conversation where a coordinator hands tasks to parallel cloud threads, each on its own branch. How it compares with Conductor, how to bring pushed branches over, and the limits to know first.
- Author: hupicake
- Tags: News

*Updated November 20, 2026: Expanded with setup steps, what threads load from your repositories, usage costs and Conductor's current status.*

Conductor is an app for running a team of coding agents in parallel. It runs Claude Code, Codex, Cursor and OpenCode agents under the hood, and its site says it is "trusted by 100k+ builders". Conductor has announced that it is joining Meta, which makes this a good moment to look at Anthropic's own way of coordinating parallel Claude Code work: Projects. This guide reflects both products' pages as of November 20, 2026.

## Where Conductor stands now

Conductor's announcement says it is joining Meta and that something new is coming early next year. A line saying Conductor Cloud would shut down within weeks is now struck through, followed by a note that plans have changed and Conductor will still be developed. Its FAQ says the app keeps working, cloud workspaces can be transferred to local, all data can be exported, and Conductor has never sold or trained on user data. As of November 20 there is no shutdown deadline, though what Meta's plans mean longer term is not known.

## What a Claude Code project is

A project is one long-running conversation where Claude acts as a coordinator; Anthropic likens it to briefing a chief of staff. You send it work in any order, and it starts a thread for each piece or passes it to a thread already working in that area. Each thread is a separate Claude Code session with its own context window, usually in the cloud, and keeps going after you close your laptop. A cloud thread works on its own branch. It opens a pull request when you ask, or on its own for a bug fix or similar concrete change, then watches it with auto-fix on, waking to push fixes when CI fails or a review comment arrives, so review before you merge. An Overview pane shows finished threads, ready pull requests and threads waiting for you.

Every cloud thread starts with the project's instructions and memory, so a rule you state once reaches all of them. If a thread stops for approval, telling the coordinator to go ahead doesn't reach it; you answer inside that thread.

## Bring your existing branches over

There is no import for Conductor workspaces. What the docs describe, for an existing Claude session, is to push its branch to GitHub, add the repository to the project, and tell Claude the branch name; the same works for a branch you pushed from Conductor, but only what is committed and pushed comes along. A cloud session already doing the work can also be turned into a project from its sidebar menu with Continue in project.

## How to start one

- Check your plan: Projects is in public beta on Pro, Max and Ultra and is rolling out gradually. It isn't offered on Team or Enterprise yet. Look for Projects in the sidebar at claude.ai/code or in the desktop app's Code tab, or under More. If it is missing, you can join the waitlist.
- Set up GitHub: your code must be on github.com, with push access and the Claude GitHub App installed on each repository. On an organisation-owned repository only an organisation owner can complete that install, and SAML SSO organisations need the app authorised first. A token from /web-setup is not enough.
- Create the project: select New project, give it a name, and optionally a one-line goal and the repositories or files it should read.
- Write project instructions before the first batch, send one small real task, and check Thread model and Thread effort in Project settings: new projects run threads on Opus at high effort, which uses your plan fastest. On your first project Claude takes a turn of its own as soon as it is created, and any Setup recommendations it posts start switched on.

## What threads don't pick up

Cloud threads load each repository's root CLAUDE.md, .claude/CLAUDE.md and .claude/rules/. They do not load skills under .claude/skills, MCP servers from .mcp.json, or plugins, permission rules, hooks or env values from .claude/settings.json. Instead, you enable skills and connectors on your claude.ai account, add plugins in Project settings, and set environment variables in the cloud environment. If a task needs your local tools, Claude can run that one thread on your own computer through Remote Control (Claude Code v2.1.280 or later, while the computer is awake); such a thread gets the instructions but not the memory files.

## Limits and cost

- A project belongs to one user. You can't share it or its threads, and there are no organisation-level controls during the beta. If your team relied on Conductor's multiplayer workspaces, that is a real gap.
- Projects run at claude.ai/code, in the desktop app and in the mobile apps, not in the terminal CLI, VS Code or JetBrains, and not through Bedrock, Google Cloud or Foundry.
- Usage counts against the same plan limits as your other sessions and is used faster: each thread is a full session, the coordinator uses tokens too, and threads watching a pull request wake up on CI failures (ask one to stop watching if you don't need it). Usage in Project settings shows tokens by thread and model. A limit you ask for on parallel threads is a preference, not a cap; the only enforced limit is 500 new threads per day.
- A cloud thread's sandbox pauses between turns. If it can't resume, the thread restarts from a fresh clone and uncommitted changes can be lost, so ask Claude to commit and push on long tasks.

## Who should switch

Projects suits a solo developer whose code lives on GitHub and who wants agents to keep working in the cloud while they are away, such as a migration across several repositories or a stream of bug reports for one service. On the sources' own terms, Conductor is multiplayer and runs four agent families while Projects is single-user and Claude Code only, so teams sharing workspaces or using other agents will find Conductor closer to what they have. Anthropic points teams that want shared steering in Slack to Claude Tag.

## Our take

In our view Projects is not a like-for-like Conductor replacement: it is closer to delegating to a project lead than to running a grid of terminals. The shared memory and the automatic pull-request follow-up are genuinely useful. Single-user ownership and the plan-limit drain are real costs. If Conductor's change of owner unsettled you, start one small project with strict instructions, ask Claude to propose threads before starting them and run only a few at a time, and see how its pull requests compare with your usual workflow before moving everything.

Source: [Let Claude coordinate ongoing work with Projects (Claude Code Docs)](https://code.claude.com/docs/en/claude-projects?ref=claudefox.com), [Projects redesigned: from folder to conversation (Claude blog)](https://claude.com/blog/projects-redesigned?ref=claudefox.com), [Conductor is joining Meta (Conductor)](https://www.conductor.build/announcement?ref=claudefox.com), [Conductor home page and changelog](https://www.conductor.build/?ref=claudefox.com)

This story first appeared in the [claudefox daily briefing for November 8, 2026](https://claudefox.com/daily-2026-11-08/).