Asana says cache changes cut a browser agent's cost 76x

Reddit r/artificial News

Summary

Asana says it reduced a browser-agent workflow's model cost by 76x (from $36.21 to $0.47 per run) and cut runtime from 22.5 to about 4 minutes by stabilizing page history to enable prompt caching and pruning screenshots in batches, rather than changing the underlying model.

Asana says it cut the estimated model cost of one browser-agent workflow from at least $36.21 to $0.47 per run, while reducing runtime from at least 22.5 minutes to about four minutes. The change was not a new model. It kept the agent's growing page history stable long enough for prompt caching to work, then pruned screenshots in batches instead of rewriting the history on every step. The result came from a 144-run study across GPT-6.1 Sol and three other frontier models, plus a 12-run follow-up. Asana says every best-condition run reached the same 192 facts, but also notes that the study used only three or four runs per condition and that its baseline included capped runs. The practical lesson is to measure cache reads, history churn, cost, runtime, and answer quality together. A cheaper agent that fails more tasks is not cheaper. Sources: OpenAI: https://openai.com/index/asana-browser-agent/ Asana: https://asana.com/inside-asana/cut-browsers-agent-cost
Original Article

Similar Articles

Your Agentic Workflow's Cache Keepalive Costs 8x Too Much

Lobsters Hottest

A detailed measurement study across Anthropic, OpenAI, Gemini, and DeepSeek finds that the conventional 30-second prompt cache keepalive is 8x too frequent; a 4-minute interval is optimal, and only Anthropic's cache saves money at long idle gaps.