Skip to content

llm

3 posts with the tag “llm”

Smaug open weights: self-improving agents at 10-100x lower cost

Smaug open weights: run self-improving agents at 10-100x lower cost

Section titled “Smaug open weights: run self-improving agents at 10-100x lower cost”

The biggest cost in enterprise AI is not the model. It is the loop: the agent that plans, calls tools, checks its work, and runs again until the job is done. On September 10, Abacus.AI released Smaug, a line of three open-weight models tuned for that long-running agentic loop (Abacus.AI press release). The company says the technique raises agentic-loop performance by 15-20% without raising cost, at prices 10-100x lower than frontier models from Anthropic and OpenAI (Abacus.AI press release). Open weight means the model and the technique are something you can own and run yourself.

Smaug is not one model. It is one fine-tuning technique applied three ways (Unite.AI).

ModelBaseJobSize / detail
Smaug AgenticMoonshot Kimi K3flagship self-improving agentsMoE, 2.8T total / 104B activated params, 1,048,576-token context (Unite.AI)
Smaug FlashDeepSeek V4 Flash 0731personal agents, messaging appsfixes long-context tool-use “spins and confusion”; WhatsApp, Telegram, Slack (Unite.AI)
Smaug Miniopen baseenterprise chatbots, light reasoning27B, multimodal, fine-tunable on your data (Morningstar / PR Newswire)

Smaug Agentic, the largest, is a supervised fine-tune of Moonshot AI’s Kimi K3, a mixture-of-experts model with 2.8 trillion total parameters, 104 billion activated, and a 1,048,576-token context window (Unite.AI). The fine-tune changes no architectural parameters, and it ships under the Kimi K3 license inherited from the base model (Unite.AI). All three models are open-weight on Hugging Face and available through Abacus’s RouteLLM API (Unite.AI).

A long-running agent loop repeats four steps until the task is done: read intent, call a tool, observe the result, then decide the next action. On a frontier model, each pass burns tokens at API rates. The loop fails when the model “spins” and re-fires the same action, or loses the thread in a long tool-use session. Smaug targets that failure point directly. Abacus says the flash variant removes the base model’s spins and confusion in long-context tool use, without losing its cost and speed profile (Unite.AI).

Self-improvement is the second half. Because you can host the model and fine-tune it on your own data, the agent can be retrained on the outcomes it produces, closing the gap between a generic assistant and a tool that knows your systems (Morningstar / PR Newswire).

The pitch is not faster answers. It is control over where the model runs and what it costs.

  • Data stays in your VPC. Abacus says enterprises can host Smaug inside their own cloud VPC, with full control over the data and the hosting location (Abacus.AI press release). No customer prompt crosses your boundary to an external API.
  • Cost scales with open weights. The company frames the price gap as 10-100x against frontier API models (Abacus.AI press release). For a loop that runs for hours, that multiple decides whether the workload is viable.
  • Fines-tuning is a real option. Smaug Mini is built to be further tuned on enterprise data (Morningstar / PR Newswire). You are not locked to a vendor’s weights.

Two caveats are worth stating plainly. Performance numbers come from Abacus’s own announcements, not from an independent benchmark (HPCwire). And a self-improving agent still needs supervision: it will act, so you need review, guardrails, and a rollback path, exactly as you would for any code that ships itself.

  1. Measure your agent-loop cost per completed task, not per token. A 10-100x gap changes what you can afford to automate (Abacus.AI press release).
  2. Treat open-weight hosting as the default for data-bound agents. A VPC-hosted model never leaks prompts to a third party (Abacus.AI press release).
  3. Verify vendor claims against an independent benchmark before you commit (HPCwire’s coverage notes the announcement framing) (HPCwire).
  4. Budget for supervision. Self-improving agents change the game, but they are still code that runs on your infrastructure.

The shift here is quiet and practical. It is not a smartest-model race. It is a cost and custody race: run agents that keep your data, at a price that makes long-running loops boring. That is the kind of boring DevOps can confidently run in production.

DeepSeek V4 Pro Is GA: 1.6T Parameters, 1M Context, and a Price Hike Coming

DeepSeek released the production version of its flagship model this week. Build 0813 ended a preview window that ran nearly four months (Unite.AI). The company formally announced the release on August 13, 2026 (Reuters). DeepSeek models already power the AI chat features on this site. The family’s flagship is now a stable production target.

Calls to the deepseek-v4-pro endpoint now route to the GA build automatically. The endpoint name did not change (AI/TLDR). DeepSeek says the new build “greatly enhances agent capabilities” and is available through the API, the app, and the web (Reuters). The build appeared on OpenRouter’s model page on August 12 (Unite.AI; OpenRouter). API users spotted the swap in the system_fingerprint field, which now returns fp_v4pro_20260812 (r/DeepSeek).

SpecValue
BuildDeepSeek-V4-Pro-0813 (GA, August 12, 2026)
ArchitectureMixture of experts, 1.6 trillion total parameters
Active parameters per tokenAbout 49 billion
Context window1 million tokens
Max output384,000 tokens
AttentionCompressed Sparse Attention + Heavily Compressed Attention
Thinking modesnon-think, think high, think max
Pretraining dataMore than 32 trillion tokens

Sources: GMICloud, Apidog, MindStudio.

The attention design cuts inference cost hard. DeepSeek reports the V4 line runs at 27% of the single-token compute and 10% of the KV cache of V3.2 (Apidog). Long-context workloads are the target, not the edge case.

ItemPrice per million tokens
Input, cache miss$0.435
Input, cache hit$0.003625 (about 120x less)
Output$0.87

Caching is automatic. There is no parameter to enable it (AIHubMix). Teams that reuse long prefixes, like system prompts or document chunks, get the cache-hit rate on every repeated token (Apidog). Concurrency is capped at 500 requests for Pro, versus 2,500 for Flash (GMICloud).

The price holds for now. It will not hold for long. DeepSeek’s pricing page warns that “a significant increase” is coming soon (AI/TLDR). Reuters confirms DeepSeek will raise API pricing for V4 Pro and V4 Flash and introduce peak and off-peak pricing (Reuters).

DeepSeek shipped the family in three steps.

  1. April 24, 2026: the V4 series previewed with open weights for Pro and Flash under the MIT license (Unite.AI).
  2. July 31, 2026: V4-Flash went official first. Flash runs about 300B total parameters with roughly 13B active per token, at $0.14 input and $0.28 output per million tokens (Apidog; Yotta Labs).
  3. August 12, 2026: the Pro flagship went GA as build 0813 (GMICloud).

The order was deliberate. When Flash went official, DeepSeek published agent-benchmark results showing the re-trained small model outscoring the preview Pro on internal coding-agent suites (Unite.AI). Flash became the default agent workload model. The 0813 build is the flagship’s answer.

The V4 series is trained for agentic work: coding assistants, multi-step automation, and long-document synthesis (Unite.AI). The price gap to the frontier is the headline. V4 Pro runs about $0.435 in and $0.87 out per million tokens, against roughly $10.50 per million tokens for Gemini 3 Pro (MindStudio). That is a 50 to 60 times spread on the same class of agentic tasks (MindStudio).

Benchmarks back the value claim. Official scores put V4 Pro on top of Cybergym (83.3) and a terminal automation benchmark (31.8), with a modest gap to leaders on HLE and NL2Repo (MindStudio). Independent testing on a custom coding and agentic benchmark measured 76.25%, up from the preview’s 24.8% (MindStudio).

Integration is a one-line change for most stacks. The API is OpenAI-compatible, so the openai SDK works with model="deepseek-v4-pro" (Apidog). Anthropic Messages format and DeepSeek’s own Responses API also work (Apidog). Thinking modes return a reasoning_content field alongside the answer (Apidog).

One open item: weights. Hugging Face still hosts the April preview builds. DeepSeek has not announced a timeline for publishing the 0813 weights (Unite.AI). The stated cadence for the V4 line runs through the API first.

  1. Track the build, not the endpoint name. deepseek-v4-pro moved from preview to GA with zero code change on your side. If you need reproducibility, log the system_fingerprint so you know which snapshot served a response.
  2. Structure prompts for cache hits. Keep system prompts and document prefixes stable. The 120x cache gap decides whether this model is cheap or not (Apidog).
  3. Budget for the hike now. The increase is announced, with peak and off-peak pricing to follow (Reuters). Model your cost at 1.5x to 2x the current rate.
  4. Match the model to the load. Flash carries high-throughput traffic at 2,500 concurrent requests (GMICloud). Pro earns its 500-cap on long-context reasoning and heavy agent loops.
  5. Do not wait on self-hosting. The 0813 weights are not published. If you need open weights today, the April previews are what exists (Unite.AI).

This continues the cost story from our post on routing cloud AI instead of burning it. The economics just got sharper: a frontier-class agent model at cache-hit prices is now a default, not a bargain.

Qwen3.8-Max: 2.4 Trillion Parameters, 1M Context, Open Weights Next Week

Alibaba shipped its largest AI model ever on August 3, 2026. Qwen3.8-Max packs 2.4 trillion parameters and a 1M-token context window, and its weights go open source next week. The story topped Hacker News at 571 points and lifted Alibaba shares 6% in a day (Reuters, 2026).

Qwen3.8-Max is a Mixture-of-Experts flagship. It is the most capable model the Qwen family has released (Qwen, 2026). It reads text, images, and video, and it plans, executes, and verifies work inside one long conversation (QwenCloud, 2026).

Two details matter for engineers. First, this is the first Qwen-Max-class model to go open weights (Qwen, 2026). The weights land next week, together with Qwen3.8-27B, a smaller model aimed at local and self-hosted deployments. Second, the API price undercuts the closed frontier at $2 per 1M input tokens and $6 per 1M output tokens (QwenCloud, 2026).

The model exposes a reasoning_effort dial with xhigh, medium, and low settings. You trade reasoning depth against cost per request (Qwen, 2026). Alibaba claims the model trails only Anthropic’s Claude, and benchmark coverage puts it level with Claude Fable 5 and ahead of GPT-5.6 Sol on several tests (Bloomberg, 2026; Neowin, 2026).

Qwen also demoed a 10+ day autonomous coding run. The model built the oh-my-cli project from scratch, including a self-evolving harness, without human intervention (Qwen, 2026).

Open weights change the deployment math. A frontier-class model you can host, fine-tune, and keep behind your own firewall changes what AI in CI/CD can mean. Alibaba and MiniMax both moved to open-source releases this week to cut developer costs (Global Times, 2026).

The reasoning_effort dial gives you cost control at request level. Run xhigh for architecture reviews. Run low for routine lint-and-summarize tasks. The 1M context window fits long-horizon agents. A coding agent that holds an entire repo, its test history, and its incident log in one context can work for days without a restart (Qwen, 2026).

The takeaway: frontier-class AI is going open. Watch the weight release next week, then plan which of your pipelines can run on a self-hosted model.