Sakana AI launches Fugu and Fugu Ultra

Fugu inverts the dominant scaling playbook. Rather than train one ever-larger model, Sakana built a comparatively small router LLM that calls other LLMs, including instances of itself recursively, and coordinates them behind a single OpenAI-compatible endpoint ^[1]. When a request arrives, Fugu doesn't necessarily answer it directly; it decides whether to solve the task itself or assemble a team of expert models, then delegates, verifies, and synthesizes a single reply. The orchestration leans on three adaptive roles: a Thinker that plans, a Worker that executes coding and applied tasks, and a Verifier that checks outputs for errors, hallucinations, and requirement compliance ^[1].

MarkTechPost describes the result as an orchestration model that routes tasks across a swappable pool of frontier LLMs ^[6]. Two variants ship through one API: a low-latency base Fugu for everyday work and Fugu Ultra, which marshals a deeper pool of agents for hard, multi-step problems like research, cybersecurity, and patent search. The architecture is grounded in two ICLR 2026 papers, TRINITY and Conductor ^[1]. The practical upshot for a developer is that the complexity of a multi-agent system never reaches their code; it looks, and bills, like a single model.

The timing is the tell. Sakana wrapped the launch in the language of AI sovereignty, and the pitch lands because of recent events: after export controls restricted access to Anthropic's Fable and Mythos models, Sakana argues that relying on a single vendor's API for critical infrastructure has become a material vulnerability rather than a hypothetical risk ^[4]. Because Fugu's agent pool is swappable, the company frames it as a hedge against sudden supply-chain disruption, where the orchestrator simply reroutes to whatever models remain available if a provider is cut off ^[4].

Underneath the messaging sits a sharper strategic logic. Japan lacks the compute scale of the United States and the data scale of China, so Sakana is making an asymmetric bet: a roughly 7-billion-parameter foreman that accesses the world's best models rather than spending billions to train a frontier model of its own ^[5]. That is how a Tokyo lab can claim Fable-and-Mythos-class results without ever training a frontier model itself ^[2]. Whether sovereignty built on top of other companies' closed APIs is a genuine hedge or a relabeled dependency is exactly where the skeptics dig in.

By Sakana's own benchmarks, Fugu Ultra doesn't merely keep pace with the frontier, it edges ahead on the hardest coding and agentic tests. On SWE-Bench Pro it posts 73.7 against Claude Opus 4.8's 69.2 and GPT-5.5's 58.6; on TerminalBench 2.1 it leads at 82.1; and on LiveCodeBench it tops the field at 93.2 ^[2]. It also reports 50.0 on Humanity's Last Exam and 95.5 on GPQA-Diamond ^[1].

The catch sits in plain sight: every one of these figures is self-reported, no independent evaluation has landed yet, and Sakana has not disclosed the ratio of open to closed models behind the scores ^[4]. There is a subtler measurement problem too. Because Fugu is orchestrating models like Opus, GPT, and Gemini under the hood, a benchmark partly credits those underlying models plus the router rather than a capability Sakana trained from scratch. The numbers are real and impressive; the open question is what exactly they are crediting.

The sharpest pushback isn't that Fugu is fake, it's that it may simply relocate the lock-in. Critics argue Fugu trades single-vendor dependency for orchestrator dependency: the orchestrator is closed, the routing is hidden, and a user cannot see or control which model answered a given query or how much it cost ^[4]. Hands-on testing cooled the launch hype, too. One widely cited researcher reported the system was incredibly slow and that results fell short of Fable in practice ^[3].

That skepticism dominated developer reaction. Across developer YouTube and Reddit, the recurring frame was that Fugu is an orchestrator, not a model, with testers flagging steep latency, opaque token consumption, and base-plan usage limits that one user exhausted on a single prompt. The most interesting counter, tellingly, came from inside the skeptical camp: several practitioners argued the lazy dismissal misses the real story, because reaching next-generation performance through a better harness rather than a bigger model is itself the result worth paying attention to. That tension, more than the benchmark table, is what makes Fugu worth watching.