@garrytan@conductor_build I did the same recently and agree. Same for the codex app. I wanted to like them both but conductor still is the best experience across the board by a solid margin.
@rameerez Itโs too bad the onus is still on the web developer to implement
That said, itโs another surface area definitely worth opening up for ai first web apps / experiences so they work well with openclaw, etc
I was lucky enough to work with @charlieholtz in Dec to help add support for codex in @conductor_build
What I learned:
1. They SHIP ๐ข
2. Have incredible taste and hyper focus on delivering what users need
3. Super chill and fun to be around
This is an awesome opp to join a team thatโs going to do big things!
come work with us at @conductor_build!
we're growing fast and have big plans. interfaces to orchestrate AIs are already changing how we work and we think we have a real shot at building the best one.
if you're up to moving to San Francisco send me a DM or apply below!
DAU since launch:
@lgrammel It would be ideal if agents run other agents as tools in the ai sdk. And even better if it is compatible with workflow dev kit as well. Iโm missing that compatibility when building a production system at the moment
@darrenjr@0xblacklight@aisdk@lgrammel ๐ฏ this would be amazing. Iโm working on implementing an agent implementation in ai sdk that essentially can do this
@rauchg@vercel The basic idea is the ability to treat cc like you would any other model with some added capabilities
And probably leveraging the agent abstraction, workspaces, and workflows sdk
Either one of these would be awesome:
"harnesses are not model-agnostic" is sad but very true. Lots of downstream implications, like:
- first-party agents (claude code, codex, antigravity) work better than generic agents (cursor)
- swapping models is hard in practice. If progress stalls people will stop doing it. https://t.co/bX8mmJaaYx
also the inverse of 1 could be really useful too... i.e. fork off a workspace to take it down a different path
(perhaps to add a small feature in parallel to the same branch, or to do a little experiment that won't pollute the original workspace)
tried @conductor_build for the first time today... wow!
this might be my new daily driver over cc / codex / cursor, etc
it's a nice balance between a cli / ide, with the option to jump into either as needed
and it's almost too easy going from idea to merged pr with the github integration (it's in a diff league compared to other tools)
bravo @charlieholtz
that said, here are a couple ideas/nits that popped up in my first session that might be worth considering:
1. ability to merge workspaces so many changes can be worked on in parallel that ultimately end up in the same pr vs pr for each
2. when viewing file diff, keep the list on the right so I don't have to move all the way to the other side to change files
2a. make it so the diff view is scrollable to see all files so I don't even have to click the separate files :)
Weโre testing something ๐งช
GitHub Copilot CLI is now in public preview. Build, debug, and deploy with GitHub Copilot coding agent without leaving your terminal.
Try it out and tell us what you think ๐
https://t.co/ZPexOhsII4
Gave an AI agent a shopping list.
A minute laterโฆ my Instacart cart was full.
No Selenium. No Playwright. No external browser process.
Just Genie, our open-source Chrome extension that lets LLMs drive any website from inside the browser with jQuery powered by @gensx_inc