Thread

1. nylonstrung · 1790103554 · focus · HN ↗

   I don't really understand how async tool calls translate to token savings

   It says that it removes tokens wasted while a model is waiting on synchronous tool calls. What tokens exactly is Pi using when waiting?

   1. dumberquestions · 1790105086 · focus · HN ↗

      I think a running agent periodically checks if a process it started has finished.

      1. [deleted] · 1790105833 · focus · HN ↗

         [deleted]

      2. zergrush · 1790133476 · focus · HN ↗

         that shouldn't be what eats up tokens tho

         gpt 6 sol already made a lot of progress with caches

         i have a feeling unreal agent might have decided to release now rather than getting sherlocked

         i just think its very risky right now to spend too much time building harnesses or anything on top of codex or claude simply because frontier labs will just absorb whatever works

   2. 332451b · 1790112999 · focus · HN ↗

      "More tool work per model turn" could reduce the number of cache reads (or even cache misses) and associated cost?
   3. swiftcoder · 1790146158 · focus · HN ↗

      I assume the bigger problem is the cache expiring while you wait for the tool call to complete. A bunch of hosted providers only keep the cache alive for ~5 minutes - if you sit there waiting for a 5 minute tool call, you get to pay to reload the entire context into cache

Unofficial Hacker News client; not affiliated with Y Combinator.