Together AI improves coding-agent usability through evals
Together AI says it built an evaluation system to test whether coding agents can complete common platform tasks, then used it to identify documentation, skill-file, and API problems. After fixes including two added sentences in a GPU-cluster skill file, the company reports that a test task went from four of 15 passes with Sonnet to 100% across all three tested models. It also plans to open-source its evaluation package next week, with a local dashboard for running and comparing agent configurations and results.
The case study shows how product documentation, CLI guidance, and API design can materially affect coding-agent performance, while the planned open-source package gives developers a way to test agent readiness in their own platforms.

Earlier this year, we started seeing more and more devs using coding agents to build with Together AI.
It’s not hard to see why: It might take days or even weeks for a developer to wire up an app for production inference by hand, especially if they’re new to the platform. But for an agent using our SDK and CLI, it only takes a few minutes—at least in theory.
In practice, we had no idea whether the agents pointed at our platform were able to work with Together efficiently, or if they were hitting obstacles, going down rabbit holes or failing outright, and wasting tokens in the process.
As devs delegate more of their work to agents, developer experience (DX) is increasingly becoming synonymous with agent experience (AX). The easier your software is for agents to use, the easier it is for devs to build it into their own products and workflows.
#Together AI#GitHub#Claude Sonnet#Claude Opus#GPT Sol#Opus 4.8#Opus 5.5