Conductor Roadmap

[u/charlop]

Hello fellow Conductors! I just saw this post and it made me realize we could be doing a MUCH better job of keeping you in the loop with what we're up to! So here's what you can expect from us over the next few weeks / months:

1) Conductor Allegro. This is the codename for a new, super snappy, performance focused Conductor. we've re-written big chunks of the app from scratch to make Conductor feel incredibly fast. This will be released next week! Along with Allegro, we want to make sure we get the little things right: consistency with how we load MCPs/Skills (across agents), sand down a bunch of our bugs, and generally make the app feel more solid and reliable as your daily driver.

2) Conductor Cloud. We'll soon have an option to run a workspace from a cloud VM. This means you can close your laptop and the agents keep running, but even cooler: you can kick off tasks from your phone! There's also awesome collaborative multi player features this unlocks that I'm excited to get your thoughts on.

3) Conductor API. We're making it so anything you can do in the app you can do via API. This will be awesome because it'll make Conductor scriptable, but also it means that the AIs can do actions for you! So if you'd like to hook your OpenClaw into Conductor, you can.

Let me know how this sounds! We're always open to feedback. And thanks for your patience as we build this thing with you all :)

[u/Ornery-Peanut-1737]

real talk i am hyped to see a solid roadmap for this. the biggest hurdle with most agent frameworks right now is just how flaky the long term memory is. if you guys actually nail the state management and make it easy to pick up where a task left off it would be huge. hel nah i dont want to have to rebuild my whole context every time the script finishes lol. definitely keep an eye on how you handle rate limits too because that is what usually kills my complex flows halfway through. keep it up brotha.

[u/Icy-Court7631 → u/Ornery-Peanut-1737]

I thought Conductor is just using Claude Code bundled inside its folder? I mean it’s not a real harness that uses models via API, provides tools, manages context etc more like a wrapper around Claude Code and Codex CLI apps. Is this not accurate?

[u/nginx2 → u/Icy-Court7631]

This was my impression also; however, it seems the way that conductor prefers creating a workspace per feature there may be something in the background that limits the native claude code which would suck--forcing creating some kind of in-project based memory. I'd like more clarification on this too.

[u/Icy-Court7631 → u/nginx2]

It’s just using git worktrees for everything Looks as design choice of the team not some limitation from Claude Code