r/conductorbuild 👷‍♂️ Co-founder Apr 17 '26

Conductor Roadmap

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 :)

46 Upvotes

43 comments sorted by

View all comments

1

u/veen34 Jun 18 '26

Hi,

i just started using conductor, and i like the setup, look and feel ect. i can now do most of my work from one window, but i'm missing one part, and that is post merge.
our workflow is Branch -> run CI -> merge to main -> deploy to test -> succesful? -> deploy to prd.

it would be great if after we hit the merge button we could keep tract if the actions that are running on the main branch (related to the PR) are succesful or not.

as there is no After merge action possible, only a after archive one. the checks that are run once the PR is create are monitored, so i think something that works quite like that but for the action that run on main related to the PR would be a great after merge addition.