Engineering brief
Stop Inventing Bad Scripting Languages with Agent Tools
This engineering brief covers Stop Inventing Bad Scripting Languages with Agent Tools, with practical context for AI and developer-tool decisions.
The Brief
A single JavaScript REPL with persistent state cut spreadsheet errors by 42 percentage points and eliminated timeouts entirely. The real bottleneck isn't model smarts—it's the interface you give it.
Decision relevance
Read this for workflow impact, implementation trade-offs, and the claims that need technical scrutiny before they reach team planning.
Summary
The breakthrough was replacing 15 sequential spreadsheet tools with a single JavaScript REPL that maintains state. This lifted accuracy from 50% to 92% on an internal financial analysis benchmark and eliminated timeouts entirely. The REPL let the agent interleave reasoning with shorter scripts, building on previous results rather than chaining many atomic calls.
Earlier attempts—multi-agent architectures, SQL, XML representations—all failed because they were too rigid, lacked context flow, or didn't align with how LLMs reason. The team discovered that when an agent makes many tool calls, it's effectively using a bad scripting language; giving it a real one proved far more efficient and easier to extend.
Equally important were high-fidelity feedback loops: a formula engine and a renderer let the agent verify and correct its work. Without them, the REPL alone would produce unreliable outputs. The verification loop's value increases with model capability, making it a durable investment even as interfaces evolve.
Domain knowledge prompts and deterministic evaluation were crucial supporting practices. The team replaced LLM judges with black-box spreadsheet comparisons where possible, reducing confounded results. And they caution that many apparent model failures are actually infrastructure bugs—teams must inspect traces before blaming the model.
Why It Matters
Shows that giving agents a real scripting language with state and feedback loops is the highest-leverage change for structured data tasks.
Editorial analysis
Key claims
- Replace many tools with a persistent REPL and invest in high-fidelity verification loops for complex agent tasks.
Practical use cases
- Use this as input for tooling evaluation, workflow planning, and technical due diligence.
Risks / caveats
- Experiments with SQL, XML, and multi-agent splitting are just historical dead ends.
Who should care
- Engineering managers, tech leads, and CTOs evaluating AI or developer tooling decisions.
Related topics
Bottom Line
Replace many tools with a persistent REPL and invest in high-fidelity verification loops for complex agent tasks.
Watch
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
GRPO for LLMs: Reward Design Matters More Than Algorithm Choice
GRPO makes RL for LLMs accessible, but reward hacking is a real risk. The key is group variation and careful monitoring—not just watching reward curves go up.
Opus 5: The first practical default model for AI-assisted coding
Opus 5 offers a compelling middle ground between capable and cheap coding. Real savings are 20-25%, not 50%. Teams should test it as a daily driver before…
Managing AI Agents, Not Just Using Them
An AI engineer uses an agent manager and adversarial code review catching 63% of AI-generated changes—a shift in how teams should design AI workflows.
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.