in a world where agent experience (AX) >> developer experience (DX) you need to make sure agents can use your platform
this is how we use evals to make sure agents can use the Together platform🔥
How we do agent evals at Together:
→ Define ~10 representative tasks
→ Run agents (Claude Code) in sandboxes
→ Test 3 configs (baseline, MCP, skills) for each task
→ Analyze trajectories and improve docs + APIs
Agent task completion improved from 67% to 96%! More below:
Read more about how we do agent evals here:
together.ai/blog/how-we-do-a…
1
422
closed → open migration works best as an iterative rollout
discover → evaluate → adapt → decide → production
evaluate on real traffic, improve what falls short, then canary the strongest candidate before moving more traffic
How do you build a small coding model from scratch?
@RicursiveAI 's Dan Zhang breaks down the architecture and decisions behind Ripple-65B Preview with @zainhas: dense over MoE, the ablations that held up (and didn’t), and what happened inside the RL runs.
Tuesday, Nov 17 . 11 A.M. PT / 2 P.M. ET
Register: luma.com/together-1kx8
6
1,115
Heading to @AWSreInvent ? Make plans for Tuesday night. Join Together AI + Coder at SUSHISAMBA for food, drinks, and conversation.
📍SUSHISAMBA at the Venetian, Las Vegas
🗓️ Tuesday, December 1
🕡 6:30-8:30 p.m. PST
inkling 2 small from thinking machines is now live on together ai
the multimodal moe is built for coding, long-horizon agentic work + vision, with 594b total parameters, 17b active + up to 1m context
try it now: together.ai/models/inkling-2…
poetiq uses together post-training to launch complex rl research workloads quickly, while keeping complete algorithmic control over their setup
fast to launch, with the training loop still fully theirs
together.ai/post-training
performance depends on the shape of your traffic
short in / long out → decode speed. long prompts → prefill. tool-heavy agents → end-to-end latency. repeated turns → token economics
measure the bottleneck your workload actually creates
tl;dr of what Together Compiler does, from @realDanFu on @thecompute100:
1/ run the model end to end
2/ find the bottlenecks
3/ let the model fix them
Links below 👇
Learn about Together Compiler: togetherai.link/R7BKfl7
Watch on YouTube: youtube.com/watch?v=V_SbzAxb…
Listen on Spotify: open.spotify.com/episode/0By…
2
908
SVP of Research Dan Fu on @thecompute100 covered:
- what a kernel actually is
- how a 3T-parameter model gets served on day zero
- how Together Compiler uses AI to improve inference
“We’re at a place where the models are good enough now that we can take those models and apply them to our own inference workloads. It’s starting to get to the promise of models that can improve themselves.”
Fun podcast on kernels, origins of @togethercompute, and how we’re using AI to build inference in an RSI inference loop with Together Compiler.
Thanks so much for having me @gabyllorenzi and @BSchech!
2
25
2,913
Up to 2.7× more throughput at the same speed per user.
In our benchmarks comparing Together Compiler vs. the best InferenceX configs on NVIDIA B200 and B300:
→ Kimi K3: 2.7×
→ GLM-5.3: 1.8×
→ DeepSeek V4.1 Flash: 1.8×
→ MiniMax M3.1 Flash: 1.5×
Read more: togetherai.link/R7BKfl7
If you’re comparing models by their price sheet, you’re missing half the math.
Jacob Loewenstein @spatialjlo from NVIDIA explains why token efficiency belongs at the top of your evaluation criteria, whether you’re adopting a model or training your own.
One of the standout moments from Open by Design NYC, where Jacob, Zach Wentz @zkwentz from Reflection, and Hassan El Mghari @nutlope from Together AI chatted with builders digging into open models, post-training, and inference.













