The article misses the point that you can have a third option - harness inside and outside both.

The use cases will evolve so much more in coming weeks and months that the boundaries will blur. You can still contain the agent outside in a sandbox though.

With instavm (https://instavm.io), you can provide an OCI image built from a dockerfile.

That's not the same as running the docker daemon in the sandbox.

I also felt the need for a cloud based cron like automations, so decided to build it myself https://cronbox.sh with:

  1. an ephemeral linux sandbox for each task 
  2. capability to fetch any url
  3. can use tools like ffmpeg to fulfill your scheduled task

Not just sides, the vents are much sharper.

Few years back, I tried to look on reddit for complaints regarding this - barely anything.

> The biggest problem is the coding agents don't "Fail fast and loud". They fail deceivingly.

GPT 2 and 3 used to fail fast (and loud coz we could easily see it lying)

My next exploration will be "Coding Agents: fail slow, silent, and deceivingly".

After one month working on using Claude to create trading strategies, the one thing I learned; if the strategy looks like it can profit, it is a lie. The trading strategy agent doesn't find trading strategies that work, it is really a bug hunting agent.

Has to be taken in light of median income too right?

I think you are absolutely right. (had to)

This is a bit restrictive, doesn't take screenshots. So you can't "say take screenshots of my homepage and send it to me via email"

It doesnt allow egress curl, apart from few hardcoded domains.

I have created Cronbox in the cloud which has a better utility than above. Did a "Show HN: Cronbox – Schedule AI Agents" a few days back.

https://cronbox.sh

and a pelican riding a bicycle job -

https://cronbox.sh/jobs/pelican-rides-a-bicycle?variant=term...

Had used cactus before - https://news.ycombinator.com/item?id=44524544

Then moved to pocket pal now for local llm.