Charlieholtz
My flow is something like: - Create a new workspace for a specific bug/feature - Ramble into the input box. I use a goose neck microphone and Spokenly (with Parakeet as the model ) for local speech-to-text - Hit enter! I don't use plan mode. - Ask for a review from a different model (⌘⇧R) - Create a PR and run a /babysit loop - Run a local version of the app and click around, do a human review. If the LOC are negative we don't pay much attention to the code. If it's positive we do - Merge!
I often have 3-5 workspaces running like this. There's lots of room for improvement but it's been working quite well for me.
We've re-built Conductor from scratch to make it twice as fast
This is helpful to know - we're working on adding more agents, Copilot and OpenCode harnesses are among the most popular requests.
We also recently built an escape hatch. If you turn on Settings → Experimental → Big Terminal Mode you can create new terminals in the center panel (with ⌘⇧T) and use any agent you'd like (Copilot, OpenCode, etc). It isn't the best experience because you don't get notifications etc (yet), but at least it lets you use the harness you'd like until we build out the first-class UI for it.
Send me feedback anytime, I'm [email protected].
Cmd Joins Conductor
Conductor raises $22M Series A
Conductor lets you run a team of coding agents on your Mac. We launched in July through Show HN, and are used by engineers at companies like Linear, Vercel, Notion, Stripe, and YC.
We’re on a mission to build the human interface to AI organizations. We’re a team of four looking for one or two more exceptional engineers or designers. No AI experience needed, just some enthusiasm for the awesome alien power of LLMs.
https://www.ycombinator.com/companies/conductor/jobs/MYjJzBV...
Show HN: Chorus is now open source
How to Checkpoint
Conductor (YC S24) Is Hiring a Founding Engineer in San Francisco
Or, skip the integration and use your local GitHub CLI auth.
Or, skip the integration and use your local GitHub CLI auth.
Internally our workflow looks like this: - we have a script that sets up a repo — copies env variables, runs pnpm i, inits a db, etc - we have a field in the repo settings called “setup script.” every time you make a new workspace, that script runs
Hopefully will be much improved over the next week or two!
> - Entering messages when the agents can result in task lists to save time.
Ah yes, queuing coming soon too! Do you prefer if the queued messages send when Claude is finished or interrupt it?
Right now the app uses GitHub's OAuth sign in (https://docs.github.com/en/apps/oauth-apps/building-oauth-ap...) which unfortunately doesn't allow for fine-grained permissions (it will only have access to organization code if you explicitly grant it) . We're switching our sign-in to a GitHub App so we can make the permissions fine-grained.
It will only have access to organization code if you explicitly grant it. We're working on switching our sign-in to a GitHub App so we can make the permissions fine-grained.