Couldn't you just do AgentExecutor(...).run(task="...") and launch an autonomous AI in only one line?
The timing of killing EVs is particularly bad. The global market is clearly moving toward electrification regardless of what any single manufacturer does. BYD, Tesla, and the Chinese EV makers are not slowing down. Every year Honda delays, the gap in battery technology, software integration, and manufacturing cost efficiency widens.
What makes this shortsighted is that EV development isn't just about the car — it's about building the software and battery supply chain competence that will define the next 20 years of automotive. You can't pause that for a few years and catch up later. The institutional knowledge, supplier relationships, and engineering talent move to whoever is actively building.
This feels like the Kodak pattern: a profitable incumbent deciding the future can wait because the present is still comfortable.
This feels less like "agents" and more like a controlled generate → execute → fix loop.
Works great when you have a clear verification signal (tests passing), but what drives convergence when that signal isn’t well-defined?
the rag approach works better than people think if you get the chunking right
self-plug here.
Launch an AI agent to operate on production servers/sql safely using tmux
Impressive results. Would be curious about the long-term performance.
If you want sandboxed access to git, Slack, Gmail, etc, I built https://agentblocks.ai
[dead]
[flagged]
I was curious, so I dug a bit.
Under the hood it's effectively running:
Which cool, great, I sure love "pip install"ing every time instead of just baking a single container image with it already installed.This isn't any sort of fancy or interesting sandboxing, this is shelling out to "docker run", and not even using docker as well as it could.
Quoting from the linked page:
> The tradeoff is ~5-10 seconds of container startup overhead
Sure, maybe it's 5-10 seconds if you use containers wrong. Unpacking a root filesystem and spinning up a clean mount namespace on linux is a few ms, and taking more than a second means something is going wrong, like "pip install"ing at runtime instead of buildtime for some reason.
I can spin up a full linux vm and run some code in quicker than 5 seconds.