AIToday
AI Coding AssistantsAI Business & IndustryOpenAI BlogPublished: Aug 19, 2026, 04:00 JST

Asana clears 5 years of engineering work in 2 weeks with Codex

Asana clears 5 years of engineering work in 2 weeks with Codex

3 Key Points

  1. What happened

    Asana used OpenAI Codex to remove its outdated testing system, Enzyme, in about two weeks—work it expected to take five years. Costs were about $12,000, versus a roughly $6 million estimate for the previous staffing plan.

  2. Why it matters

    The old testing tool had fallen out of maintenance and was blocking modernization of Asana's frontend stack. The successful migration shows that AI agents can make long-running software projects practical to tackle, changing which projects Asana believes are worth attempting.

  3. What to watch

    The outcome hinges on whether agents can handle other migrations and rewrites Asana once assumed would take years. The test is whether engineering review keeps pace while agents scale.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

Asana's migration off Enzyme highlights a shift in how engineering organizations can approach legacy technical debt. The old testing system was no longer actively maintained and had become a blocker to modernizing the frontend stack. By using OpenAI Codex, Asana's engineers reduced a projected five-year, $6 million staffing effort to about two weeks and $12,000 in direct costs, suggesting that AI agents can compress timelines dramatically when tasks are well-scoped.

The project's success appears to hinge on two factors. First, simple instructions outperformed elaborate setups, and having an engineer check progress twice daily kept the agents on track. Second, human review of each proposed change remained essential, indicating that agents augment rather than replace engineering oversight. Asana's CTO notes that not every years-long project will collapse into weeks, but the experience likely expands the set of migrations and rewrites the company now views as feasible.

Looking ahead, the real test is whether this approach scales to other long-running software problems Asana previously avoided. If the pattern holds, other companies may revisit their own technical debt backlogs, though outcomes could vary depending on codebase complexity and the quality of agent instructions.

FAQ
How did Asana use Codex to remove Enzyme?
Asana gave Codex a five-sentence prompt, and up to four coding agents worked in parallel on separate copies of the codebase. An engineer checked progress twice daily and reviewed every proposed change.
What were the cost savings compared to the original plan?
The migration cost about $12,000 in model and infrastructure costs, while the previous staffing plan was estimated to cost roughly $6 million.
How long did the Enzyme removal actually take?
It took about 1.5 weeks of engineering effort, spread across two calendar weeks, to fully remove Enzyme.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAWS enhances contract search with auto-generated metadata filters in Bedrock