Founding Engineer @ Conductor (San Francisco, ONSITE)

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...

Fixed! You can now give Conductor fine-grained GitHub repository access.

Or, skip the integration and use your local GitHub CLI auth.

Are you still using outdated GitHub Oauth apps for this, or have you swapped to GitHub Apps? GitHub Apps are newer and have Oauth flows, but have a fine-grained permissions model instead of the Oauth permission model.

More info: https://docs.github.com/en/apps/oauth-apps/building-oauth-ap...

More-over, can you document the GitHub permissions needed and which GitHub App(s) this tool uses? Are you using device-flow, online oauth-flow, etc? And where are the Oauth tokens stored if so? Is there any server-side component where you might be storing tokens?

Thanks!

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?

Is some of the intermediary output being suppressed? This gives the feeling of CC "working" on my behalf.

Being able to quickly hit escape to interject. Escape again to see the conversation history.

The key bindings should be exactly the same.

I don't think I'm looking for an interface to replace CC - it's a great interactive terminal app.

I just want a better way to manage the sessions.

Thank you! Yes I agree :)

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!

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?

Queued would be more useful as we can also stop the conversation and prompt right away.

Yes Mac only (for now)

Let me know how it goes!

We create an isolated git worktree locally on your machine — whereas Codex (I believe) is running a container on the cloud

Claudes' Codes?!