If you combine this with products like Sprites from Fly.io (or OSS version - agent substrate), where you pay only per execution request in a sandbox, you can have huge savings compare to the event loop inside the sanbdox. You will be billed only for request executions (tens of milliseconds per read/write, hundreds of milliseconds per search, etc.) and zero for all the waiting time during the the inference phase.

Also, if you don't require a real Linux sandbox — you might actually emulate the environment, e.g. just-bash idea with linux-like environment to give agents something that looks like their native habitat, but under the hood, it can be just CF Durable Objects SQLite or whatever else.

Probably(?) almost all knowledge work doesn't require a Linux sandbox. You can just build a document reading and editing agent that does tool calls and connects to other products via MCPs, APIs, etc. And lightweight actors make a lot of sense to me in these cases.

I'm just blown away. Editing weights? Writing weights from scratch!?

But again, it's very far from being a simple serverless micro server that scales infinitely and is super easy to use.

> Starting October 30, 2026, your included usage in ChatGPT Work and Codex will decrease from 20 times to 10 times the ChatGPT Plus allowance.

> For those who want even more usage and speed, the new Pro 500 tier offers our highest usage allowance, with 25 times the usage of Plus.

Comments URL: https://news.ycombinator.com/item?id=49919026

Points: 23

# Comments: 9

I think AI is even worse than drugs. On the one hand, it has some elements of a slot machine (when you have irregular success with the process, it creates a more powerful cycle of dopamine release on success). On the other hand, it makes work easier, and humans are just wired to choose the easier road. It's like walking or driving a car when you have to travel 10 miles each day. I don't see how, on a civilization scale, AI won't transform our civilization for better or worse.

And if this already happened at least once, how many times it has already happened and was “accidentally” added to the main model?

Here's the same token usage priced at different rates: a real long-running coding task, medium codebase, 447 turns.

  Input           1,026,957
  Output          164,667
  Cache read      36,554,368

  Type      Rate     Cost  Share
  Input   10.000   10.270    19%
  Output  50.000    8.233    15%
  Cache    1.000   36.554    66%
  Total            55.057   100%

  Type      Rate     Cost  Share
  Input    0.300    0.308    50%
  Output   1.200    0.198    32%
  Cache    0.003    0.110    18%
  Total             0.615   100%

  Type      Rate     Cost  Share
  Input    0.300    0.308    42%
  Output   1.200    0.198    27%
  Cache    0.006    0.219    30%
  Total             0.725   100%

  Type      Rate     Cost  Share
  Input    0.300    0.308    21%
  Output   1.200    0.198    13%
  Cache    0.027    0.982    66%
  Total             1.487   100%

I just ran two light tasks on my codebase and got 100% of the weekly limits of a Pro plan blown away. Is Ultra plan any different? Because on Codex it wouldn't affect my Max plan at all, I think it would have been below 1% othese usage.

I started Ottex nine months ago with the idea that models will get to the point that they will overcome VC-funded startups, and I think it just happened. So yeah, I got a little bit overexcited...