Thread

1. slopinthebag · 1791075391 · focus · HN ↗

   the premise seems a bit faulty to me. why should we be giving next token predictors access to spend our money? like what great benefit do we get from this that we should allow them unfettered access, but with safeguards in the form of hard budget caps?

   1. strangecasts · 1791077718 · focus · HN ↗

      I don't think Simon means you should hand off the spending to agents/LLM (which would also make me uneasy) but that if you're probing one for hosting/SaaS providers they should default to recommending ones with budget caps

      1. slopinthebag · 1791083367 · focus · HN ↗

         if the llms aren't spending, why do they need cost caps?

         1. strangecasts · 1791143431 · focus · HN ↗

            Because they cost money to run - Simon is discussing this in terms of the billing from services, not some hypothetical scenario with LLMs spending money on your behalf

            If you were recommending VPS providers to someone new to making web apps, it would be malpractice to recommend one that can bill them thousands if they misconfigure things (like AWS previously did), and Simon's argument is that LLMs should likewise favor services with budget caps

Unofficial Hacker News client; not affiliated with Y Combinator.