Asana Tests Browser Agents at $0.47 and About Four Minutes per Run
Asana Tests Browser Agents at $0.47 and About Four Minutes per Run
AI Agents & Automation

Asana Tests Browser Agents at $0.47 and About Four Minutes per Run

OpenAIOct 9, 2026

Asana says tests of an optimized GPT-6.1 Sol browser-agent workflow averaged $0.47 and about four minutes per run.

Asana says it has reduced the estimated model cost and runtime of a browser-agent workflow by changing how the agent handles browsing history, screenshots, and cached inputs. OpenAI published the results on October 9, 2026. In the reported tests, the optimized workflow using GPT-6.1 Sol averaged $0.47 and about four minutes per run—76 times cheaper and five times faster than the original production setup on another model, which the study labels Model B.

The work began with StackAI CTO Frank Hidalgo using GPT-6 Astra in Codex to investigate the agent and run experiments. Asana’s StackAI platform lets customers build workflows that navigate websites, fill out forms, and collect information. Hidalgo estimated that the investigation would have taken one to two months manually; the team completed it in about a week.

The study tested a task that collected six fields for each of 32 books from a public demo catalog. The team compared four models and tested different history budgets, caching approaches, and screenshot-removal policies. The selected configuration gave the agent more room to retain browsing history, cached that history, and removed screenshots in batches rather than at every step.

The changes addressed a cost problem in the earlier design: each request resent the accumulated page text and screenshots, while frequent edits to that history made caching less effective. On Model B, the revised workflow cut estimated cost from at least $36.21 to $1.24 per run. The optimized GPT-6.1 Sol workflow averaged $0.47. On Sol alone, the changes reduced cost from $1.97 to $0.47; the company says 89% of input tokens in the optimized runs came from cache.

The larger history budget also improved completion in the tests: GPT-6.1 Sol returned correct answers in all 18 runs, compared with three of 18 under the smaller budget. Asana says it has released the browser-navigation changes in StackAI and is developing ways to repeat these evaluations when configuring agents.

Industry Impact

Lower-cost browser automation

Enterprise software and workflow automation

Overview

Asana’s tests show that browser-agent costs and runtimes can fall substantially through changes to history management, caching, and screenshot handling. In the selected GPT-6.1 Sol configuration, runs averaged $0.47 and about four minutes; the study compared this with an original production setup using another model. For developers and product teams, the work highlights the importance of optimizing workflow design—not just model choice. The results come from a specific catalog task, so teams should validate performance on their own workflows before budgeting around them.

Key Impact Points

The optimized GPT-6.1 Sol workflow averaged $0.47 per run, with 89% of input tokens coming from cache.

On the tested task, a larger history budget improved correct answers from three of 18 runs to all 18.

Asana says browser-navigation changes are available in StackAI, bringing the workflow improvements into its platform.

Opportunities

Browser-agent workflow optimization

Enterprise software and workflow automation

The article supports an opportunity for workflow-platform teams to help customers measure and improve browser-agent performance. Repeatedly sending page history and screenshots can raise costs, while frequent history edits can undermine caching. Tools or services that evaluate history budgets, caching, and screenshot policies could help teams find configurations suited to specific tasks. Asana says it is developing ways to repeat these evaluations when configuring agents, indicating a practical need for reusable testing. The reported savings and completion gains are specific to one task and should be treated as a basis for customer trials, not a guaranteed result across workflows.

  • Reusable browser-agent evaluation and tuning

    Problem: Browser-agent workflows can incur high costs and long runtimes when they repeatedly send browsing history and screenshots, and some configurations may reduce task completion.

    Solution: Provide repeatable evaluations of history budgets, caching approaches, and screenshot-removal policies for specific browser workflows.

    Target Users: Teams building or configuring browser-navigation workflows on platforms such as StackAI.

    Business Value: Help teams assess cost, runtime, and completion quality together, then select a configuration based on their own tasks.

    Revenue Potential: The article does not quantify revenue potential; evaluation and tuning could support a platform feature or a paid workflow-optimization service.

Reference link

https://openai.com/index/asana-browser-agent

Image Source Link

https://zenphi.com/wp-content/uploads/2026/04/ai-agent-platform-process-structure.webp

Community Discussion (0)

Loading discussions...