Interesting. I have been doing a simple man's version of multiple git clone folders and 'docker compose -p'. Making that smoother is attractive, esp if can be made opaque for our more junior teammates.
On one end, I have been curious about getting multiple agents to work on the same branch, but realized I can just wait till they do that natively.
More so, all this feels like a dead end. I think OpenAI and github are right to push to remote development, so these don't matter. Eg, mark up a PR or branch in GitHub, and come back as necessary, and do it all from my phone. If I want an IDE, it can be remote ssh.
Seems odd that the LLM is so clever it can write programs to drive any API.
But so dumb that it needs a new special purpose protocol proxy to access anything behind such an API...
lmeyerov|8 months ago
On one end, I have been curious about getting multiple agents to work on the same branch, but realized I can just wait till they do that natively.
More so, all this feels like a dead end. I think OpenAI and github are right to push to remote development, so these don't matter. Eg, mark up a PR or branch in GitHub, and come back as necessary, and do it all from my phone. If I want an IDE, it can be remote ssh.
shykes|8 months ago
If you're interested, here's the keynote recording: https://www.youtube.com/live/U-fMsbY-kHY?t=3400s
steeve|8 months ago
dboreham|8 months ago
rahimnathwani|8 months ago
shykes|8 months ago
container-use combines both forms of isolation: containers and git worktrees in a seamless system that agents can use to get work done.
brunoqc|8 months ago
kamikaz1k|8 months ago
akshayKMR|8 months ago