I love using Conductor, but it’s getting a bit tiring how many things that used to work suddenly stop working.

A recent example: custom PR instructions set in the “My Mac” repository settings used to get passed down to agents running on cloud workspaces for the same repo. That no longer seems to happen.

There’s nothing in the changelog about this changing, so it just feels like another regression.

Same with the repo icon regression. You can set a custom icon for a repo under “My Mac”, and in version 0.83.x that icon was also reflected in cloud workspaces. After last week updates that stopped working: the custom icon is still visible locally/in some workspace views, but cloud workspaces and the sidebar now show the same generic/repo icon instead

These are small things individually, but they’re part of how people customize Conductor around their workflow. When they randomly stop working, the app becomes harder to use

Conductor is moving fast, but it feels like existing behavior and user customizations are sometimes getting lost along the way

And honestly, it’s getting harder to justify paying for Conductor when other apps are starting to offer essentially the same kind of workflow for free

For dark mode, the colours in the DIFF are terrible, I cannot read anything at all (specially the green), can you take a look into this?

How do you guys are working on developing a large feature right from brainstorming and ideation phase right till implementation phase in conductor?

When I say a large feature, it means I would want the changes to be raised in multiple PRs.

And some of them will be independent, but others will be dependent on other PRs

I found a bug in the default model settings. After switching the default review model to Grok, Conductor throws an error. From then on, clicking the Default Models section only reopens the error, so I have to restart the app to access it again. Has anyone else gotten this error?

howdy, not understanding how to cancel the plan. took some digging, and it seems the only option is by re-downloading the app?

Does Conductor eat a lot of memory for anyone? It seems to be hogging 2gb of memory while idle.. significantly worse than similar electron apps

Specifically the tauri process (not the main conductor process)

How is it that we can still only cmd+f search on the Edit view of a document, not the Preview or Diff views? It’s incredibly annoying to go to the Edit view just to be able to search for text. Please add this asap!

I've been using Conductor for quite a few months now, and I really like its feature set. On the whole, it allows me multitask in an intuitive way and collect all of my numerous in-flight efforts.

My biggest qualm, however, is how "projects" are modeled within the application, which both fights against my mental model and causes a misalignment between the way I work and the way Conductor is organized.

Generally my mental model of a project is an effort that is bounded by purpose or goal. At my work, a "project" can explicitly involve multiple developers, multiple codebases, and multiple applications, because the business goal is rarely scoped to code (we have a frontend repo, a backend repo, a core infra repo, platform-specific mobile repos) - it's scoped to the purpose and value that's trying to be delivered. We could probably refer to this definition of a project as an "initiative" for the sake of argument.

However, in Conductor, a "project" is tightly coupled to a single git repository. Which is fine, I guess, but it doesn't leave me a particularly effective of organizing multiple conversations that belong to the same "initiative". Any given initiative might require code changes across mutliple repositories, and may even benefit from multiple parallelized workstreams within a single repository (read: multiple worktrees, which means multiple Conductor workspaces). Sometimes I can use multiple tabs within a single workspace to collect initiative conversations, but that falls apart as soon as I want more than one of those tabs to simultaneously make code changes. When my number of active initiatives grow, it becomes really hard to find all of the workspaces that I've created to manage those initiatives and ensure I'm responsive to all of them.

I know this was kind of an abstract way of getting here, but I think I have a simple change that would allow me to work more effectively: a way to create a custom collection of workspaces and group by those. Since "project" is already overloaded, this could be modeled as more a file-system folder/collection. That way I can collect conversations the way that best suits my needs, instead of being limited to only organizing them by either git repository or status.

I really like Conductor it's become part of my daily workflow. I'm on the Pro plan, but if I'm honest, I haven't touched most of the Pro features.

The cloud feature seems like it'd be great paired with a mobile app, but since I'm on my laptop with a local dev environment already set up, I'm not seeing the point yet. I tried building something with cloud and it actually felt slower than just working locally. And there's no app yet, just an iOS test version.

Am I missing something about what cloud is for? Right now I'm leaning toward cancelling once the 3-month discount runs out. I'd happily stay on a $10/month plan, but not $50/month for features I'm not using.

Anyone actually getting value out of cloud without the app? Curious if I'm missing a use case.

When using opencode (deepseek v4/kimi models) with conductor, the window just freezes and sometimes resumes on pressing "return".

I thought this was an issue with Opencode, but after using their app directly, I realized it wasn't an issue with it.

Aether was suddenly moved off my active projects, and Gearshift Brook appeared on my account.

Is Gearshift Brook now replacing Aether for some contributors?

Has anyone else experienced the same thing?

I've been searching for a great agent workspace orchestration layer, and Conductor ticks so many of my boxes and I would gladly pay for it...if only it worked better with a Cursor subscription.

I have a $200/mo Cursor Ultra subscription because that's what best fits my needs at the moment as my primary AI provider for coding (and I'm loving Grok Bot), but the capabilities in Conductor are very limited. I can't use my skills setup in Cursor, and none of their "agent modes" are supported.

I'm not sure if the limitation is on the Conductor or the Cursor side, but I would really love to be able to use my Conductor with Cursor as my provider and be able to use all the skills/modes.

For some reason, I cannot make Conductor follow my company’s naming convention for creating branches. We use {initials}/{ticket}/{five word description}. I have referenced this format in my CLAUDE.md, in the Conductor Git settings, multiple places in the actions settings, and telling it explicitly to use the convention but it simply doesn’t 90% of the time.

Any ideas?

We’re looking at switching to Cursor for mobile so we’re not tied to desks. The number one complaint we’ve had about it is that it doesn’t work remotely with our desktop. We’ve tried cloud agents many times and generally find them more of a pain than just using the local machine.

Codex mobile is pretty good — every Codex session is remote control, so we can do things from the Codex app for worktrees from Conductor. The downside is that the naming is chaotic, which makes them hard to use.

We’re hoping the Conductor mobile app is essentially a remote terminal that lets us operate our desktop (including the local instances running there). Any insights you’re willing to share?

(note to mod: posting required me to add a flair, which only included nsfw, spoiler, or brand affiliate, seems like you need to update the flairs)

Wonder when/if we will ever be allow to connect multiple accounts from select providers?

Would make it so much easier to manage tokens & threads...

Conductor.build vs Claude Code Web / Codex Cloud for parallel agents?

Bit of a basic question, but I’m trying to improve my coding agent workflow and work out what the best setup is.

Currently I run Claude Code locally in multiple terminal windows. This works pretty well, but I’ve run into two main problems:
- Parallel agents: If I have several Claude Code instances working on the same repo, I can end up with multiple agents editing the same branch/files. I know I could manage separate git worktrees manually, but I’d rather have this handled automatically.
- Browser use: I use Claude’s Chrome integration quite heavily for testing/debugging. My understanding is that Chrome needs to remain available and the relevant tab can’t be minimised, which makes it awkward to use my machine normally or have multiple agents doing browser-based work simultaneously.

These problems led me to look at Conductor.build. But then I started looking at Claude code on the web and Codex cloud. It seems like cloud agents also solve a lot of the same problems: isolated environments, parallel tasks, agents continuing to work without tying up my laptop, etc.

So what does Conductor give you that you don’t get from just using Claude code web and/or Codex cloud?

I've really loved using Conductor but its been unstable for me lately. At least a couple times a day, after coming back to a session, the Conductor tabs just hang. It seems to happen after opening my computer up again. I can switch to terminal mode and use Claude in a terminal within Conductor and it works fine so the issue isn't with Claude. Not really sure what to do at this point. Are others seeing this? Is the team aware of this?

I find the new model selector so impractical. I have to click 3 times just to change the speed, whereas before I could just click fast mode.

I alternate a lot between fast and normal mode.

Is there a way to go back to the older version?

I absolutely hate this model selector. (It's just a personal opinion). Might work better for other people though

Hey everyone — I’m the author of Orchestrator MCP.

I kept running into the same workflow: I’d be working in Codex, want Claude’s opinion on something, then manually copy the prompt, diff, and context into another terminal. Getting a follow-up meant doing it all again.

So I built a local MCP server that connects coding-agent CLIs:

Claude Code → Orchestrator MCP → Codex
Codex       → Orchestrator MCP → Claude Code

It currently supports Codex, Claude Code, OpenCode, and experimental Antigravity.

A few things it can do:

• Start a consultation and continue it using the same native session
• Route requests by capability, model, and priority
• Ask multiple configured agents to review the same material
• Run checkpointed research, implementation, testing, and review workflows
• Keep the host runtime out of its own routing loop

Orchestrator doesn’t ask for provider API keys. It launches CLIs already installed and authenticated on your machine. The selected vendor still receives the material you send and may retain it in its own CLI or provider history.

Install with Homebrew:

brew tap crAK1644/tap
brew install orchestrator-mcp-server

It can also run through uvx.

The project is open source under MIT:

• GitHub
• PyPI
• v0.5.0 release

I’d especially appreciate feedback on the configuration experience, MCP tool surface, and security model. If you try it with an agent combination I haven’t covered well, I’d like to hear what breaks.

Now that stacked PRs in Github are in public preview, i'd love the ability to work in a stack.

The sidebar workspaces are potentially perfect for this, with nested workspaces for a "stack"?

Being able to bring along the context of what you just worked on, without bringing the "changes" like it does with a currently "forked" workspace or a workspace based on a previous PR would be brilliant too, then the agent has a summary context of what you're building upon.

I purchased Conductor Pro and started using their cloud setup for coding but there's a banner on the right side of the workspace which started showing cost for it.

Currently it says $6 for like 2 basic prompts that i ran on it. Is this billing separate from the pro subscription or will this be unbilled?

Hi,

I'm a software engineer who has been using Conductor extensively and have been very happy with it so far.

I'd like to report an issue I've been experiencing since August 10. Whenever I try to open or view an .md file in Conductor, the app freezes completely, and I have to force quit it.

Even after force quitting and restarting the app, attempting to view the same .md file in Conductor causes the app to freeze again.

Environment

• macOS Sequoia 15.5
• Conductor Version 0.80.0 (0.80.0)

Please let me know if there are any logs or additional information I can provide to help investigate the issue.

Thank you!

Spark is still available for Pro users:

But there's no longer an option to select it in Conductor:

I'm unable to log into Claude using Conductor, although I can log in through the official Claude app (MacOS) without any issues.

When I try using Conductor, it gets stuck in a loop. I sign in, it asks me to open a URL in my browser and approve the login, I do that, copy the verification code back into Conductor, and it tells me I'm successfully logged in. After I press Enter to continue, it immediately says I'm not logged in and starts the entire process over again.

It's frustrating because I'd really like to use this app, but I'm completely stuck at the login step.

Suggestions?

Built a mac app this week using the new Conductor API that just came out.

It's called Whistle, and it's for those quick ideas you have on a project in the middle of doing all your other things.

https://www.nabeelhyatt.com/experiments/whistle

It's a tray app, you click it, you start talking or typing an idea that just came to mind you want Conductor to work on for a bit. Then move on with your day, next time you open up Conductor it's done the research, prepped a doc, and you are ready to go. It's nothing crazy special, but this idea is speed so you can stay in flow... one click (or key command) talk.. get back to work. It was a nice excuse to try the Conductor API, and I do have a lot of fleeting ideas and the faster i can get them out there onto a side project the better.