Sorry about that, working on Intel right now!
Intel version now live!
Readit NewsCharlieholtz commented on Show HN: Conductor, a Mac app that lets you run a bunch of Claude Codes at once conductor.build/... · Posted by u/Charlieholtz
Totally understand, but you're asking for the keys for the kingdom, without any data disclosure or privacy policy. Even if you switch to fine-grain permissions, the lack of any "and here are our commitments to handling or accessing your data" is (and should be) a show-stopper for anyone trying this out.
In case people aren't reading, here's the c+v of what Conductor gets access to currently:
--
This application will be able to read and write all public and private repository data. This includes the following:
Code
Issues
Pull requests
Wikis
*Settings*
*Webhooks and services*
*Deploy keys*
*Collaboration invites*
Now fixed in the latest version. You can now give Conductor fine-grained GitHub repository access.
Or, skip the integration and use your local GitHub CLI auth.
Any way to have it not require full write access to your entire GitHub account?
Fixed! You can now give Conductor fine-grained GitHub repository access.
Or, skip the integration and use your local GitHub CLI auth.
There’s a “feel” to the way Claude Code outputs the text. And for input as well.
Sadly, this is lost with conductor.
I just don’t feel as joyful using it.
Ah, we’d love for Conductor to feel magical to use — we spend a lot of time thinking about this. Any chance you could say more about what’s lost?
This is very useful! I think the interfaces around models being used in an async manner will look very different than the synchronous chat UIs we are today. Claude Code is the first real “agent” that is providing true economic value, and there’s so much low hanging fruit in making the interfaces far better.
Thank you! Yes I agree :)
Yes I had a similar experience. the thing that tripped me up with git worktrees, which is maybe obvious in retrospect, is that they don’t include things that are not tracked by git - e.g. .env.development.local
So starting a new worktree requires additional setup and isn’t as simple as just checking out a new branch
Sorry about that! We’re working on making this more intuitive.
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!
This is pretty cool, here are few feedbacks:
- I switch in between planning and execution in the middle of the conversation using Terminal a lot, it would be nice to have it here as well rather than defining how I want Claude to think in advance.
- Entering messages when the agents can result in task lists to save time.
I’m also experimenting different UX with CC, here is Claude Code running in Slack if anybody is interested. https://peerbot.ai
Thank you! Yes, I agree, we're adding plan mode soon. For now I find Opus responds reliably to "plan this out and don't make any changes."
> - 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?
Its for mac only? But isn't it just an API wrapper?
Yes Mac only (for now)
Oh cool, I was already doing this with git worktrees but a ui for it would be handy.
Let me know how it goes!
Is it similar to what OpenAI Codex does with isolated environments per agent run?
We create an isolated git worktree locally on your machine — whereas Codex (I believe) is running a container on the cloud