Re:Jules, our asynchronous coding agent, is now available fo...
by mattnewton on Wednesday August 06, 2025 @02:03PM
(#44815483)
Getting the environment set up in the cloud is a pain vs just running in your environment imo. I think we’ll probably see both for the foreseeable future but I am betting on the worse-is-better of cli tools and ide integrations winning over the next 2 years.
[ Parent
| on HN ]
Re:Jules, our asynchronous coding agent, is now available fo...
by mvieira38 on Wednesday August 06, 2025 @02:54PM
(#44816102)
It took me like half an afternoon to get set up for my workplace's monorepo, but our stack is pretty much just Python and MongoDB so I guess that's easier. I agree, it's a significant trade-off, it just enables a very convenient workflow once it's done, and stuff like having it make 4 different versions with no speed loss is mind-blowing.
One nice perk on the ChatGPT Team and Enterprise plans is that Codex environments can be shared, so my work setting this up saved my coworkers a bunch of time. I pretty much just showed how it worked to my buddy and he got going instantly
Re:Jules, our asynchronous coding agent, is now available fo...
by drdrey on Wednesday August 06, 2025 @02:11PM
(#44815580)
with something like github copilot coding agent it's really not, the environment setup is just like github actions
Re:Jules, our asynchronous coding agent, is now available fo...
by MattGaiser on Wednesday August 06, 2025 @02:19PM
(#44815677)
It’s surprisingly good. If you try Copilot in GitHub, it has had no issues setting up temporary environments every single time in my case.
No special environment instructions required.
Re:Jules, our asynchronous coding agent, is now available fo...
by mattnewton on Wednesday August 06, 2025 @09:21PM
(#44819647)
It has depended heavily on the project. New SPA for the web? No problem. Nontrivial application with three services each with their own container in a monorepo? ML inference code that requires cuda hardware? No chance.