51–60 of 60 posts
AI outputs often feel like a gacha game. Paradoxically, the 'expensive' tokens are sometimes the cheapest in the long run. In my experience, higher-end models have a much higher 'one-shot' success rate. You aren't just saving on total token count by avoiding loops; you’re saving engineering time, which is always the most expensive resource anyway.
So all that to say, maybe try other harnesses because it could just be a prompt issue in the harness.
I am also an unabashed opencode shill, so take that into account too.
The per-route breakdown is exactly what's missing from the native dashboards. I've been running Trough for this: it sits in front of your HTTP API calls and tracks cost by route, so you can see "this endpoint is costing $X/day" rather than just an aggregate total. Retry storms show up as a spike on a specific route, which makes it easy to pinpoint the loop. Self-hosted Go binary, free for one service. stockyard.dev/t…
The per-route breakdown is exactly what's missing from the native dashboards. I've been running Trough for this: it sits in front of your HTTP API calls and tracks cost by route, so you can see "this endpoint is costing $X/day" rather than just an aggregate total. Retry storms show up as a spike on a specific route, which makes it easy to pinpoint the loop. Self-hosted Go binary, free for one service. stockyard.dev/t…
This is great visibility..just checked the website..I will try this over weekend