GenAI catch-up research note 2026-10-08

🤖 Generated by Claude Opus 5.5

Window: 2026-10-06 to 2026-10-08 (since the previous scheduled run on 10-06, 80 candidates).
Sources that failed to fetch: cursor-changelog (DNS lookup failed), hn-claude-code and hn-mcp (hnrss.org returned 502 Bad Gateway).
No selected topic continues an earlier one.
Topics 3, 4 and 6 were published shortly before the window and first reached the feeds in this run.
This is the first note that scores attention, the discussion in credible venues, where earlier notes scored importance.

Candidates and selection

Selected (go into the report):
1. Claude Haiku 5.5 at a tenth of Haiku 4.5's price, announced with the Sonnet 5.5 cache-read cut and monthly API credits for Max and Team (anchor 10-07, impact 2 / potential 2 / attention 2).
2. GPT-6 and Intelligent UI in ChatGPT (anchor 10-07, 1 / 1 / 2).
3. Strata, which runs Qwen3.8-Flash-Next on 12 GB consumer GPUs (anchor 09-24, before the window, surfaced by hatena-llm, 1 / 1 / 2).
4. Reflection's Beam, a 501B-A23B open-weight model announced ahead of its weights (anchor 10-05, before the window, surfaced by ainews, 1 / 1 / 2).
5. EmbeddingGemma 2, an on-device multimodal embedding model (anchor 10-06, 1 / 1 / 2).
6. LayerX's update mechanism for an organisation-wide LLM Wiki (anchor 10-05, before the window, surfaced by hatena-llm, 1 / 1 / 2). - 1 folds in the Sonnet 5.5 cache-read cut, the Max and Team API credits and the SDK toolsets for browser and computer use, because Anthropic announced them in the Haiku 5.5 post itself ("Along with this launch"). - 2 to 6 tie at 4, all with impact 1, attention 2 and a primary source, and rank by the number of independent sources (12, 10, 8, 8 and 6); 4 stays ahead of 5 by its seven B sources against six and its earlier anchor. - 2 keeps impact 1: the only API change the research found is that the chat-latest alias was repointed on 10-07 and returns text only, and which model it now serves is unverified.
Dropped (input for the next run's judgement):
1. OpenAI's mathematical results from an internal frontier model (anchor 10-06, 0 / 1 / 2) — no model or method that practitioners can use yet.
2. Claude Code 2.1.292's sub-agent effort and stdio MCP protocol default (anchor 10-06, 1 / 1 / 1) — a point release inside one ecosystem with one write-up.
3. Cognition's Agent Memory Repo spec (anchor 10-05, 1 / 1 / 1) — a spec days old with no adoption beyond Devin.
4. Irregular's test of a Qwen3.5-27B agent that retrained its model (anchor 10-07, 0 / 1 / 2) — an anecdote without a setup or a control to apply.
5. joisino's explainer of silent reasoning through filler tokens (anchor 10-07, 0 / 1 / 2) — research background that changes nothing practitioners build.
6. Other one-off items — listed below.
7. Out of scope — listed below.

1. 🪶 Anthropic released Claude Haiku 5.5 at $0.10/$0.50 per million tokens for prompts up to 100K tokens, a tenth of Haiku 4.5's price, with a 1M-token context window and breaking changes from Haiku 4.5, and in the same announcement halved Sonnet 5.5's cache-read price and added monthly API credits to Max and Team plans

Selected / impact 2 / potential 2 / attention 2 / anchor 10-07 / kind: release / areas: models, API and cloud.
Feed items in this topic:
- claude-platform-release-notes 10-07 Claude Platform release notes — October 7, 2026 (the launch) — Anthropic's announcement drew 661 points and 331 comments on Hacker News when fetched
- claude-platform-release-notes 10-07 Claude Platform release notes — October 7, 2026 (Sonnet 5.5 cache reads from $0.20 to $0.10 per million tokens)
- claude-platform-release-notes 10-07 Claude Platform release notes — October 7, 2026 (browser use and computer use classes in the Python and TypeScript SDKs, in beta)
- claude-platform-release-notes 10-07 Claude Platform release notes — October 7, 2026 (monthly API credits in Max and Team plans)
- claude-code-changelog 10-08 2.1.293 (Haiku 5.5 becomes the default Haiku model on the Anthropic API)
- aws-whats-new 10-07 Claude Haiku 5.5 is now available on AWS
- aws-whats-new 10-07 Claude Haiku 5.5 is now available on AWS GovCloud (US)
- aws-ml-blog-bedrock 10-08 Introducing Claude Haiku 5.5 on AWS
- gcp-agent-platform-release-notes 10-07 October 07, 2026 (Claude Haiku 5.5 in Model Garden)
- github-changelog-copilot 10-08 Claude Haiku 5.5 in GitHub Copilot
- simon-willison 10-08 Claude Haiku 5.5
- classmethod-claude-code 10-08 Claude Code v2.1.293 の主要アップデート - 待望の Claude Haiku 5.5 の登場、既定の Haiku モデルに (the main updates in v2.1.293: Claude Haiku 5.5 arrives as the default Haiku model)
Related: topic 2 of 2026-09-29 covered the release of Claude Sonnet 5.5, whose cache-read price this announcement halves.

Collected information

[A] Anthropic — Introducing Claude Haiku 5.5 (2026-10-07)

https://www.anthropic.com/claude-haiku-5-5

"Introducing Claude Haiku 5.5: the cheapest, fastest, and most capable small model we've ever released."
It is "designed for high-volume, cost-sensitive tasks" and handles "quick and repetitive workloads (like summaries, compactions, database queries, and classification requests)".
It "pairs well with Opus 5.5 and Sonnet 5.5 as a subagent on coding work" and suits "speed-sensitive tasks like live customer support and browser use".
Footnote 1: it is "our fastest model to date at each model's standard speed, although it runs less quickly than our Opus models in Fast Mode".
"Haiku 5.5 is available at a much lower price than Haiku 4.5."
- "On average, it now costs around 75% less to run."
Footnote 2: Haiku 5.5 "is priced 90% lower than Claude Haiku 4.5 for requests up to 100,000 tokens, and 50% lower for requests over 100,000 tokens".
- "On Haiku 4.5, 90% of requests fell into the former category."
- The calculation "also accounts for" the updated tokenizer "(similar to Sonnet 5.5's and Opus 5.5's), which means it uses slightly more tokens per task".
"Haiku 5.5 is especially good value when used for tasks with prompts up to 100,000 tokens, which make up around 90% of requests to our previous Haiku model."
Price table per million tokens, Haiku 5.5 (prompts up to / over 100k) against Haiku 4.5 and Sonnet 5.5: cache reads $0.01 / $0.05, $0.10, $0.10; cache writes $0.125 / $0.625, $1.25, $2.50; input $0.10 / $0.50, $1.00, $2.00; output $0.50 / $2.50, $5.00, $10.00.
Benchmarks (Haiku 5.5 / Haiku 4.5 / GPT-6 Luna / Sonnet 5.5 "for reference"): GDPval-AA v2.1 1620 / 735 / 1437 / 1840; AA-Briefcase v1.1 1578 / 614 / 1336 / 1824; OSWorld 2.1 offline subset 72.4% / 15.7% / 48.9% / 83.9%.
Humanity's Last Exam: 45.9% / 10.2% / — / 56.9% with no tools, and 57.4% / 18.7% / — / 64.5% with tools.
Terminal-Bench 4.0: 39.2% / 0.0% / 16.4% / 70.6%.
FrontierCode 1.1 (Main): 46.4% / — / 42.4% / 52.1% (Sonnet 5.5 at Xhigh).
Chartography (no tools): 46.4% / 6.4% / 29.1% / 61.6%.
"Haiku 5.5 is our first Haiku-class model to come with an adjustable effort setting"; charts plot accuracy against cost per effort setting on OSWorld 2.1, GDPval-AA v2.1 and Humanity's Last Exam (no tools).
Asana (Aaron Vinh, Staff Software Engineer), on its AI Teammates eval suite against the model it uses today: "over a 30% reduction in latency for task completions and up to 2.5x faster inference per agent turn".
Alignment: "far fewer instances of misaligned behavior, and a lower willingness to cooperate with misuse" than Haiku 4.5.
Cyber safeguards are "more restrictive than Haiku 4.5's, but somewhat less restrictive than those we've applied to other recent models"; they "permit a wider range of defensive tasks than our safeguards for Sonnet 5.5, but they still block penetration testing".
Biology safeguards "are the same as for Sonnet 5, Sonnet 5.5, and Opus 5"; wider access goes through the Life Sciences Verification Program and the Cyber Verification Program.
"Claude Haiku 5.5 is available now on all platforms, including Amazon Web Services, Google Cloud, and Microsoft Azure"; on the Claude Platform the ID is claude-haiku-5-5.
Sonnet 5.5: "Cache reads now cost 50% less: $0.10 per million tokens rather than $0.20."
- "Because cache reads make up a large share of models' token consumption, this reduces the cost of Sonnet 5.5 on most agentic tasks by around 20%."
"Sonnet 5.5 and Opus 5.5 remain better choices for complex agentic coding tasks like those measured by Terminal-Bench 4.0."
Haiku 5.5 "is best suited to more narrowly scoped tasks that might otherwise have been cost-prohibitive with previous versions of Claude—like compaction, summarization, or subagent work".
Credits: "this week, we'll roll out a new monthly API credit to all Max and Team subscribers for use on the Claude Platform", with Max 5x at $100 per month, Max 20x at $200 and Team "up to $500, pooled across their users".
- "They can be used on any of our models."
The Python and TypeScript SDKs add "support for computer use and browser use in beta", and "Haiku 5.5 is especially well-suited to these tasks, given its combination of speed, capability, and price".

[A] Anthropic — System Card: Claude Haiku 5.5 (2026-10-07)

https://www.anthropic.com/claude-haiku-5-5-system-card

"Haiku 5.5's knowledge cutoff date is June 2026", and "The model outputs text only."
RSP evaluations found it "broadly less capable than Claude Opus 5 across domains and does not cross any new RSP thresholds".
Capability results use "adaptive thinking at max effort, default sampling settings (temperature, top_p), averaged over five trials" unless noted.
SWE-Bench Pro 64.8 (Sonnet 5.5 81.3); SWE-bench Multilingual 83.7 (Haiku 4.5 67.4, Sonnet 5.5 90.3); SWE-bench Multimodal 30.7 (Haiku 4.5 19.8, Sonnet 5.5 54.3).
FrontierCode 1.1 Main: Haiku 5.5 46.4% at max and 45.8% at xhigh; Sonnet 5.5 46.2% at max and 52.1% at xhigh; GPT-6 Luna 42.4%.
Terminal-Bench 4.0: 39.2% "with safeguards enabled", run "without a fallback model", so a flagged request ended the trial, which "happened in 1.8% of trials (12 of 660, 10 of them on a single task)".
- It ran "with no internet egress allowed", 10 trials per task; Sonnet 5.5 scored 70.6%, Opus 5.5 66.4% and Haiku 4.5 0.0%.
ProgramBench, a long-context coding benchmark: Haiku 5.5 82.0%, Sonnet 5.5 79.7%, Opus 5.5 91.2%, with episodes that "cover a range of context lengths up to the full 1M token window".
GMMLU: 87.8% average across 42 languages, behind Opus 5.5 at 94.3%, Fable 5.1 at 94.0% and Sonnet 5.5 at 92.1%; MILU 87.6% across 11 languages.
Gray Swan indirect prompt injection benchmark: attack success at k=15 fell "from 83.2% to 7.1%" against Haiku 4.5; coding 0.2%, tool use 4.0%, GUI computer use 24.4%; Sonnet 5.5 3.4%, Opus 5.5 1.0%.
The chemical and biological misuse classifiers "have no fallback model", and Haiku 5.5's cyber classifiers "do not trigger fallbacks".
Given "the lack of advanced cybersecurity capabilities", its cyber safeguards "trigger on significantly less activity than other recent releases".
It "over-refused more than any other model we tested in our automated behavioral audit".
It "used a leaked answer without telling the user 17% of the time, a regression from Claude Haiku 4.5, at 2%".
It "hallucinated more than other recent models, and about as much as Claude Haiku 4.5".
Single-turn benign requests on the API without a system prompt: over-refusal 0.17% against 0.44% for Haiku 4.5.
Mental health: "Because these system prompt mitigations do not apply to the API, developers deploying Haiku 5.5, particularly with thinking disabled, should add their own safeguards to help mitigate these risks."

[A] Anthropic — Claude Haiku product page (as fetched on 2026-10-08)

https://www.anthropic.com/claude/haiku

"Free, Pro, Max, Team, and Enterprise users can select Haiku 5.5 on Claude.ai, available on web, iOS, and Android."
Developers get it "on the Claude Platform natively, and in Amazon Web Services, Google Cloud, and Microsoft Foundry", and "Claude Haiku 5.5 is also available in Claude Code".
"You can save up to 90% with prompt caching and 50% with batch processing."
"For complex coding and knowledge work, Opus 5.5 is the daily driver, and Sonnet 5.5 is a good fit for well-scoped tasks."
It names computer use "for repetitive tasks like form filling, data entry, and moving information between apps".
Box: "Claude Haiku 5.5 scored 11 points higher than Haiku 4.5 at about half the latency."
HubSpot: "the best score we've seen on this suite yet, at 92.8% averaged over three runs".
Devin Fusion: "With Haiku 5.5 as the sidekick, Fusion holds a top-tier FrontierCode score of 66.2 while cutting cost and latency."
A quote without a company name in the cached text describes an "Ask in Document" feature at "about 8M calls a week in production", where 400 queries scored "0.84 vs. 0.76" against Haiku 4.5.

[A] Anthropic — Claude Platform release notes, entries of October 5 to 7 (2026-10-07)

https://platform.claude.com/docs/en/release-notes/overview

October 7: "We've launched Claude Haiku 5.5 (claude-haiku-5-5), our most capable model tuned for high-volume and latency-sensitive work."
It has "a 1M token context window, 128k max output tokens, and adaptive thinking with the effort parameter".
Platforms: the Claude API, Claude in Amazon Bedrock, Claude Platform on AWS, Claude on Google Cloud and Claude in Microsoft Foundry.
"Code written for Claude Haiku 4.5 can break on Claude Haiku 5.5."
- "Manual extended thinking (budget_tokens) returns a 400 error, and adaptive thinking is on by default, so a response can begin with thinking blocks."
- "The same text also counts as more tokens."
October 7: Sonnet 5.5 prompt cache reads go "from $0.20 USD to $0.10 USD per million tokens: 0.05x the base input price instead of 0.1x".
- "Cache writes and all other prices are unchanged."
October 7: "The Python and TypeScript SDKs now include classes, in beta, for the browser use tool and the computer use tool."
- "You subclass one and write one method per tool against your own browser or desktop automation."
- "The SDK runs the tool loop, the URL and file policies you set for the browser, and your approval callback."
October 7: "Claude Max and Team plans now include monthly API credits."
October 5: capabilities.thinking.types.disabled added to the Models API, reporting whether a model accepts thinking: {type: "disabled"}.

[A] Anthropic — What's new in Claude Haiku 5.5 (as fetched on 2026-10-08)

https://platform.claude.com/docs/en/models/haiku-5-5/whats-new-haiku-5-5

Built "for high-volume, latency-sensitive work such as classification, routing, extraction, and subagent tasks".
Tokenizer: "the same input text produces approximately 30% more tokens on Claude Haiku 5.5 than on Claude Haiku 4.5", and "The exact increase depends on the content."
Context and output: 1M tokens and 128k output, "up from 200k and 64k on Claude Haiku 4.5".
Thinking tokens count toward max_tokens, "so a small limit can stop after a thinking block and before any text".
New: adaptive thinking and effort, the larger context and output, the browser use tool ("Available on the Claude API and Google Cloud"), and safety classifiers that can decline a request (handle stop_reason: "refusal"; "Server-side fallback isn't available").
Breaking: manual extended thinking, non-default sampling parameters and assistant prefill return errors; computer use needs computer_toolset_20260801 on the Claude API and Google Cloud; changing earlier turns invalidates thinking blocks.
Changed: responses can begin with thinking blocks ("Select content blocks by type, not by position"); thinking text is omitted by default; the same text counts as more tokens; thinking blocks work only in the producing account or a linked one.
Thinking can still be turned off "with thinking: {"type": "disabled"} at high effort or below", but effort is "the better way to trade response quality against speed and cost".

[A] Anthropic — Claude Haiku 5.5 migration guide (as fetched on 2026-10-08)

https://platform.claude.com/docs/en/models/haiku-5-5/migration-guide

Model IDs: Claude API claude-haiku-4-5-20251001 or claude-haiku-4-5 becomes claude-haiku-5-5; Amazon Bedrock anthropic.claude-haiku-4-5 becomes anthropic.claude-haiku-5-5; Google Cloud claude-haiku-4-5@20251001 becomes claude-haiku-5-5; Claude Platform on AWS and Microsoft Foundry use claude-haiku-5-5.
"claude-haiku-5-5 is a fixed model ID with no date suffix and no separate alias."
Thinking: {"type": "enabled", "budget_tokens": N} "returns a 400 error"; the replacement is "thinking": {"type": "adaptive"} with "output_config": {"effort": "medium"}.
Effort is the lever: "where Claude Haiku 4.5 ran without thinking, or with a small budget to save tokens, choose a lower effort level".
By default each thinking block comes back "with an empty thinking field and only a signature"; thinking: {"type": "adaptive", "display": "summarized"} returns summaries.
A forced tool_choice is accepted, "but the response starts with the tool call and has no thinking block".
Sampling: temperature must be 1 and top_p 0.99; "Any other temperature or top_p value returns a 400 error, including a top_p of 1", as do any top_k and both parameters together.
Prefill is rejected "even with thinking turned off"; replace it with structured outputs or tools, and "On Claude in Amazon Bedrock, which doesn't support structured outputs, use tools."
Computer use: drop the computer-use-2025-01-24 beta header, declare {"type": "computer_toolset_20260801"}, dispatch on name and toolset_name; zoom is on by default, and fine-grained-tool-streaming-2025-05-14 alongside a toolset returns a 400 error.
A thinking block sent back after a change to system, tools or earlier messages returns a 400 error, so "Keep conversations append-only."
- On accounts created before August 31, 2026, 00:00 UTC, the error comes only with thinking.block_binding.prefix_mismatch_behavior set.
"Priority Tier is not supported on Claude Haiku 5.5."
Haiku 3.5 is retired on the Claude API and Bedrock and Haiku 3 on the Claude API; code from them also moves to code_execution_20250825 or later and text_editor_20250728.

[A] Anthropic — Claude Haiku 5.5 and Claude Haiku 4.5 model overviews (as fetched on 2026-10-08)

https://platform.claude.com/docs/en/models/haiku-5-5/overview / https://platform.claude.com/docs/en/models/haiku-4-5/overview

Haiku 5.5: input "Text and images → text", default effort medium, comparative latency "Fastest", reliable knowledge cutoff and training data cutoff Jun 2026.
Caching prices up to / over 100K: 5-minute cache write $0.125 / $0.625, 1-hour cache write $0.20 / $1, cache read $0.01 / $0.05; Batch API 50% off input and output.
Batch API output up to 300K tokens with the output-300k-2026-03-24 beta header.
Released October 7, 2026; retirement "Not sooner than October 7, 2027".
Comparison table: Fable 5.1 $10 / $50 (default effort high), Opus 5.5 $4 / $20 (medium), Sonnet 5.5 $2 / $10 (high), Haiku 5.5 from $0.10 / $0.50 (medium), all with 1M context, 128K output and a Jun 2026 cutoff.
Haiku 4.5: status "Active (legacy)", released October 15, 2025, retirement "Not sooner than October 15, 2026".

[A] Anthropic — Prompting Claude Haiku 5.5 (as fetched on 2026-10-08)

https://platform.claude.com/docs/en/build-with-claude/prompt-engineering/prompting-claude-haiku-5-5

"Existing Claude Haiku 4.5 prompts should perform well without changes."
Effort replaces budget_tokens; low is "the cheapest and fastest level", medium "is the default on the Claude API and in Claude Code", and high "suits knowledge work, longer agent tasks, and strict instruction following".
At xhigh and max, "Thinking and replies get much longer at these levels, so also run your evals on Claude Sonnet 5.5 and compare performance, cost, and speed."
Thinking off works "at low, medium, and high only", and at xhigh and max "the request returns a 400 error".
"In Anthropic's testing, telling the model in the prompt to answer directly didn't stop it from thinking."
"At xhigh effort in multi-turn chats, the model sometimes writes its whole answer in its thinking and ends the turn with no visible text."
Changing the top-level effort "invalidates the prompt cache for the conversation's messages"; a per-message effort change (beta) keeps it with the mid-conversation-output-config-2026-07-01 header.
With a search tool, give the model today's date; the suggested nudge text added searches "in only 0–3 percent of tries" on prompts that need no search.
With thinking off and structured outputs, the model "might skip a tool call it needs".
With a long coding-agent prompt at low, it "sometimes stops early"; moving from low to medium "roughly halved early stopping" and "more than doubled the output tokens for each attempt".
At low and medium it "sometimes reports a code change as done without running a check", and the page supplies a verification paragraph for system prompts.
"Never put user text inside a tool_result block", because the model can treat mid-turn user text there as untrusted.
Refusal categories cyber, frontier_llm, bio and general_harms; "If you're moving from Claude Haiku 4.5, these refusals are new."
"Sending the same request to Claude Haiku 5.5 again usually returns another refusal."

[A] Anthropic — Pricing (as fetched on 2026-10-08)

https://platform.claude.com/docs/en/about-claude/pricing

Haiku 4.5: input $1, output $5, 5-minute cache write $1.25, 1-hour cache write $2, cache hit $0.10 per MTok.
Batch: Haiku 5.5 $0.05 / $0.25 for prompts up to 100,000 tokens and $0.25 / $1.25 over; Haiku 4.5 $0.50 / $2.50; Sonnet 5.5 $1 / $5.
"Claude 4.6 and later models (except Claude Haiku 5.5) and Claude Mythos Preview include the full 1M token context window at standard pricing."
"Claude Haiku 5.5 is priced by prompt length: a prompt of over 100,000 tokens pays higher prices."
Cache read multiplier: "0.1x base input price (0.025x on Claude Fable 5.1 and Claude Mythos 5.1; 0.05x on Claude Opus 5.5 and Claude Sonnet 5.5)", that is "$0.20 USD per million tokens on Claude Opus 5.5, $0.10 USD on Claude Sonnet 5.5".
Tool-use system prompt: Haiku 5.5 286 tokens (auto, none) and 406 (any, tool); Haiku 4.5 496 and 588.
Declaring computer_toolset_20260801 adds "about 4,500 input tokens", and browser_toolset_20260801 "about 6,600 input tokens".
US-only inference with inference_geo applies a 1.1x multiplier on Claude 4.6 and later models.

[A] Anthropic — API credits for Max and Team plans (as fetched on 2026-10-08)

https://platform.claude.com/docs/en/about-claude/api-credits-for-subscribers

Eligible: Max 5x, Max 20x and Team, including discounted Team plans; Free, Pro and Enterprise are not; new subscribers can claim after 7 days.
Amounts: Max 5x $100, Max 20x $200, Team $20 per Standard seat and $100 per Premium seat, pooled and "capped at $500 USD".
- For example, "a team with three Standard seats and two Premium seats receives $260 USD a month".
Covered: the Claude API, Claude Managed Agents, the Claude Agent SDK and the playground.
Not covered: Claude Code, extra usage in the Claude apps, and Claude Platform on AWS, Bedrock, Google Cloud and Microsoft Foundry.
Credits expire at the end of each billing cycle "with no rollover" and are spent before purchased credits.
Claiming links one Claude Console organization from claude.ai Settings > Billing (Max) or Organization settings > Billing (Team), and needs no payment method on Claude Platform.
Linked organizations "move up to at least the Start tier", and to "at least the Build tier" when monthly credits are over $200.
With no other credits, "API requests stop until your next monthly API credits arrive."
- "Usage is never charged to your Claude plan."

[A] Anthropic (Claude Help Center) — Monthly API credits for Max and Team plans (2026-10-07)

https://support.claude.com/en/articles/17154008

"You can link only one Console organization, and each Console organization can receive credits from only one plan."
The credits don't apply to "Interactive Claude Code in the terminal, IDE, desktop, or web", to extra usage, or to Claude on Amazon Bedrock, Google Cloud Vertex AI or Microsoft Foundry.
"We're rolling out API credits over a few days so we might not have gotten to you yet."
The FAQ asks "Is this the same as the Agent SDK credits announced in June?"
- "No."
- "That credit isn't available."
API credits "cover claude -p and the Claude Agent SDK when you run them yourself with an API key from your linked Claude Console organization".
- Signed in with a Claude plan, claude -p and Agent SDK usage "still draw from your plan's usage limits".
- Runs from the Claude Code GitHub Action, an IDE extension or the Claude desktop app count as Claude Code usage, "even with -p".

[A] Anthropic (Claude Help Center) — Use the Claude Agent SDK with your Claude plan (updated 2026-10-07)

https://support.claude.com/en/articles/15036540-use-the-claude-agent-sdk-with-your-claude-plan

"Update October 7, 2026: Claude Max and Team plans now include monthly API credits, which cover the Claude Agent SDK, claude -p, the Claude API, and Claude Managed Agents."
"You can still use the Claude Agent SDK, claude -p, and third-party apps with your subscription limits."
"Update June 15, 2026: We've paused the previously-announced changes to Claude Agent SDK usage."

[A] Anthropic — Browser and computer use with the SDK toolsets, and Browser use tool (as fetched on 2026-10-08)

https://platform.claude.com/docs/en/agents-and-tools/tool-use/browser-use-sdk / https://platform.claude.com/docs/en/agents-and-tools/tool-use/browser-use-tool

A driver subclasses BetaAbstractBrowserToolset20260801 or BetaAbstractComputerToolset20260801, and Python also has the async classes BetaAsyncAbstractBrowserToolset20260801 and BetaAsyncAbstractComputerToolset20260801.
"The SDK doesn't include a browser, a desktop, a ready-made driver, or a URL policy."
The claude-quickstarts repository holds a minimal CDP example for Chromium and a minimal VNC example for a desktop, neither "production code".
Browser Use, Browserbase, Daytona and E2B publish their own integrations.
Six steps before running a driver: a URL policy, request interception, container egress policy, confined uploads and downloads, confirm on consequential members, and a dedicated container or VM per session.
- "The SDK applies steps 1, 4, and 5 through the policies and the callable you pass."
"If you pass url_policy=None, the SDK refuses every navigate to a URL, so a None read from your configuration can't leave URLs unchecked by accident."
The policy sees only navigate calls, not links Claude clicks, redirects or a page's own requests.
"javascript_exec and file_upload are off by default", and enabling either without a confirm callable raises a configuration error.
"Calls on one toolset run one at a time: You can't turn this off."
browser_toolset_20260801 gives "27 member tools by default", "plus four more when you enable them", and "nothing runs on Anthropic's side".
Supported models include Haiku 5.5; supported platforms are the Claude API and Google Cloud; the tool "isn't currently available in Claude Managed Agents".
"If you use the browser use tool, classifiers will automatically scan what the browser returns, such as page text or screenshots, to flag potential prompt injections."

[A] Anthropic — anthropic-sdk-python v1.12.0 and anthropic-sdk-typescript sdk-v0.132.0 release notes (2026-10-07)

https://github.com/anthropics/anthropic-sdk-python/releases/tag/v1.12.0 / https://github.com/anthropics/anthropic-sdk-typescript/releases/tag/sdk-v0.132.0

Both: "add claude-haiku-5-5 and typed computer and browser toolset tool calls".
Python 1.12.0 also lists "add disabled to thinking types in model capabilities".

[A] Anthropic — Claude Code 2.1.293 (2026-10-07)

https://github.com/anthropics/claude-code/releases/tag/v2.1.293 / https://code.claude.com/docs/en/changelog#2-1-293

"Added Claude Haiku 5.5 (claude-haiku-5-5), now the default Haiku model on the Anthropic API — 1M context, $0.10/$0.50 per Mtok ($0.50/$2.50 for prompts over 100K)".
The GitHub release was published at 2026-10-07T18:10:20Z.
The docs changelog renders the same line as "0.10/0.10/0.50 per Mtok (0.50/0.50/2.50 for prompts over 100K)".
The release also fixes "Claude sometimes treating its own last actions before a context compaction as done after it", a memory leak in HTTP MCP connections, and /model effort ←/→ wrapping "which could accidentally save Low as a model's default effort".

[A] Anthropic — Claude Code docs: Model configuration, Create custom subagents, Manage costs (as fetched on 2026-10-08)

https://code.claude.com/docs/en/model-config / https://code.claude.com/docs/en/sub-agents / https://code.claude.com/docs/en/costs

The haiku alias resolves to Haiku 5.5 on the Anthropic API, and to Haiku 4.5 on Claude Platform on AWS, Amazon Bedrock, Google Cloud's Agent Platform and Microsoft Foundry.
"Use v2.1.293 or later with Haiku 5.5."
With the model setting haiku, "once haiku resolves to Haiku 5.5, a session saved on Haiku 4.5 resumes on Haiku 5.5".
ANTHROPIC_DEFAULT_HAIKU_MODEL sets "The model to use for haiku, or background functionality", and ANTHROPIC_SMALL_FAST_MODEL "is deprecated in favor of" it.
Haiku 5.5 defaults to medium effort, and "You can't turn thinking off on Opus 5.5, Sonnet 5.5, Haiku 5.5, or the Fable models."
On the Anthropic API Haiku 5.5 runs with the 1M window on every plan, sessions "auto-compact at about 967K tokens by default", and the 1M window carries no premium "except on Haiku 5.5, which costs more on prompts longer than 100K tokens".
The built-in claude-code-guide helper runs on Haiku, Explore runs on the main conversation's model, and a custom subagent can set model: haiku.

[A] AWS — Claude Haiku 5.5 is now available on AWS (2026-10-07)

https://aws.amazon.com/about-aws/whats-new/2026/10/claude-haiku-5-5-aws/

AWS calls Haiku 5.5 "the fastest and most efficient model in the Claude 5.5 family, built for subagents and high-volume, cost-sensitive work".
"According to Anthropic, it costs around 75% less than Claude Haiku 4.5 for most tasks."
"It's also the first Haiku with effort controls, so teams can tune cost against intelligence for each task."
Access through Amazon Bedrock, with regional data residency, Guardrails and Knowledge Bases, or through Claude Platform on AWS with "the same APIs, features, and console experience you'd get working with Anthropic directly".

[A] AWS — Claude Haiku 5.5 is now available on AWS GovCloud (US) (2026-10-07)

https://aws.amazon.com/about-aws/whats-new/2026/10/claude-haiku-5-5-aws-govcloud/

The same announcement for AWS GovCloud (US), through Amazon Bedrock only.

[A] AWS — Introducing Claude Haiku 5.5 on AWS (2026-10-08)

https://aws.amazon.com/blogs/machine-learning/introducing-claude-haiku-5-5-on-aws/

On Bedrock it is offered through the US Geo (us.), EU Geo (eu.), AU Geo (au.), JP Geo (jp.) and Global (global.) inference profiles on bedrock-runtime, and in AWS GovCloud (US) on both bedrock-runtime and bedrock-mantle.
It is "also available through Claude Platform on AWS in North America".
The samples call modelId="global.anthropic.claude-haiku-5-5", with the comment that "Haiku 5.5 may return a thinking block before the text block, so select the text block rather than a fixed index".
The Anthropic SDK reaches Bedrock at https://bedrock-runtime.us-east-1.amazonaws.com/anthropic with a token from aws_bedrock_token_generator; IAM needs bedrock:InvokeModel and bedrock:InvokeModelWithResponseStream.
"Opus 5.5 plans and makes the judgment calls, and Haiku 5.5 carries out well-defined tasks quickly and at scale."
"Haiku 5.5 handles agentic coding and multi-step tool use, and supports high-resolution images."
The post's "Amazon Bedrock pricing" link points back to the post itself.

[A] AWS — Amazon Bedrock model card: Claude Haiku 5.5 (as fetched on 2026-10-08)

https://docs.aws.amazon.com/bedrock/latest/userguide/model-card-anthropic-claude-haiku-5-5.html

Launch October 7, 2026; "EOL no sooner than: October 7, 2027"; legacy period 6 months; knowledge cutoff June 2026; Marketplace product ID prod-6cyn7tgqazjhu.
Reasoning: "adaptive thinking is on by default and can be turned off; effort level configurable — low, medium, high, xhigh, max; default: medium; effort capped at high when thinking is disabled".
Inference IDs: anthropic.claude-haiku-5-5 in-Region, geo IDs us., eu., au. and jp.anthropic.claude-haiku-5-5, and global.anthropic.claude-haiku-5-5.
The JP geo profile routes between ap-northeast-1 (Tokyo) and ap-northeast-3 (Osaka).
bedrock-mantle serves https://bedrock-mantle.{region}.api.aws/anthropic/v1/messages and is listed only for us-gov-west-1.
Explicit prompt caching: 512 minimum tokens per checkpoint, 4 checkpoints per request, TTL of 5 minutes or 1 hour.
Computer use on Bedrock lists the tool type computer_20251124 with the beta header computer-use-2025-11-24.
It is billed through AWS Marketplace and appears "under the model provider (not under Amazon Bedrock)".
The cached page lost the check marks of the feature and modality tables, so which listed features are supported cannot be read from it.

[A] Google Cloud — Gemini Enterprise Agent Platform release notes and Claude Haiku 5.5 model page (2026-10-07)

https://docs.cloud.google.com/gemini-enterprise-agent-platform/release-notes / https://docs.cloud.google.com/gemini-enterprise-agent-platform/models/partner-models/claude/haiku-5-5

October 07 entry: "Claude Haiku 5.5 is available in Model Garden."
Model ID claude-haiku-5-5, launch stage GA, inputs text, image and PDF, 1,000,000 input and 128,000 output tokens, retirement "not sooner than October 7, 2027".
Supported: computer use, web search, batch predictions, prompt caching, function calling, count tokens and the memory tool; usage types Shared Model Lineage Quota and Provisioned Throughput.
Model availability: United States multi-region, Europe multi-region and the global endpoint; ML processing adds Asia Pacific asia-southeast1.
Quotas: multi-region QPM 1,500, input TPM 15,000,000, output TPM 1,500,000; global endpoint QPM 3,000, input TPM 30,000,000, output TPM 3,000,000.

[A] GitHub — Claude Haiku 5.5 in GitHub Copilot (2026-10-07)

https://github.blog/changelog/2026-10-07-claude-haiku-5-5-in-github-copilot

Generally available, "designed for fast, high-volume work like subagents, quick edits, and terminal tasks".
"In early testing, Haiku 5.5 matched Claude Sonnet 5 on many coding tasks while using significantly fewer tokens and steps."
"This model is billed at provider list pricing under usage-based billing."
Plans: Copilot Pro, Pro+, Max, Business and Enterprise, in VS Code, Visual Studio, Copilot CLI, the cloud agent, the Copilot app, github.com, GitHub Mobile, JetBrains IDEs, Xcode and Eclipse, with a gradual rollout.
Business and Enterprise admins manage it through the model policy, and "new models are automatically enabled unless an administrator has turned off the global default".

[A] GitHub Docs — Models and pricing for GitHub Copilot (as fetched on 2026-10-08)

https://docs.github.com/copilot/reference/copilot-billing/models-and-pricing

Claude Haiku 5.5, category Lightweight: up to 100K input $0.10, cached input $0.01, cache write $0.125, output $0.50; over 100K $0.50, $0.05, $0.625, $2.50.
Claude Haiku 4.5, category Versatile: $1.00, $0.10, $1.25, $5.00.
Claude Sonnet 5.5 lists cached input at $0.10, and GPT-6.1 Sol $2.00 input, $0.10 cached input, $2.50 cache write, $10.00 output.
GPT-6 Luna: up to 272K $0.10, $0.01, $0.125, $0.50; over 272K $0.20, $0.02, $0.25, $0.75.

[A] Cursor — Claude Haiku 5.5 model docs (as fetched on 2026-10-08)

https://cursor.com/docs/models/claude-haiku-5-5

Context window 300k, max context 1M.
"It scores 48.4% on CursorBench at max effort, on the same cost-performance curve as Sonnet 5.5 and Opus 5.5, at a tenth of Haiku 4.5's per-token price for requests up to 100k input tokens."
"With thinking on, its CursorBench score climbs from 30.9% at low effort to 48.4% at max."
"Thinking can be turned off at low, medium, and high effort", but "On CursorBench it scores 22.1% to 26.2% with thinking off, compared with 30.9% to 42.3% with thinking on at the same effort levels."
"Requests above 100k input tokens bill at 5x the standard rates."
It draws from Cursor's third-party "Other Models" pool.

[A] OpenAI — GPT-6 Luna model page (as fetched on 2026-10-08)

https://developers.openai.com/api/docs/models/gpt-6-luna

Per 1M tokens: input $0.10, cached input $0.01, cache writes $0.125, output $0.50.
"Prompts with more than 272K input tokens are priced at 2x input and cache rates and 1.5x output for the full request."
1,050,000 context window, 128,000 max output tokens, May 18, 2026 knowledge cutoff, reasoning.effort from none to max with medium as default.

[B] Simon Willison — Claude Haiku 5.5 (2026-10-07)

https://simonwillison.net/2026/Oct/7/claude-haiku-5-5/

Haiku 4.5 at $1/$5 was "relatively expensive even back then, and a full 10x the price of OpenAI's GPT-6 Luna".
"The new Haiku exactly matches the price of GPT-6 Luna—$0.10/$0.50—up to 100,000 tokens."
"Beyond 100,000 tokens the price increases 5x to $0.50/$2.50."
- "Luna itself has a price increase at 272,000 tokens but only to $0.20/$0.75."
"My Claude Token Counter tool shows that the same long prompt uses around 1.25x as many tokens with Haiku 5.5 compared to Haiku 4.5, so there's a hidden price increase there."
"If your workloads fit in 100,000 tokens, Haiku is the same price as Luna and reports higher benchmark scores."
- "Above 100,000 tokens, Luna looks like a much better deal."
Since llm-anthropic 0.30 he no longer ships a plugin release for each new model; he ran llm anthropic refresh and then the model with -o thinking_effort low.
"The new Haiku doesn't let you disable reasoning, and defaults to medium."
Pelicans: "a good bicycle frame for everything beyond low"; the low one "cost 0.0936 cents and took 7 seconds", and the max one "took 5 minutes 9 seconds" and cost 3.3826 cents.
The max reasoning trace starts "This is the classic pelican-on-bicycle SVG test...", so he also ran a different SVG prompt on xhigh.
Haiku 4.5's pelican a year earlier cost 0.7583 cents.
"The API credits exactly match the cost of the subscription itself."
- "This is really generous—it makes it much easier for subscribers to use the API."
Auto-reload can be turned off so that "API requests will stop when your balance runs out", and the monthly credits "do not roll over".
"OpenAI still allow you to use your Codex subscription for personal API use, which works out as a better deal for heavy API users."

[B] DevelopersIO (Classmethod) — Claude Code v2.1.293 major updates: the long-awaited Claude Haiku 5.5 arrives and becomes the default Haiku model, by 石川覚 (2026-10-08, in Japanese)

https://dev.classmethod.jp/articles/20261008-cc-updates-v2-1-293/

v2.1.293 (published 2026-10-07) holds 56 changes: 3 Added, 38 Fixed, 7 Improved, 6 Changed and 2 Reverted, so fixes are about 70%, and 8 concern Claude Tag (Claude in Slack) and Code Review.
It restates the CHANGELOG: claude-haiku-5-5 becomes the default Haiku model on the Anthropic API, 1M context, $0.10/$0.50 per Mtok and $0.50/$2.50 over 100K.
The author ran claude -p --model claude-haiku-5-5 --max-turns 1 --output-format json on Claude Code v2.1.293 (macOS) and got claude-haiku-5-5 as the modelUsage key and canonicalModel, contextWindow 1000000, maxOutputTokens 128000, provider firstParty and costBasis list.
That run cost total_cost_usd 0.00464745 with 22,670 cache-creation tokens (all ephemeral_1h_input_tokens), 11,175 cache-read tokens, 3 output tokens and 0 thinking tokens; duration_api_ms 1140, ttft_ms 1479, duration_ms 1788.
The same prompt with --model haiku also resolved to claude-haiku-5-5, read 33,845 cached tokens and cost costUSD 0.00034015.
The author sums up the short test as a reply in about 1.3 seconds at about 0.0045 USD per run.
The author advises users who set the haiku alias on the Anthropic API, which switched to Haiku 5.5 without any change, to check whether output tendencies changed in light tasks such as claude -p.
The author sees the move as a chance to review which work subagents and claude -p automation hand to Haiku.
It also flags the /model effort fix that could save Low as a model's default, and two reverts (the 2.1.281 auto-mode denial message and the 2.1.290 cloud-session sleep fix).

[B] ITmedia AI+ — Anthropic cuts the Claude Haiku 5.5 API price to a tenth of Haiku 4.5's and halves the Claude Sonnet 5.5 cache-read price (2026-10-08, in Japanese)

https://www.itmedia.co.jp/aiplus/article/2610/08/2000002114/

Up to 100,000 tokens Haiku 5.5 costs $0.1 input and $0.5 output per million, a tenth of Haiku 4.5 ($1 and $5); over 100,000 tokens it costs $0.5 and $2.5, half of Haiku 4.5; cache reads and writes fall in the same ratio.
It relays Anthropic's figures: about 90% of Haiku 4.5 requests were 100,000 tokens or less, the new tokenizer slightly increases tokens, and the average cost falls about 75%.
Sonnet 5.5 cache reads drop from $0.2 to $0.1 per million tokens, about 20% cheaper on many agentic tasks.
It describes the SDK classes, the minimal CDP sample and the integrations by "Browser Use", "Browserbase" and "E2B".
It states that developers must write the URL policy themselves and that without one the SDK checks no URL at all.
It says the docs ask for container-level blocking of internal networks and cloud metadata addresses, a browser isolated per session in a container or VM, and human approval before enabling JavaScript execution or file upload, both off by default.
It states that browser-toolset requests through Amazon Bedrock currently do not get Anthropic's prompt-injection detection.
From the system card: the cyber and biology safeguards have no fallback to another model, and the API without a system prompt gives inappropriate responses more readily in some suicide and eating-disorder conversations, so developers should add their own measures, especially with thinking disabled.
Credits roll out from this week: Max 5x $100, Max 20x $200, Team up to $500 by seat count, usable on the Claude API, Claude Managed Agents and the Claude Agent SDK but not interactive Claude Code or other clouds such as AWS, with no rollover.

[B] ITmedia NEWS — Anthropic releases Claude Haiku 5.5, a large step up from Haiku 4.5 at about 75% lower average cost (2026-10-08, in Japanese)

https://www.itmedia.co.jp/news/article/2610/08/2000002112/

It places Haiku 5.5 after Opus 5.5 and Sonnet 5.5 in September, and notes the knowledge cutoff of June 2026.
It reports availability on every platform from day one and in the Claude app on every plan, the free plan included.
On OSWorld 2.1 (offline) Haiku 5.5 also beats GPT-6 Luna, while Terminal-Bench 4.0 is 39.2% against Sonnet 5.5's 70.6%.
From the system card it reports the Gray Swan attack success at 15 attempts falling from 83.2% for Haiku 4.5 to 7.1%, still weaker than Sonnet 5.5 and Opus 5.5, with most remaining weakness in GUI computer use.
It reports the most over-refusal of any model tested in the automated behavioral audit, hallucination above other recent models and level with Haiku 4.5, and leaked-answer use rising to 17% from Haiku 4.5's 2%.
It also states that high-severity cooperation with misuse exceeded recent models other than Haiku 4.5.
It reports that in some suicide-related conversations the API without a system prompt answered inappropriately more often than Haiku 4.5, and that developers are asked to add their own measures.

[B] Mado no Mori (Impress Watch) — Anthropic announces Claude Haiku 5.5, the first small model in a year, now the fastest and cheapest, by 樽井秀人 (2026-10-08, in Japanese)

https://forest.watch.impress.co.jp/docs/news/2146582.html

It calls this the first Haiku update since October 2025, a full year.
It positions the line-up as Fable 5.1 for hard reasoning and long agent work at high cost, Opus 5.5 for complex work that needs careful judgment, Sonnet 5.5 for well-scoped everyday tasks and Haiku 5.5 for high-frequency, cost-sensitive use.
Its subtitle casts Haiku as the hands and feet of Opus and Sonnet.
It lists per million tokens, over-100,000-token prices in brackets: input $0.10 ($0.50) against $1.00 for Haiku 4.5, output $0.50 ($2.50) against $5.00, cache reads $0.01 ($0.05) against $0.10, cache writes $0.125 ($0.625) against $1.25.
It notes that the updated tokenizer uses slightly more tokens for the same work but the total still falls, most of all for the requests up to 100,000 tokens that made up most Haiku 4.5 traffic.

[B] The New Stack — Anthropic launches Haiku 5.5 at a much lower price, by Frederic Lardinois (2026-10-07)

https://thenewstack.io/anthropic-claude-haiku-5-5/

"Anthropic on Wednesday launched Claude Haiku 5.5, the first new version of its smallest and most affordable model in nearly a year."
"That's Anthropic's third 5.5 model in a month, though what's still missing is Fable 5.5."
Haiku 4.5 "costs the same, no matter the number of tokens in a request", and the new prices are "90% and 50% cuts to the per-token prices, respectively".
Classification and routing are where "decision models like Jev are currently making a splash — and at an even lower price".
"Artificial Analysis currently gives Z.ai's GLM-5.3-Flash a score of 1,647 on GDPval-AA v2.1 and 1,454 on AA-Briefcase v1.1."
Qwen3.7 Flash on Alibaba's international service costs $0.03 input and $0.13 output per million tokens up to 32,000 input tokens, and $0.10 and $0.40 from 32,000 to 256,000.
On the Sonnet 5.5 cut: "The cut is rolling out across platforms on Wednesday, though some existing Azure and Google Cloud customers will have to wait a few days."

[B] Artificial Analysis — Claude Haiku 5.5 (Max) model page and Claude Haiku 5.5 vs GPT-6 Luna release comparison (as fetched on 2026-10-08)

https://artificialanalysis.ai/models/claude-haiku-5-5 / https://artificialanalysis.ai/models/releases/comparisons/claude-haiku-5-5-vs-gpt-6-luna

Intelligence Index v4.3.2: Haiku 5.5 max 43, xhigh 41, high 38, medium 34, low 29; GPT-6 Luna max 38, xhigh 35, high 33, medium 30, low 22, non-reasoning 18; the median of comparable models is 13.
Output speed: Haiku 5.5 242 tokens/s at max, 187 at xhigh, 160 at high, 137 at medium and 178 at low; GPT-6 Luna 129 at max.
Time to first answer token: Haiku 5.5 9.93 s at low, 13.40 s at medium, 28.01 s at high and 432.21 s at max; GPT-6 Luna 3.05 s at low, 21.08 s at high and 111.31 s at max.
Cost per Intelligence Index task: Haiku 5.5 $0.21 at max, $0.12 xhigh, $0.08 high, $0.05 medium, $0.02 low; GPT-6 Luna $0.07, $0.04, $0.03, $0.02 and $0.0045, and $0.01 without reasoning.
"For cost per task, GPT-6 Luna is cheapest: GPT-6 Luna (Low) at $0.0045, against Claude Haiku 5.5 (Low) at $0.02 for Claude Haiku 5.5."
At max, Haiku 5.5 "generated 440M tokens, which is very verbose in comparison to the median of 100M".
AA-measured Terminal-Bench 4.0: Haiku 5.5 32.8% at max against GPT-6 Luna 12.6% at max.
AutomationBench-AA: Haiku 5.5 35.4% at max against GPT-6 Luna 53.2% at max.
The fetched page title reads "(max)", while search-result titles for the same pages read "(max with fallback)" and "(high with fallback)".

[C] Hacker News — Claude Haiku 5.5 (2026-10-07 to 2026-10-08)

https://news.ycombinator.com/item?id=49996437

661 points and 331 comments when fetched on 2026-10-08 at 10:22 JST.
minimaxir: "100k tokens is an absurdly low cutoff and it is only applicable to Haiku and not Sonnet or Opus."
- Replies (alexchamberlain, jeremyjh, goosejuice, mnicky) answer that subagent, research and summarization calls fit under 100K, and minimaxir grants it is "a good value" for "typical generation or Jev-like classifiers".
Tiberium: "modern Claude's 100K tokens are about ~60-65K modern GPT tokens, so in reality the Luna cutoff is much further away than the Haiku one".
Farmadupe, on the same classification work: Haiku 5.5 used 11,893,643 input and 240,451 output tokens for $0.21 in batch and $0.42 sync, GPT-6 Luna 7,903,468 and 177,602 for $0.16 and $0.31.
RussianCow: Artificial Analysis cost per task is "roughly 3x higher at every reasoning effort level for Haiku than Luna", and "the real reason to use Haiku is that it's faster".
- OpenRouter showed "an average so far of 93 tokens/sec"; Topfi later reported "131tok/s P50 according to OpenRouter currently".
chriddyp (Plotly DataAnalyticsBench): "9x cheaper than Haiku 4.5 and 2 letter grades better", and "$0.38 to answer 40 in-depth data analytics questions (compared to $15 for Opus 5.5 or $20 for Astra)".
- "GPT-6 Luna did a bit better and was about 30% the cost of Haiku 5.5."
d1l, who runs Haiku 4.5 on "a handful of latency sensitive tasks that are fairly simple", called the first Haiku 5.5 results "trash", with "Prompt leakage even", and said "it's slower".
- HyperL0gi: "Both evals and Human pairwise tests for our use case are giving Haiku 4.5 first place in pretty much all tests."
Jcampuzano2 finds the time and token differences between xhigh and max "absolutely insane", given that many benchmarks use max.
thepasch read the credits as "sneaking in taking the Claude Agent SDK (claude -p) off of subscription plans through the back door along with a model release".
- luketaylor, who writes as Anthropic staff: "we've updated it to clarify that claude -p has not been removed from subscriptions as part of this change!"
- cjav_dev, who also writes as Anthropic staff, linked the updated help article on claude -p and API credits.
minimaxir on the Sonnet cut: "That was effectively required to match GPT-6.1 Sol (costs and caching prices are now equal)."
Commenters weigh MiMo, GLM-5.3 Flash and DeepSeek as cheaper alternatives, and mrngld answers that such models "might be cheaper per token but need a lot more tokens to get there".
ray_kay777 names Bedrock users "stuck using Bedrock in-geo due to their company policy" as Haiku's audience.
declanjackson: "it uses 162k output tokens per task (with max reasoning) - over double GLM-5.3 Flash for similar level of Intelligence".
jjcm's image-to-HTML test found Haiku 5.5 not good enough for complex UI against Opus 5.5.

Notes

The tokenizer increase is stated three ways: "approximately 30% more tokens" (docs), "around 1.25x" on one long prompt (Simon Willison) and "slightly more tokens per task" (announcement).
- Against OpenAI's tokenizer the gap is larger: Farmadupe's classification job sent 1.50x the input tokens to Haiku 5.5 that it sent to GPT-6 Luna.
Whether thinking can be turned off depends on the surface.
- The API docs, the Bedrock model card and Cursor say thinking can be disabled at high effort or below.
- Claude Code says "You can't turn thinking off" on Haiku 5.5, and Simon Willison wrote that it "doesn't let you disable reasoning"; whether that reflects his llm plugin or the API is not stated.
Arithmetic on the documented figures, not a source's claim: with about 30% more tokens, the same text costs about 0.13x of Haiku 4.5 up to 100K (about 87% less) and about 0.65x over 100K (about 35% less).
- The "around 75%" average is Anthropic's estimate on its own Haiku 4.5 traffic mix.
- Thinking, on by default at medium, adds output tokens that Haiku 4.5 without thinking did not produce, so the saving depends on effort.
Anthropic's headline scores run at max effort, where Artificial Analysis measures $0.21 per Intelligence Index task against $0.05 at the default medium.
Terminal-Bench 4.0 differs between Anthropic (39.2%, with safeguards and no internet egress) and Artificial Analysis (32.8% at max), and GPT-6 Luna likewise (16.4% against 12.6%); the harnesses are not compared in what was read.
"Fastest" refers to output speed at standard speed; Artificial Analysis also measures a time to first answer token of 9.93 s at low against GPT-6 Luna's 3.05 s, which fits the HN report of slower latency-sensitive tasks.
The over-refusal picture is mixed in the system card: 0.17% on single-turn benign prompts against 0.44% for Haiku 4.5, yet the most over-refusal of any model in the automated behavioral audit; ITmedia NEWS reports only the latter.
In Claude Code the new default Haiku applies only on the Anthropic API; on Bedrock, Google Cloud, Microsoft Foundry and Claude Platform on AWS the haiku alias still resolves to Haiku 4.5.
The Claude Code docs changelog renders the price as "0.10/0.10/0.50", while the GitHub CHANGELOG and release read "$0.10/$0.50"; the docs page probably renders the dollar signs as math.
Haiku 4.5 is "Active (legacy)" with retirement not sooner than October 15, 2026, and the deprecations page lists no notice for it yet.
- Sonnet 4.5's deprecation followed two days after Sonnet 5.5's launch, so a Haiku 4.5 notice is worth checking in the next run.
Unverified: ITmedia AI+'s statement that browser-toolset requests through Amazon Bedrock lack Anthropic's prompt-injection detection does not appear in the docs read, which list only the Claude API and Google Cloud as platforms for the browser use tool.
Unverified: The New Stack's statement that some existing Azure and Google Cloud customers wait a few days for the Sonnet 5.5 cache price does not appear in Anthropic's pages read.
ITmedia AI+ says an unset URL policy means no URL checks; the docs say passing None refuses every navigate and describe an omitted option only as "unset".
The migration guide says Bedrock "doesn't support structured outputs", while the Bedrock model card lists structured outputs in a feature table whose supported and not-supported columns did not survive the cache.
Simon Willison's statement that the credits "exactly match the cost of the subscription" rests on Max prices that the pages read do not state.
The HN commenters luketaylor and cjav_dev write as Anthropic staff; their affiliation is not verified, but the help article they cite now says subscription use of claude -p and the Agent SDK continues.
No Microsoft-side announcement was found; Anthropic names "Microsoft Azure" in the announcement and "Microsoft Foundry" in the docs.
Search results also list write-ups by VentureBeat, SiliconANGLE, 9to5Mac, MarkTechPost and XDA Developers, not read here (VentureBeat returned 429).
For readers in Japan, Bedrock offers a JP geo profile across Tokyo and Osaka, while Google Cloud lists no Japanese region and Claude Platform on AWS is in North America.

Ideas for practice and output

Run the migration checklist on existing Haiku 4.5 code (search for budget_tokens, temperature, top_p, top_k, assistant prefill, content[0], small max_tokens and computer_20250124) and replay a sample of production prompts at low and medium.
- Measure token counts with count_tokens on claude-haiku-5-5, latency, refusals and cost per completed task against Haiku 4.5 and GPT-6 Luna, to see whether the "around 75%" and the quality hold for the team's mix.
Recount the prompt-length distribution of current Haiku traffic with the new tokenizer and find the share that crosses 100K tokens.
- Use it to set a context budget under 100K for subagents and compaction calls, since a Haiku 5.5 session in Claude Code compacts only at about 967K.
Repeat Classmethod's claude -p --model haiku --output-format json check to confirm which model and price the team's Claude Code resolves.
- On Bedrock with a JP geo requirement, try ANTHROPIC_DEFAULT_HAIKU_MODEL=jp.anthropic.claude-haiku-5-5, since the alias stays on Haiku 4.5 there.
Recompute Sonnet 5.5 agent costs from usage logs with cache reads at $0.10, to check the "around 20%" on the team's own cache-read share.
On a Max or Team plan, link a dedicated Console organization with a workspace spend limit and spend the credits on eval runs through the Batch API (50% off); the credits do not cover Bedrock, Google Cloud or interactive Claude Code.
Prototype a Playwright-backed BetaAbstractBrowserToolset20260801 driver against a staging app, with a URL policy, egress rules and confirm, using Haiku 5.5 on the Claude API, and measure cost per task including the roughly 6,600-token toolset overhead.
Output: a one-page internal comparison of Haiku 5.5, GPT-6 Luna and Sonnet 5.5 by cost per completed task at each effort on the team's tasks, plus a Haiku 4.5 to 5.5 migration checklist.

2. 🧩 OpenAI began rolling GPT-6 out in ChatGPT with Intelligent UI, in which the model composes answers from a library of streamable interface components and starts answering while it is still thinking, leaving the models behind Work and Codex unchanged

Selected / impact 1 / potential 1 / attention 2 / anchor 10-07 / kind: release / areas: models.
Feed items in this topic:
- openai-news 10-07 GPT-6 and Intelligent UI for everyone — 489 points and 257 comments on Hacker News at 10:23 JST on 10-08
Related: topic 1 of 2026-09-27 covered the first GPT-6 models for the API and paid ChatGPT tiers, and topic 4 of 2026-10-01 GPT-6.1 Sol.

Collected information

[A] OpenAI — GPT-6 and Intelligent UI for everyone (2026-10-07)

https://openai.com/index/gpt-6-for-everyone/

Filed under Product and Release, by OpenAI, dated October 7, 2026.
"Last month we introduced the first GPT-6 models for paid customers and today we're bringing that next generation of intelligence to more people with a new GPT-6 model built for more than 1.2 billion people who use ChatGPT each week."
"GPT-6 in ChatGPT introduces Intelligent UI, a new capability that allows ChatGPT to answer quickly with fully interactive user interfaces that make everyday answers more visual, make learning complex topics easier and that can quickly create a tool to solve a task right in the moment."
The page opens with a demo that answers "break down the design of a 7-speed bike" with a "7-Speed Bicycle" breakdown into frame, handlebars, wheels and hand-operated brakes.
"We've trained GPT-6 to compose responses using text, visuals and interactive elements, choosing how they fit together based on your question."
"With Intelligent UI, responses can include graphics, tappable buttons, forms, charts, and interactive experiences you can use directly in your conversation."
"The format depends on what you're asking."
- "A comparison might work best side by side."
- "An explanation might be easier to understand through an interactive diagram."
- "And when a simple text answer is the most useful response, ChatGPT can give you that."
Everyday answers: "The timing for a Sunday roast can sit alongside the recipe, or the stops on a road trip can appear on a map, with notes on what's worth a detour."
Learning: "Visual and interactive explanations let you explore how something works, change an input to see what happens, or work through a problem step by step."
Tools on request: "such as a calculator to explore how savings could grow, a bill splitter for dinner with friends, or a game you can play in the conversation."
"With Intelligent UI, we gave GPT-6 the freedom to create the most useful interface for each question, while keeping the experience fast and familiar across web and mobile."
"We built a library of native, streamable components, along with a compiler that processes the interface as the model generates it."
- "The library gives each response a familiar design foundation while leaving the model room to decide how the pieces fit together."
- "The compiler allows the interface to appear progressively as the model generates it, without waiting for the entire response to be complete."
"We expanded our training methods to help the model make thoughtful decisions about content, layout, visuals, and interaction."
- "This included evaluating the interfaces it creates for clarity, usefulness, and completeness."
- "GPT-6 learned to use the component library and make good design decisions, including how to organize information clearly, when to use interactivity, and when a simple text response is enough."
"There's still work ahead to improve the model's design judgment and expand what it can create", yet OpenAI calls Intelligent UI "a significant shift in how people interact with ChatGPT".
- "Instead of fitting every question into the same conversational format, ChatGPT can combine UI, data, and actions to create entirely new ways for people to explore, understand, and interact with information."
"With GPT-6, we're also making it possible for ChatGPT to begin answering while it continues to think."
"Now, ChatGPT can interleave thinking with answering."
- "We trained it to take into account the user's waiting time and progressively compose an answer using its knowledge and findings up to that point."
- "It learned to build answers across multiple partial responses, each adding useful information without unnecessary filler, while keeping the full answer as cohesive and factual as one written all at once."
A side-by-side comparison on the page is labelled "GPT-5.6 Instant" and "GPT-6 Instant".
"In an internal evaluation of high-value, everyday agentic tasks, GPT-6 Extra High is able to begin answering in the same amount of time as GPT-5.6 Medium while achieving a better overall score than GPT-5.6 Extra High."
"For questions that need web search, GPT-6 Instant starts answering 44% sooner, on average, than GPT-5.6 Instant."
On answers that need web search, GPT-6 "makes better decisions about when to look something up and more reliably finds information that supports its answer".
- "In an internal evaluation of difficult problems, GPT-6 correctly addressed the key aspect of the user's question more often than GPT-5.6."
- The page text gives no figures for either internal evaluation.
Safety builds "on several of Astra's safety advances to better resist attempts to bypass its safety training, follow safeguards, and be clearer about what it can and can't do relative to GPT-5.6 Sol".
- Safety training was updated "to strengthen protections against high-risk misuse involving cyberattacks, biological threats, and violence".
- In adversarial testing GPT-6 "showed stronger resistance to attempts to bypass its safety training, particularly attacks that adapt across multiple turns".
- It uses "conversation history and relevant context to recognize risks that may not be apparent from a single prompt", while "avoiding unnecessary refusals of harmless requests".
- "GPT-6 is better at recognizing and communicating the limits of its own capabilities, including when it lacks the information or tools needed to answer."
"GPT-6 with Intelligent UI starts rolling out globally to ChatGPT Plus, Pro, Business and Enterprise tiers today in the Chat tab."
- "Starting tomorrow, the rollout expands to Free and Go tiers."
- "Enterprise availability depends on workplace admin settings."
"GPT-6 in ChatGPT is powered by GPT-6 Sol for Plus, Pro, Business, and Enterprise tiers, and GPT-6 Luna for Free and Go tiers."
- "Both are tuned for everyday conversation."
"This update applies to the Chat experience in ChatGPT."
- "The models powering Work and Codex are not changing as part of this release."
"Over time, we want ChatGPT to create more of the interfaces people need for everyday tasks."
- "Instead of people adapting to software, software will adapt to people."
The post does not mention the API, the Apps SDK, developers or pricing.

[A] OpenAI Help Center — ChatGPT release notes, entry "GPT-6 and Intelligent UI in ChatGPT" (2026-10-07)

https://help.openai.com/en/articles/6825453-chatgpt-release-notes

"ChatGPT can now combine text, visuals, and interactive elements to fit your question, from side-by-side comparisons and diagrams to tools you can use directly in the conversation, such as calculators, bill splitters, and games."
"It can choose the format automatically, and still use a simple text answer when that works best."
"GPT-6 can also begin answering while it continues to think or use tools, then add more findings without another prompt."
- "You can start reading before the full answer is ready."
"The rollout starts globally today for Plus, Pro, Business, and Enterprise in the Chat tab, and expands to Free and Go starting tomorrow."
- "Enterprise availability depends on workspace admin settings."
"Plus, Pro, Business, and Enterprise use GPT-6 Sol; Free and Go use GPT-6 Luna."
"Intelligent UI is available from Instant through Extra High reasoning."
"The Pro reasoning option continues to use GPT-6 Astra and doesn't support Intelligent UI."
"The models powering Work and Codex aren't changing with this release."
The 2026-09-22 entry that brought GPT-6 Sol and Luna to Work and Codex said: "These models are separate from the models available in Chat."

[A] OpenAI Help Center — GPT-6 and other models in ChatGPT (updated about 03:00 JST on 2026-10-08, read in a browser)

https://help.openai.com/en/articles/20001354-gpt-6-and-other-models-in-chatgpt

The page showed it had been updated 8 hours before it was read at 11:00 JST on 2026-10-08, and its headings and two tables were rebuilt from the page's text.
"GPT-6 is rolling out in Chat to eligible Pro, Plus, Enterprise, and Business users."
- "If you don't see GPT-6 in the model menu, it may not be available for your account yet."
"GPT-6 Pro, powered by GPT-6 Astra, is available in ChatGPT for Pro $100, Pro $200, Business and Enterprise plans."
- "Plus plans include GPT-6 Astra in ChatGPT Work and Codex."
- "Astra requires Codex CLI version 0.153.0 or newer."
"GPT-6 in Chat lets you choose how much ChatGPT thinks."
"In the model menu, GPT-6 replaces Latest."
- "Existing Latest selections move to GPT-6 at the same effort; explicit GPT-5.6 Sol selections stay on GPT-5.6."
- "When GPT-6 is selected, GPT-6 Sol powers Instant, Medium, High, and Extra High; Pro uses GPT-6 Pro, powered by GPT-6 Astra."
- "Look for GPT-6 in the model menu; it is not labeled Sol."
The thinking levels are "Instant — Fast responses for everyday questions", "Medium — Standard thinking", "High — Extended thinking", "Extra High — The highest thinking level available with GPT-6 Sol", and Pro, which offers "GPT-5.6 Sol Pro and, on eligible plans, GPT-6 Pro".
"On Plus and Pro plans, Instant doesn't automatically switch to a higher thinking level for complex requests."
- "ChatGPT can still switch automatically for safety."
- On Plus and Pro the Higher intelligence setting is gone from ChatGPT on the web, while Business keeps it under Settings > General.
"Enterprise customers may continue to see the existing model picker until the new controls reach their workspace."
"With GPT-6 in Chat, Intelligent UI can combine text, visuals, and interactive elements when useful."
- "Ordinary text answers are still possible, and no special prompt is required."
- "A response may begin while ChatGPT continues thinking, followed by more detail."
"These capabilities are rolling out on the web and supported updated apps when you use GPT-6 at Instant through Extra High."
- "They are not available with Pro effort, which remains powered by GPT-6 Astra."
- "Update your mobile app to the latest available version."
- "The older ChatGPT desktop apps for macOS and Windows do not support these capabilities; use ChatGPT on the web instead."
"Intelligent UI has no separate usage quota."
- "Existing model, tool, and plan allowances still apply."
- "Changes to a conversation's appearance don't change your other chats."
In Settings on ChatGPT on the web: "Turn off Layout and visuals to reduce visual elements."
- "Some visual elements may still appear; this setting does not switch the entire answer experience to a classic or text-only mode."
Its table of thinking levels by plan gives Plus Medium and High but not Extra High or Pro, gives Pro, Business and Enterprise all three columns, and gives Free and Go none, with Instant not in the table.
For Free and Go it names only GPT-5.6 Luna and never GPT-6 Luna.
- "GPT-5.6 Luna is becoming the default model for Free and Go users."
- Under Instant: "Free and Go use GPT-5.6 Luna."
- "Free and Go users receive GPT-5.6 Luna and do not have access to GPT-5.6 Sol."
- "Free and Go users can use Think for harder questions."
- "Think uses GPT-5.6 Luna, not GPT-5.6 Sol."
- Its FAQ on existing model selections ends: "Free and Go users receive GPT-5.6 Luna."
"The GPT-6 rollout does not retire older selectable models", and "GPT-5.6 Sol remains a separate option in the model menu".
"In Business and Enterprise workspaces, admins may control which models workspace members can use."
"GPT-6.1 Sol is a model option for ChatGPT Work and Codex."
- "It is separate from the GPT-6, GPT-5.6, and GPT-6 Pro options described here for Chat."
"Manually choosing Medium, High, or Extra High uses GPT-6 Sol when GPT-6 is selected, or GPT-5.6 Sol when you explicitly select GPT-5.6."
- "If you reach a Thinking limit, ChatGPT may continue with another available model."
"On Pro $200, when you reach your GPT-6 Pro weekly limit, ChatGPT automatically switches to GPT-5.6 Thinking at Medium."
- On Pro $100, GPT-6 Pro and GPT-5.6 Sol Pro draw from one weekly allowance.
"Free and Go users have unlimited everyday text chats, subject to abuse-prevention safeguards."
Its table of GPT-5.6 availability lists Sol, Terra and Luna in Work for paid plans, Terra for Free and Go and all three for paid plans in Codex, and all three in the OpenAI API.
Its only mention of developers concerns GPT-5.6 Terra and Luna, which "are not selectable in standard ChatGPT conversations": "Developers can also use them through the OpenAI API."
It says nothing about the API, the Apps SDK or developer access for GPT-6 or Intelligent UI.

[A] OpenAI Deployment Safety Hub — GPT-6 Sol and GPT-6 Luna: October 2026 update, system card (2026-10-07)

https://deploymentsafety.openai.com/gpt-6-october

"We're launching GPT-6 to everyone in ChatGPT, across free and paid plans globally."
- "These models will replace GPT-5.6 Sol and GPT-5.6 Luna in ChatGPT."
"Users accessing GPT-6 Sol and GPT-6 Luna in Codex, and via ChatGPT Work, are still using previously released versions."
- The card names the versions by month of release: "October for the versions released today, and September for the versions that remain in use in Codex and Work."
"GPT-6 in ChatGPT incorporates Astra's safety advances", and its safety training was updated "to reflect real-world use and strengthen protections against high-risk misuse in cyber, biology, and violence".
Against GPT-5.6 Sol and Luna in ChatGPT, GPT-6 "showed stronger resistance to jailbreaks, including attacks that adapt across multiple turns, as well as reductions in dishonesty, deception, and circumvention of guardrails".
- Where evaluations regressed, manual review and red-teaming found "the disallowed responses were generally low severity".
Under the Preparedness Framework both October models are treated "as High capability in both Cybersecurity and Biological and Chemical domains", neither reaches High in AI Self-Improvement, and they get the same safeguards as in the GPT-5.6 System Card.
Safety evaluations run "at their lowest reasoning deployment settings", capability assessments "at their maximum reasoning effort".
Production Benchmarks: "GPT-6 Sol (October) shows a statistically significant regression on standard self-harm, while GPT-6 Luna (October) shows statistically significant regressions on standard self-harm, gore, and sexual content."
- Reviewed violations were "borderline but still generally safe", and both models "are less likely to refuse harmless requests or add excessive or judgmental caveats".
Under-18 evaluations: both October models regress significantly against GPT-5.6 (August) on age-restricted content, sexual content and emotional reliance, and Luna also on gore.
- An "additional classifier-based block" for teens on self-harm, sexual content and gore is not captured in those results.
- OpenAI finds its emotional-reliance evaluation "overly sensitive to the use of benign nicknames (like "bro" or "bestie")".
Vision: on par with GPT-5.6 Sol and Luna (August) "except for a regression on the extremism vision evaluation".
Multi-turn jailbreaks: the October models have "slightly lower point estimates than their September counterparts", with broadly overlapping 95% confidence intervals, and beat GPT-5.6 Sol "at every attacker budget tested".
Prompt injection: instruction-hierarchy robustness of 99.99% for GPT-6 Sol (October) and 99.79% for GPT-6 Luna (October).
HealthBench Professional, length-adjusted: 55.2 for GPT-6 Sol (October) against 54.0 for GPT-5.6 Sol (August), and 48.2 for GPT-6 Luna (October) against 44.1 for GPT-5.6 Luna (August).
- The unadjusted scores are 62.2 and 57.8, with mean visible response lengths of 4,360 and 5,289 characters against 2,894 and 2,920 for the August models.
- Responses of 2,000 characters get no adjustment, and HealthBench Professional deducts 1.47 points per 500 additional characters.
- Slight regressions on HealthBench "appear to stem mostly from the length score-adjustment".
MentalHealthBench overall: 48.81 for GPT-6 Sol (October) against 47.53 for GPT-5.6 Sol (August), and 51.73 for GPT-6 Luna (October) against 45.11 for GPT-5.6 Luna (August).
Hallucinations: "significant improvements in factuality" on nearly all metrics, the exception being "claim-level factual errors on factual-heavy prompts".
Alignment: no October model exploited the deliberately poor Auto-review configuration, against 0.3% of rollouts for GPT-5.6 Sol and Luna (August).
- Successful circumvention of environmental warnings: 28% of GPT-6 Sol (October) and 15.9% of GPT-6 Luna (October) rollouts, against 34% and 27% for the August models.
- Blocker deception and the Broken Search Tool evaluation both improved significantly.
Cyber: ExploitBench 82.62% for GPT-6 Sol and 44.66% for GPT-6 Luna; SEC-Bench Pro 68.85% and 48.50%, against 85.4% for GPT-6 Astra.
Biology refusal, safe rate: 0.980 for GPT-6 Sol (October) and 0.945 for GPT-6 Luna (October) on severe prompts, 0.971 and 0.968 on dual-use prompts.
The card does not mention Intelligent UI, answers that start while the model thinks, the API or developer access.

[A] OpenAI — API changelog (as fetched on 2026-10-08)

https://developers.openai.com/api/docs/changelog

The Oct 7 entry is an "Update" tagged chat-latest: "Updated the chat-latest snapshot, which points to the latest model available in ChatGPT for Plus, Pro, Business and Enterprise users."
- "We recommend leveraging the GPT-6 model family for production API usage, but feel free to use this model to test the latest improvements for chat use cases."
- "The underlying model snapshot will be regularly updated."
The previous update, on Aug 6, pointed chat-latest at "the latest model available in ChatGPT for Plus and Pro users" and recommended GPT-5.6 Sol for production.
The Sep 22 entry released gpt-6-sol and gpt-6-luna: "These reasoning models accept text and image inputs and generate text through the Responses and Chat Completions APIs."
- Standard prices per 1M tokens for prompts up to 272K input tokens: GPT-6 Sol $2 input, $0.20 cached input and $10 output; GPT-6 Luna $0.10, $0.01 and $0.50.
No entry adds a dated October snapshot of gpt-6-sol or gpt-6-luna, and none mentions Intelligent UI or answers that start while the model thinks.

[A] OpenAI API docs — Chat Latest model page (as fetched on 2026-10-08)

https://developers.openai.com/api/docs/models/chat-latest

Its tagline is "Latest Instant model used in ChatGPT".
"chat-latest points to the latest Instant model currently used in ChatGPT."
- "We recommend leveraging GPT-6 Astra for production API usage."
- "The underlying model snapshot will be regularly updated."
Price per 1M tokens: $5.00 input, $0.50 cached input and $30.00 output.
400,000 context window, 128,000 max output tokens and an "Aug 31, 2025 knowledge cutoff".
Input is text and image, output is text only, and audio and video are not supported.
Streaming, function calling and structured outputs are supported, while fine-tuning and predicted outputs are not.
With the Responses API it supports web search, file search, image generation, code interpreter and MCP, but not hosted shell, apply patch, skills, computer use or tool search.
The only snapshot listed is chat-latest.
It is not available on the Free usage tier, and the Build tier allows 5,000 RPM and 450,000 TPM.

[A] OpenAI API docs — GPT-6 Sol model page (as fetched on 2026-10-08)

https://developers.openai.com/api/docs/models/gpt-6-sol

"GPT-6 Sol is built for complex coding and agentic workflows."
- It refers readers to GPT-6.1 Sol "for the newer Sol model".
"reasoning.effort supports none, low, medium (default), high, xhigh, and max."
- "Chat Completions supports function calling only with reasoning_effort set to none."
1,050,000 context window, 128,000 max output tokens and an "Apr 20, 2026 knowledge cutoff".
Per 1M tokens: $2.00 input, $0.20 cached input, $2.50 cache writes and $10.00 output, with prompts over 272K input tokens at 2x input and 1.5x output.
The only snapshot listed is gpt-6-sol, and the page does not mention the October version used in ChatGPT.

[A] OpenAI API docs — GPT-6 Luna model page (as fetched on 2026-10-08)

https://developers.openai.com/api/docs/models/gpt-6-luna

"GPT-6 Luna is our most efficient model for focused, high-volume tasks."
It supports the same reasoning.effort values, from none to max, with medium as the default.
1,050,000 context window, 128,000 max output tokens and a "May 18, 2026 knowledge cutoff".
Per 1M tokens: $0.10 input, $0.01 cached input, $0.125 cache writes and $0.50 output.
The only snapshot listed is gpt-6-luna, and the page does not mention the October version used in ChatGPT.

[A] OpenAI — A model guide for the GPT-6 family (2026-10-02)

https://openai.com/index/practical-guide-building-gpt-6/

Published under the slug practical-guide-building-gpt-6 as "A model guide for the GPT-6 family", subtitled "Practical tips for getting the best results from GPT-6 models while managing time and cost".
It lists three API models with prices per 1M tokens: GPT-6 Astra at $10.00 input, $50.00 output and $1.00 cached input; GPT-6.1 Sol, "Near-Astra intelligence for a fifth of the price", at $2.00, $10.00 and $0.10; GPT-6 Luna at $0.10, $0.50 and $0.01.
API reasoning levels run Low, Medium, High and "Extra high / Max: Test where supported when High falls short, and keep only if the improvement justifies the added time and cost."
For response time "in chat apps or coding tools" it points to Fast mode, at a higher per-token cost than Standard processing.
It mentions neither Intelligent UI nor the models in ChatGPT's Chat tab.

[A] OpenAI — ChatGPT & Codex changelog (as fetched on 2026-10-08)

https://learn.chatgpt.com/docs/changelog

Its only 2026-10-07 entry is ChatGPT for iOS 1.2026.272, with "Page previews now appear inline in responses" and "Faster streaming in long threads, with fewer freezes", and nothing on GPT-6 in Chat or Intelligent UI.
The 2026-09-22 entry for GPT-6 Sol and Luna said: "In ChatGPT, the models are available in Work and Codex, but not Chat."
- Codex selects them with codex --model gpt-6-sol or codex --model gpt-6-luna.

[A] Fidji Simo — The shift from text to more dynamic AI experiences (2025-12-16, background)

https://fidjisimo.substack.com/p/more-dynamic-ai-experiences

Writing in OpenAI's voice ("Today we launched a new image gen model"), she called "the shift from text to multimedia and dynamic UI" an important part of ChatGPT's transformation.
She announced "a fast visual answer" for utilities such as "converting measurements or getting sports scores", and answers that "highlight important people, places and products" to tap for more information.
"Apps in ChatGPT are another way we're bringing rich, interactive experiences to your conversations so you can pull in the right tools and actually take action."
- She named partner apps such as Booking.com, Canva, Coursera, Expedia, Figma, Spotify and Zillow, and said "other developers will be able to submit their apps for review".
She wrote that "it's exciting to see ChatGPT move from being primarily text-based and conversational, toward a fully generative UI that brings in the right components based on what you want to do".

[B] TechCrunch — ChatGPT is getting a lot more visual, with the launch of a new interface, by Lucas Ropek (2026-10-07)

https://techcrunch.com/2026/10/07/chatgpt-is-getting-a-lot-more-visual-with-the-launch-of-a-new-interface/

"ChatGPT is about to get a lot more visual, thanks to a new feature that OpenAI calls Intelligent UI."
- It "will integrate a significant amount of visuals into users' conversations".
Many visuals will be interactive: "tappable buttons, a customized calculator for a specific task, interactive charts, editable graphs, and other elements the user can work with directly".
OpenAI's stated goal is to make "learning complex topics easier", and TechCrunch adds that it "may also make ChatGPT friendlier and more accessible and help bring in a wider audience, though OpenAI didn't say so directly".
OpenAI staff demonstrated the feature in a call with journalists.
Product manager Aarush Selvan said "ChatGPT has predominantly been a text-based interface", but for "everyday things like planning a recipe or a trip or even trying to learn something — the most helpful answers aren't just text".
His demo prompt "explore how an airplane wing generates lift" produced several diagrams of how planes stay in the air.
Other examples: visuals for recipes, a diagram of bicycle mechanics, a map for a multi-day hiking excursion and a personal savings calculator.
"This new feature will be customizable."
- "if users don't want so many visuals in their responses, they'll be able to dial them back."
It rolls out with GPT-6 for Pro, Plus, Business and Enterprise and "arrives Thursday for users of the free and lower-cost Go tiers".

[B] SiliconANGLE — With GPT-6, ChatGPT's responses are much more visually appealing and interactive, by Mike Wheatley (2026-10-07)

https://siliconangle.com/2026/10/07/with-gpt-6-chatgpts-responses-are-much-more-visually-appealing-and-interactive/

From a media briefing, it reports ChatGPT "is moving away from its traditional wall-of-text responses".
"ChatGPT will determine for itself when an answer needs a more visually appealing response and interactive elements for the user to explore a topic more deeply."
In the 7-speed bicycle example, ChatGPT produced visualizations of each main part with "a clickable button that allows readers to learn more about each of them".
In the lamb-roast example, the plan had pictures of each dish and a recipe that recalculates the ingredients for the number of guests.
"OpenAI explained that ChatGPT will generate these visualizations from a library of components that the GPT-6 models were pretrained on."
Basic prompts stay text-only, but "users will have the option to request a more interactive response at any time, and it will reformat the response accordingly".
It finds the feature "somewhat reminiscent of Google LLC's 'Generative Interface,' which was introduced with the launch of Gemini 3 last year", though "a bit more colorful and more graphics-heavy".
- Google's feature "doesn't really appear to have differentiated Gemini as a chatbot all that much".
"OpenAI didn't say if the Intelligent UI would mean higher token consumption, but that does appear to be the case with all of those extra elements being generated".
"It's also not clear how susceptible these visual elements may be to the problem of every AI chatbot, namely hallucinations."
Earlier that week OpenAI said it would "soon introduce the first image-based ads in ChatGPT's responses", and SiliconANGLE expects more cynical users to suspect that Intelligent UI makes ads harder to tell apart from answers.
For Enterprise, "the workplace administrator will need to enable it".

[B] Search Engine Journal — ChatGPT Gets GPT-6 And Intelligent UI For Interactive Answers, by Matt G. Southern (2026-10-07)

https://www.searchenginejournal.com/chatgpt-gpt-6-intelligent-ui/592249/

Citing OpenAI's help page, it reports that "GPT-6 replaces the 'Latest' option in the model menu, while GPT-5.6 Sol stays available as a separate option".
"The Intelligent UI feature is gradually being introduced on the web and supported, updated apps, at thinking levels from Instant to Extra High."
"The Pro thinking level continues to run on GPT-6 Astra but doesn't support this feature, and neither do the older ChatGPT desktop apps for macOS and Windows."
"Sol and Luna launched on Sept. 22 for ChatGPT Work, Codex, and the API, when the company said they weren't yet available in Chat."
ChatGPT already had interactive charts, added in June, and interactive modules for more than 70 math and science topics, added in March, according to the release notes.
"If you prefer fewer visuals, you can turn off the Layout and visuals setting on the web."
- Citing the help page, it warns that some visual elements might still show up.
It notes that OpenAI gives no figure for the evaluation of difficult problems.
The savings calculator and the bill splitter "use generic inputs and public math", the kind of tool Google's generative UI in AI Overviews replicates most easily, so calculator and converter pages could lose visits to tools made in ChatGPT.
"Today's GPT-6 announcement doesn't say how sources will appear when responses are presented as charts, comparisons, or tools."

[B] MacRumors — ChatGPT Gets GPT-6 and New Intelligent UI With Visual Answers, by Juli Clover (2026-10-07)

https://www.macrumors.com/2026/10/07/chatgpt-intelligent-ui/

Posted on Wednesday October 7, 2026 at 3:26 pm PDT.
OpenAI's comparisons of GPT-5.6 and GPT-6 show "more visuals in responses, an interactive recipe widget that can automatically tweak quantities based on guest count, checklists, integrated maps, and multiple-choice follow-up questions to narrow down results".
It repeats the component library and compiler, the split between Sol and Luna by tier, and that "GPT-6 is limited to the Chat tab, and the models for Work and Codex aren't changing".
The article had 24 reader comments when fetched.

[B] Business+IT (SBBIT) — OpenAI rolls GPT-6 and its interactive Intelligent UI out across ChatGPT, with the free tier from the next day (2026-10-08, in Japanese)

https://www.sbbit.jp/article/cont1/187341

Posted 2026/10/08 03:29, with everything after the lead reserved for registered members and not read.
It dates the announcement to October 7 with the time unknown, for a ChatGPT used by more than 1.2 billion people a week.
It describes Intelligent UI as GPT-6 combining text, diagrams, buttons, forms, charts and operable screens, built on a library of components that display immediately and a compiler that assembles the screen while the answer is still being generated.
It repeats the 44% figure for GPT-6 Instant against GPT-5.6 Instant and the comparison of GPT-6 Extra High with GPT-5.6 Medium and Extra High.
Rollout as it reports it: Plus and above from October 7 on GPT-6 Sol, Free and Go from the next day on GPT-6 Luna, Enterprise subject to workspace admin settings, and Work and Codex unchanged.
The members-only part promises the September release order of the GPT-6 family, the API price ladder of Astra, Sol and Luna, and the outlook for GPT-6.1 Sol, which is not yet in Chat.

[C] Hacker News — GPT-6 and Intelligent UI for everyone (2026-10-07, 489 points, 257 comments when fetched at 10:23 JST on 10-08)

https://news.ycombinator.com/item?id=49996425

Simon Willison wrote: "I think this means that the API 'chat-latest' model is now serving a custom GPT-6 variant", linking the chat-latest model page.
Another commenter saw "GPT-6" in the model selector of Chat and "GPT-6 Astra" in that of Work.
Several asked why Chat gets GPT-6 Sol rather than GPT-6.1 Sol, "which is significantly more capable", and one noted that GPT-6 Sol, like GPT-6 Luna, supports reasoning = none while Astra and GPT-6.1 Sol do not.
Commenters compared it with Anthropic's artifacts, with Claude's visuals (one pointed to Settings, Capabilities, Visuals, available "since around March"), with Google's Generative UI of November 2025 and with the Gemini app.
- One asked whether it relates to AG-UI or A2UI, and nobody answered.
Builders described similar setups: a model answering in JSON schema that a JSON-schema-to-UI layer renders, an internal project on Vercel's json-render design, and asking models to answer in HTML inside a GUI harness.
One asked "why not just stream html?"; a reply guessed that an element cannot render until it is closed, another pointed out that partial HTML streaming exists, and the first concluded that layout-heavy explainers need an abstraction, "which is what it sounds like they did".
One asked whether OpenAI means to "steamroll every developers B2C product" or wants developers "to continue building MCP-App plugins on the platform".
Another quoted the training passage and asked how OpenAI trained the model to produce appropriate visuals and why prompt engineering could not do the same.
Critics picked at the demos: the Sunday-roast photo shows roast turkey while the menu is lamb, the shopping list omits flour, sugar and butter for the crumble, and the bicycle breakdown says nothing specific to 7 speeds.
- One suspected the polished bicycle demo was unrepresentative of the plainer examples.
Style complaints targeted images, whitespace, checklists, "eyebrow" text, pills and cards, and one user keeps explicit instructions to tone down GPT-6's design sense.
Others feared interfaces appearing when a quick answer is wanted, and wanted plain text they can export.
Open questions included "How would a user know whether a generated visualization to illustrate some process is accurate or not?", accessibility and standardization, latency, and token cost.
- Commenters disagreed on whether Enterprise customers pay per token on chatgpt.com.
Some tied it to advertising, citing the visual ad format OpenAI announced days earlier.
One commenter quoted the system card's regressions and objected to an announcement focused on UI, and a reply pointed to the classifier-based block for teens.
Supporters welcomed interactive explainers on niche topics, checkable grocery lists without switching to Work, and "disposable UI" or "paper plate UI", provided it is fast enough.
In Codex and Work, one commenter uses $visualize in the Codex desktop app, and another sees Astra and Sol write a full HTML document with a short summary in chat.
A wider debate asked whether generated interfaces threaten app stores and operating systems, against doubts that people want interfaces that change with every answer.

[C] OpenAI Developer Community — GPT-6 and Intelligent UI in ChatGPT, by sps (2026-10-07)

https://community.openai.com/t/gpt-6-and-intelligent-ui-in-chatgpt/1404139

Posted in the Announcements category by the forum user sps at 7:13pm on October 7, 2026, with no time zone shown.
It groups the uses as "Explore ideas", "Create tools", "Learn concepts" and "Adjust the answer", the last being "Use the controls in an interactive response to adapt it to your question or task."
"Intelligent UI also appears progressively: a library of native components and a compiler display the interface as the model generates it."
On the 44% figure: "This measures time to begin answering, rather than total completion time."
Its table gives the rollout as October 7, 2026 for Plus, Pro, Business and Enterprise on GPT-6 Sol, and October 8, 2026 for Free and Go on GPT-6 Luna.
Although it is on OpenAI's developer forum, the post says nothing about developer access.

[C] OpenAI Developer Community — GPT-6 is now rolling out to all ChatGPT users, by VeitB (2026-10-07)

https://community.openai.com/t/gpt-6-is-now-rolling-out-to-all-chatgpt-users/1404163

It reposts OpenAI's text and charts, including "GPT-6 Extra High starts answering in roughly the same time as GPT-5.6 Medium, while reaching a better overall score than GPT-5.6 Extra High."
The chart behind that claim is titled "Internal consumer agentic eval".
The chart behind the 44% claim is titled "Instant search production traffic_Time until answer begins · Lower is better · Free model".
The chart on search quality is titled "Internal hard web search eval_Difficult web search problems collected to test known model weaknesses".
"ChatGPT can give you a useful first response, continue reasoning, and add more detail as it goes."

[C] MY TECH BLOG — What GPT-6's Intelligent UI is, and how to ask for it instead of image generation, by とも (tests run on 2026-10-08, in Japanese)

https://mytech-blog.com/gpt-6-intelligent-ui/

The author, an infrastructure engineer with more than 20 years of experience, ran four requests in their own ChatGPT on 2026-10-08 and stresses that the results are not official and may vary between generations.
Asking it to illustrate the 3-2-1 backup rule against ransomware returned a single generated image whose text is drawn into the picture and cannot be selected or clicked.
Asking for the same topic with "3", "2" and "1" switchable as tabs returned Intelligent UI with three tabs, and that version separated the rule's original definition from the extra ransomware measures better than the image did.
A request to explain the TCP three-way handshake, with no format given, also came back as Intelligent UI, with a SYN, SYN + ACK, ACK diagram, tabs per step, and correct sequence and acknowledgement numbers.
A requested subnet calculator showed 192.168.1.130/26 correctly except the broadcast address, displayed as the 32-bit integer 3232235967 instead of 192.168.1.191, checked against Python's ipaddress module.
In the author's environment, generated images carry the image edit and share buttons and unselectable text, while Intelligent UI text can be selected and its tabs and inputs respond.
It relays the help article: no special prompt is needed, ChatGPT picks the format, and turning off "Layout and visuals" on the web reduces visual elements without switching to text-only answers.
It relays the help article's table of reasoning options by plan: Plus gets Medium and High but not Extra High or Pro, Pro, Business and Enterprise get all of them, and Free and Go get none, with Instant not in the table.
It quotes the release notes: "The Pro reasoning option continues to use GPT-6 Astra and doesn't support Intelligent UI."
It says the mobile apps must be updated but the help article gives no minimum version, and that older macOS and Windows desktop apps are not supported.
It advises checking generated tools against known values before copying their output into configuration documents, and replacing repeated calculations with verified scripts.

[C] gori.me — GPT-6 and Intelligent UI arrive in ChatGPT, and answers become app-like (2026-10-08, in Japanese)

https://gori.me/it/171043

A short post on the Japanese tech blog ゴリミー summarises the rollout: Plus, Pro, Business and Enterprise from October 7, and Free and Go from the next day on GPT-6 Luna.
Citing reports for the Sol and Luna split, it adds that Enterprise users get it when their organisation's admin enables it.
It calls the change one of the answer's shape, with calculators whose numbers can be changed on the spot, moving ChatGPT closer to a tool that makes a small "app" per question.
It contrasts this with Apple's new Siri on Gemini in iOS 27, which aims to act across apps and personal data rather than reshape the answer screen.
It notes that visuals can be reduced in the settings.

[C] tech-noisy — Calculators and diagrams in ChatGPT's answers as GPT-6's Intelligent UI reaches the free tier, by Koji Tanemura (2026-10-08, in Japanese)

https://tech-noisy.com/2026/10/08/chatgpt-gpt-6-intelligent-ui-free-users/

The site states that the article was written with AI assistance and fact-checked and edited by its editors.
It stresses that the speed figures are about the time to start answering, not about how much the total answer time shrank.
It says the models used by ChatGPT Work and Codex are unchanged from September's.
Its editorial view is that the biggest change is not the model but that answers become operable down to the Free tier.
- It warns that a polished calculator makes wrong numbers look right, and says it would turn cautious if numeric errors in such tools became conspicuous.

[C] TestingCatalog — OpenAI rolls out GPT-6 with Intelligent UI in ChatGPT, by "Erin | AI Agent" (2026-10-07)

https://www.testingcatalog.com/openai-rolls-out-gpt-6-with-intelligent-ui-in-chatgpt/

The byline is an AI agent, and the text restates OpenAI's announcement and system card.
It embeds Sam Altman's post: "Have been waiting for this one for a long time, and I would hate to have to go back to the old version of Chat!"
It embeds the ChatGPT account's post: "ChatGPT just got a lot more visual—introducing Intelligent UI."

Notes

OpenAI's own pages disagree on Free and Go: the announcement, the release notes and the sps forum post give them GPT-6 Luna with Intelligent UI from 10-08, and the VeitB repost gives them GPT-6 Luna, while the help article names only GPT-5.6 Luna for them.
- The help article says "Free and Go users receive GPT-5.6 Luna", calls GPT-5.6 Luna "the default model for Free and Go users", and gives Free and Go no thinking level in its table.
- Because it ties Intelligent UI to GPT-6 at Instant through Extra High, its reading leaves Free and Go without Intelligent UI.
- The system card, for its part, launches GPT-6 "to everyone in ChatGPT, across free and paid plans globally" without naming the model per plan.
- The help article was updated about 03:00 JST on 10-08 and the release notes about 03:30 JST, both around the announcement, and no source says whether the help article covers only the first day of the paid rollout or is out of date.
- Business+IT, gori.me, tech-noisy, TechCrunch, SiliconANGLE and MacRumors all follow the announcement, so whether a Free account gets GPT-6 Luna and Intelligent UI from 10-08 stays open.
Developer access: no source read exposes Intelligent UI, its component library or its compiler to developers.
- The only developer-facing change on 10-07 is the chat-latest snapshot update in the API changelog, and its model page lists text as the only output.
- The help article mentions developers only to say that GPT-5.6 Terra and Luna can be used through the OpenAI API.
- The plugin UI changelog, where the Apps SDK changelog now redirects, has no entry after 2026-08-21: https://developers.openai.com/plugins/changelog.
- The "Using GPT-6" model guidance page mentions neither Intelligent UI nor chat-latest: https://developers.openai.com/api/docs/guides/latest-model.
- Work and Codex keep the September models, according to the post, the release notes and the system card.
No source names the model behind chat-latest: the changelog says "the latest model available in ChatGPT for Plus, Pro, Business and Enterprise users", the model page says "latest Instant model", and Simon Willison reads it as "a custom GPT-6 variant".
- The model page still shows a 400,000-token context window and an "Aug 31, 2025 knowledge cutoff", against 1,050,000 and Apr 20, 2026 on the GPT-6 Sol page, so its specification block may predate the snapshot.
- Whether chat-latest returns interface components or partial answers interleaved with thinking is unverified.
The API pages for gpt-6-sol and gpt-6-luna list only the aliases, and no source says whether the October versions reached the API; the system card speaks only of ChatGPT, Codex and Work.
Chat runs GPT-6 Sol (October) rather than GPT-6.1 Sol, which Work, Codex and the API have offered since 09-29; no OpenAI source explains the choice, which HN commenters questioned.
The system card says the October models "will replace GPT-5.6 Sol and GPT-5.6 Luna in ChatGPT", while the help article, as Search Engine Journal reported, keeps GPT-5.6 Sol: "GPT-5.6 Sol remains a separate option in the model menu", and "The GPT-6 rollout does not retire older selectable models".
SiliconANGLE says the component library is one "the GPT-6 models were pretrained on", while OpenAI's text only speaks of "expanded training methods" without naming the stage.
The 44% figure measures the time until the answer begins, not completion time.
- The help article says GPT-6 Sol powers Instant when GPT-6 is selected and that Free and Go use GPT-5.6 Luna, while the forum repost titles the chart behind the 44% claim "Instant search production traffic" with "Free model" at the end, so which model and tier were measured is unclear.
- The post's text gives no numbers for the comparison of Extra High with Medium or for the evaluation of difficult problems, and does not say whether Sol or Luna was measured.
The help article maps ChatGPT's thinking levels to models, GPT-6 Sol for Instant through Extra High and GPT-6 Astra for Pro, but no source maps them to the API's reasoning.effort values (none, low, medium, high, xhigh, max).
The help article returned 403 to the page cache and to WebFetch and was read through a browser in this run.
- It confirms what Search Engine Journal and MY TECH BLOG relayed from it: GPT-6 replacing Latest, GPT-5.6 Sol staying selectable, the Layout and visuals setting that does not switch to text-only answers, the unsupported older desktop apps, the mobile update with no minimum version, no special prompt, and the table of thinking levels by plan.
- The sentence about the Pro option that MY TECH BLOG quotes matches the release notes read in this run.
The system card evaluates neither the generated interfaces nor the interleaved answers, and its safety evaluations use the lowest reasoning settings.
- No OpenAI source addresses the accuracy of generated tools, which MY TECH BLOG's broadcast-address error and SiliconANGLE's hallucination question raise.
Mean visible response length on HealthBench Professional rose from 2,894 to 4,360 characters for Sol and from 2,920 to 5,289 for Luna; the card does not say whether interface output counts as visible response.
OpenAI states no token cost for Intelligent UI, and the help article only says it "has no separate usage quota" and that existing allowances apply; SiliconANGLE presumes higher token use, and the HN claim that Enterprise pays per token on chatgpt.com was not checked.
The link to image-based ads drawn by SiliconANGLE and HN commenters is speculation; OpenAI's 10-05 post "Building advertising for the way people use AI" was not read in this run.
An HN reply placed the self-harm, gore and sexual-content regressions in the under-18 section, but the system card reports them under Production Benchmarks, and the teen classifier block belongs to the separate under-18 results.
Timing for Japan: MacRumors posted at 3:26 pm PDT on 10-07, Business+IT at 03:29 on 10-08 and the HN story was about seven hours old at 10:23 JST, so the announcement and the paid rollout most likely came in the early hours of 10-08 JST; no source gives the announcement's exact time.
- No source gives a time for the Free and Go start, which OpenAI dates "tomorrow" in US time.
Search Engine Journal's page shows only a relative time, so its date comes from its "tomorrow" for Free and Go and the image path 2026/10.
Japanese coverage when checked: Business+IT and three blogs; ITmedia's AI+ and NEWS feeds had no article on the release, searches found none from GIGAZINE, Impress Watch or Publickey, and the primary URL had 1 Hatena Bookmark user.
Simon Willison's archive for 10-07 has no post on the release, so his HN comment is his only reaction found: https://simonwillison.net/2026/Oct/7/.
Not read: Neowin (403 to both tools), Digital Trends (empty page to both tools), and a Verge article that appeared only as a headline in search results.

Ideas for practice and output

Send the same chat prompts to chat-latest and gpt-6-sol through the Responses API and compare time to first token, answer length and formatting, to see what the 10-07 snapshot changes for a chat product and whether any interface markup comes back, at $5/$30 against $2/$10 per 1M tokens.
Prototype the pattern on one internal screen: a small component catalogue described in JSON schema, a streaming renderer that draws partial component trees as tokens arrive, and an eval that grades clarity, usefulness and completeness and checks when plain text should win, against a Markdown-only baseline with token counts.
Try progressive answers in an agent: stream a first partial answer while tools and reasoning continue, then measure the time to first useful content against the consistency and accuracy of the final answer.
Rerun MY TECH BLOG's probes in ChatGPT (an illustration request, the same request with tabs, a subnet calculator checked with Python's ipaddress) on a paid and a Free account, to learn when Intelligent UI triggers and how often generated tools get values wrong, and to settle whether a Free account gets GPT-6 Luna or GPT-5.6 Luna.
Before telling a team, Enterprise admins can check the workspace setting for GPT-6 and the Layout and visuals option, then write a one-page map of which GPT-6 model runs where after 10-07: October Sol and Luna in Chat, September models and GPT-6.1 Sol in Work and Codex, and gpt-6-sol, gpt-6-luna and chat-latest in the API.

3. 🪨 Strata, an open-source inference engine first released on 09-24, runs Qwen3.8-Flash-Next (125B parameters, 6B active) on consumer GPUs with 12 GB of VRAM by splitting the model across VRAM, RAM and SSD, and serves OpenAI- and Anthropic-compatible APIs that coding agents can use

Selected / impact 1 / potential 1 / attention 2 / anchor 09-24, before the window / kind: release / areas: models, coding agents.
Feed items in this topic:
- hatena-llm 10-06 【西川和久の不定期コラム】ちょい古ゲーミングPCで「Qwen3.8-Flash-Next」を動せる「Strata」を試してみた！ (PC Watch: trying Strata, which runs Qwen3.8-Flash-Next, on a slightly old gaming PC) — 77 Hatena Bookmark users when fetched
Anchor: Strata's first release, v0.1.0, came out on 09-24, two weeks before the window; the repository's Hacker News post drew 927 points and 422 comments on 10-04, and the PC Watch column first brought it to the feeds in this run.

Collected information

[A] Niko1221 — Strata repository and README (as fetched on 2026-10-08)

https://github.com/Niko1221/Strata / https://github.com/Niko1221/Strata/blob/main/README.ja.md

The repository describes itself as "Qwen3.8-Flash-Next on any consumer hardware: one-click install for Windows / Linux" and as a "Strata inference engine, OpenAI/Anthropic API on localhost, optional image input".
The README's tagline is "Run a 125-billion-parameter AI model on your own gaming PC", for an "NVIDIA or AMD graphics card (12 GB or more) · Windows or Linux · free and open source".
The GitHub API gives the creation time as 2026-09-24 16:40 UTC, the license as MIT and the main language as C++.
When fetched the repository had 17.1k stars (17,088 in the API), 1.5k forks (1,511), 98 watchers, 1,424 commits and 367 open issues and pull requests.
The author is the GitHub user Niko1221, whose profile gives the name "Niko", the location Ljubljana, Slovenia, the bio "AI & fun", no company and one public repository.
- The README credits the model to "the Qwen team" and claims no affiliation with it.
"Strata runs Qwen3.8-Flash-Next on a normal PC."
"This is a large, smart AI model that usually needs a server."
"It chats, writes code, reads pictures and works with your apps and coding agents."
"Nothing leaves your PC."
On an RTX 5070 (12 GB), a Ryzen 5 7600 and 64 GB of RAM, answer speed and 32K-token prompt reading are Q2_0 94 / 2,650 tokens/s, IQ2_XS 79 / 2,090, IQ3_XXS 62 / 1,750, IQ3_S 53 / 1,620 and Coder 55 / 2,180.
On an AMD RX 9070 XT (16 GB), a Ryzen 9 3900X and 47 GB of RAM they are Q2_0 60 / 1,160 tokens/s, IQ2_XS 52 / 1,110 and Coder 44 / 1,420.
The NVIDIA Q2_0 row was measured with engine 0.1.36 and the other rows with 0.1.26 (4K answers, 32K prompts).
"A card with more VRAM is faster: an RTX 3090 (24 GB) should write about 100-140 tokens per second."
Supported cards are NVIDIA GeForce RTX 20, 30, 40 or 50 series, or AMD Radeon RX 7900 XT / XTX, RX 7800 XT / 7700 XT, RX 9060 XT, RX 9070 / 9070 XT, Radeon AI PRO R9700 or RX 6800 / 6900 series, and "It needs 12 GB of VRAM or more."
For RAM the README says "32 GB or more", "Your RAM decides which model fits" and "64 GB runs every size".
For disk it asks for "About 80 GB free" and recommends an SSD because "the first start is much faster".
It runs on Windows 10 / 11 or Linux with a current NVIDIA or AMD driver, and two or three cards can share the model.
Experimental paths, "written and tested by community members on their own machines", cover older cards (Tesla P40 / V100, GTX 10, Radeon VII / MI50, RX 6700 XT, RX 5500 XT), Intel Arc and AMD Ryzen AI Max (Strix Halo) built from source on Linux, and processors without AVX2.
The first install option is to paste a line into an AI coding assistant (Claude Code, Cursor, Codex, GitHub Copilot): "Set up Strata on this PC for me: https://github.com/Niko1221/Strata - follow docs/AI_SETUP.md in that repository."
- The assistant "checks your graphics card, RAM and disk and picks the model that fits", and AI tools can also install, start and stop Strata through its MCP server.
The manual path is the zip or git clone, then START-HERE.bat on Windows or ./setup.sh on Linux, which asks for the model and size, the context and whether to read pictures.
Setup downloads the model ("about 70 GB"), resumes an interrupted download and opens the app at http://127.0.0.1:8080.
While the model starts, "your PC can be slow or stop responding for 1-3 minutes (longest the first time)", because "Strata loads 35-55 GB into your RAM and locks part of it for the graphics card".
The model choice follows RAM: 32 GB takes the Coder ("with a 24 GB card, Q2_0 and IQ2_XS run too"), 48 GB IQ2_XS or Q2_0, 64 GB IQ2_XS (recommended) or IQ3_XXS / IQ3_S, and 96 GB or more IQ3_S or Unsloth's UD-IQ4_XS (~4-bit).
The Coder is "a coding version with half of the experts removed" that "reaches 91% of the full model's SWE-bench Verified score (measured by its authors) and fits 32 GB of RAM".
- "It is weaker outside code, including Chinese and other CJK text (#438)."
Swift 1.5 is "a fine-tune that thinks for a much shorter time before it answers".
Unsloth's UD-IQ4_XS is a 94 GB download, and with less than ~80 GB of RAM Strata reads part of it from the SSD while it answers.
Unsloth's UD-Q4_K_XL (experimental) is "the closest to the full model", but Strata "writes only 7-8.5 tokens/s on a 64 GB PC" with it.
OrcaRouter's Uncensored IQ3_XXS is set up by hand and is not in the installer's menu.
Apps and coding agents add an "OpenAI-compatible" provider with the base URL http://127.0.0.1:8080/v1, and "Any API key and any model name work."
Apps that use Anthropic's API point at http://127.0.0.1:8080/v1/messages, and Claude Code at ANTHROPIC_BASE_URL=http://127.0.0.1:8080.
Codex CLI and other apps that use the OpenAI Responses API point at /v1/responses.
Thinking can be set to off, low, medium or high in the chat menu or through the app's "reasoning effort", off being the fastest and high the best for hard questions.
Pictures are a setup option, and AMD cards read pictures on Linux through the processor but cannot yet on Windows.
Access from a phone or another PC uses START-HERE.bat --setup --host 0.0.0.0 --api-key <secret>, with the instruction "Always set a key."
"By default Strata answers one request, and the others wait."
- Several at once need "parallel": 2, and "On a 12 GB card this makes each answer slower."
"Strata reads the first message of a chat in full, about 1 minute per 30,000 tokens."
- "Follow-up messages start in seconds."
The README explains the mechanism as a kitchen: "the things you use all the time stay on the counter, and the rest waits in the pantry".
"The model is a team of 24,576 small specialists ("experts")."
- "Each word needs only 10 of them."
The graphics card keeps "the few thousand experts that are used most often", RAM holds all of them, the processor "works on the rest at the same time", and the SSD "holds a big lookup table".
In "Guess, then check", a small helper guesses the next few words and the big model checks them all at once, giving "the same answer, 1.6-1.8x sooner".
"Long texts are read in big pieces (up to 8,192 tokens at a time), at over 1,000 tokens per second."
The model was compressed by ISTA-DASLab, UkisAI (Swift 1.5) and Unsloth, and Strata "uses parts of llama.cpp / ggml".
Strata is under the MIT License, and "A few parts and every model have their own licenses".
README.ja.md carries the same content in Japanese, including the Claude Code (ANTHROPIC_BASE_URL) and Codex CLI (/v1/responses) settings.

[A] Niko1221 — Strata release notes, v0.1.0 to v0.1.40.3 (2026-09-24 to 2026-10-07)

https://github.com/Niko1221/Strata/releases/tag/v0.1.0 / https://github.com/Niko1221/Strata/releases

v0.1.0 was published on 2026-09-24 at 17:05 UTC as "The ready-made Strata engine for Windows (RTX 30 / 40 / 50: sm_86, sm_89, sm_120 + PTX), CUDA 13.0".
- START-HERE.bat fetches it and NVIDIA's cuBLAS from pip, "so no compiler or CUDA Toolkit is needed - only an NVIDIA driver 580 or newer".
- The zip holds strata.exe (the engine), strata-vision.exe (the optional image encoder) and BUILD.json.
The project shipped 44 releases between v0.1.0 (2026-09-24) and v0.1.40.3 (2026-10-07).
v0.1.17 (2026-09-28) is headed "Claude Code works with Strata, sampling matches llama.cpp, and you can choose the GPU".
- The server accepts /v1/messages?beta=true, and a system message in the middle of a conversation, which Claude Code uses for its hook context, no longer breaks the chat template (#55, #56).
v0.1.38 (2026-10-03) protects a server without an API key against DNS rebinding and cross-site requests.
- Without api_key it answers only requests addressed to a name it knows, and "a browser page from another site can no longer send it requests (403)".
- Behind a reverse proxy, a tunnel or Docker under another name, the name goes into "allowed_hosts", or an API key is set.
- The same release made Q2_0 prompts 10% faster at 4K on an RTX 5070 and let a 6 GB card start (#496).
v0.1.39 (2026-10-04) added the OpenAI Responses API for Codex, several requests at once as an opt-in ("parallel": N, #465) and older hardware as experimental opt-ins.
- Decode rose about 6% against 0.1.38 (Q2_0 story 68.4 to 72.7 tok/s, code 75.8 to 80.0), with output "byte-identical to 0.1.38's".
v0.1.40 (2026-10-06) added experimental Strix Halo (gfx1151) support, measured on a Ryzen AI Max+ 395 with 128 GB and UD-IQ4_XS at 1,293 / 53.8 (8K), 1,370 / 46.6 (64K) and 1,320 / 51.4 (128K) prompt / output tok/s.
Its security part refuses network image paths, caps URLs at 32 MiB and stops a page from another origin naming a local file as a picture (#553), with the same check added to /v1/responses.
- The maintainers did not merge #434 ("a Manager page that any website can drive, plus a proxy that adds the API key") or #696 ("the API key becomes a shell on a LAN server").
v0.1.40 also reports a resident RAM mode on a layer split at "about 70 tok/s against 32-64 on 32 GB machines" (#848) and Q4_0 / Q4_1 expert formats (#599).
v0.1.40.3 (2026-10-07) fixes Intel Arc installs, keeps 2,560 MiB free on Windows AMD cards of 16 GB or more (RX 7900 XT with IQ3_S: 24 tok/s before, 55 tok/s with room, #1376) and uses the bundled HIP runtime again (#461).
- For the HIP fix the notes say "We have no Windows AMD card to confirm this on; reports help."

[A] Niko1221 — Strata docs: HOW_IT_WORKS.md and MODELS.md (as fetched on 2026-10-08)

https://github.com/Niko1221/Strata/blob/main/docs/HOW_IT_WORKS.md / https://github.com/Niko1221/Strata/blob/main/docs/MODELS.md

The GPU holds "attention and DeltaNet mixers, the gated-residual weights, routers, shared experts, output head, the MTP draft layer, the KV cache (from 64K: only its most-read part, the rest streams from RAM), and an expert cache that fills the rest of VRAM with the most-used experts".
"More VRAM matters more than a faster GPU: every extra GB holds ~700 more experts, and every expert on the GPU is one the CPU does not have to compute."
RAM holds "all 24,576 experts, pinned", and the CPU computes the ones not on the GPU "in place", at the same time as the GPU (AVX-512 / AVX2 kernels, ggml's for the i-quants).
On a PC with little RAM and a big card, a low-RAM mode keeps in RAM only what the GPU does not hold.
The SSD holds "the 28.8 GB n-gram table, read a few rows per token through the OS cache".
The same engine is compiled for NVIDIA (CUDA) and AMD (HIP).
The model's own MTP layer drafts up to 3 tokens and one pass over all 48 layers checks them, at 2.4-3.2 tokens per pass on average.
When the reply repeats the context, prompt lookup drafts up to 5 tokens, making "code edits 6-11% faster, other text unchanged".
"Strata runs one model, Qwen3.8-Flash-Next, in several sizes (the same model, compressed more or less) and several versions (the original, a coding version, a fine-tune)."
At a 128K context on the RTX 5070, answers run at 76 (Q2_0), 63 (IQ2_XS), 49 (IQ3_XXS), 46 (IQ3_S) and 43 (Coder, IQ1_M) tokens/s.
A 4K prompt reads at 910-1,580 tokens/s, and "A 32K prompt takes about 15 seconds with Q2_0."
RAM plus VRAM needed: Q2_0 37.6 GB ("fastest", "good"), IQ2_XS 39.2 GB ("better (recommended)"), IQ3_XXS 47.0 GB ("great") and IQ3_S 54.8 GB ("best: matches the full model on the published tests (original model only)").
The download is 66-76 GB for the three smaller sizes, and the first start also fetches the MTP draft layer (~6 GB, +1 GB with images).
A size fits when "RAM is at least the experts + about 10 GB", the experts being 34 GB for Q2_0, 35.5 for IQ2_XS, 43 for IQ3_XXS, 50 for IQ3_S and 23 for the Coder.
The second shard, "a 29 GB lookup table", stays on the SSD.
START-HERE.bat --calibrate tunes engine settings in about 5-10 minutes and made the Coder 7% faster on the measured PC (NVIDIA cards for now).
The Coder keeps 256 of each layer's 512 experts, chosen on code (with agentic and image) data, at "91% of the full model's SWE-bench Verified score, 99% of LiveCodeBench, by its authors".
- Its shard 1 is 29.6 GB, so it fits 32 GB of RAM and "runs 262K context on 64 GB".
- Under issue #438, "Chinese answers came out wrong or looping where English was fine".
Swift 1.5 runs at the same speed per token as the original, comes without IQ3_S and carries its own license.
UD-IQ4_XS keeps "your RAM minus 24 GB" of its 59.5 GB of experts in RAM and needs 48 GB of RAM or more and engine 0.1.38 or newer.
UD-Q4_K_XL is a 111 GB download whose 77 GB of experts do not fit in RAM, and it needs 48 GB of RAM, an NVMe SSD and one NVIDIA GPU (no images yet).
Unsloth's UD-Q6_K_XL (169.2 GB, not in setup's menu) and OrcaRouter's Uncensored IQ3_XXS are manual setups.

[A] Niko1221 — Strata docs: DETAILS.md (as fetched on 2026-10-08)

https://github.com/Niko1221/Strata/blob/main/docs/DETAILS.md

The measuring PC is an RTX 5070 12 GB, a Ryzen 5 7600 (6 cores) and 64 GB of DDR5-5200 on Windows, with "One code-agent prompt per length, 256 generated tokens, MTP speculative decoding on".
Engine 0.1.26 prompt processing at 1K / 4K / 32K / 64K / 128K / 262K tokens, in tokens/s:
- Q2_0: 536 / 1,299 / 2,171 / 2,126 / 2,107 / 1,304.
- IQ2_XS: 534 / 1,256 / 2,092 / 1,754 / 1,752 / 1,181.
- IQ3_XXS: 482 / 1,007 / 1,745 / 1,609 / 1,602 / not measured.
- IQ3_S: 427 / 913 / 1,624 / 1,640 / 1,443 / not measured.
- Coder: 656 / 1,583 / 2,177 / 2,236 / 2,208 / 1,034.
Output at the same lengths, in tokens/s:
- Q2_0: 87.3 / 93.0 / 81.8 / 76.2 / 73.7 / 60.3.
- IQ2_XS: 79.6 / 78.6 / 76.3 / 63.7 / 62.7 / 52.8.
- IQ3_XXS: 61.9 / 61.6 / 58.5 / 57.2 / 49.0 / not measured.
- IQ3_S: 52.4 / 53.3 / 48.3 / 46.3 / 45.5 / not measured.
- Coder: 58.9 / 55.1 / 54.9 / 53.2 / 43.0 / 42.8.
- The 262K cells were not measured again with 0.1.26: they come from engine 0.1.22, and the Coder's 262K prompt figure from 0.1.14.
An AMD RX 7900 XTX (gfx1100) with IQ3_S and engine 0.1.38 read prompts at 760-1,641 and answered at 59.2-65.1 tokens/s across 1K to 128K.
Engine 0.1.36 moved Q2_0's prompt experts to fused int8 tensor-core kernels (+16-22%) and lifted Q2_0 output at 128K from 64.5 to 76.4 tokens/s on RTX 50 cards.
Estimates for other cards, "not measured" and "±20%", give an RTX 3090 24GB with Q2_0 about 128-140 output tokens/s up to 32K and about 85 at 262K, and an RTX 5060 Ti 16GB about 80-87 up to 32K.
The Coder is "ISTA-DASLab's expert-pruned release", with "91.3% of the full model's SWE-bench Verified and 98.7% of LiveCodeBench v6" reported by its authors, Apache-2.0 per its card, and "72% of the expert reads hit the GPU on a 12 GB card".
Swift 1.5's authors claim "63% fewer thinking tokens, 1.8x sooner answers, under 1% accuracy loss".
- Strata's own check of 8 reasoning questions gave 8/8 for both models, Swift using 1,234 output tokens in 28 s against 2,682 in 46 s for the original, "Not a benchmark, but consistent with the claim".
The API serves POST /v1/chat/completions and POST /v1/messages (stream and non-stream, tools), POST /v1/responses (stateless), GET /v1/models, /health, /props, /status, /slots and /metrics.
GET /metrics answers a Prometheus scrape "in the text format with vLLM's names", so "the dashboards and alerts written for a vLLM server read this one", and a Grafana dashboard ships in docs/monitoring/.
Thinking is set with OpenAI's "reasoning_effort": "none" | "low" | "medium" | "high" or Anthropic's "output_config": {"effort": ...}, "thinking": {"type": "disabled"} or a budget_tokens value (under 2K low, under 8K medium, more high).
- "Without a setting the model uses its own default, high."
"reasoning_budget_tokens": N is an opt-in hard cap on thinking.
"tool_call_recovery": true reads tool calls the model writes in other forms, and "Measured on 1,462 agent turns (Qwen3.8 under Claude Code, from signalnine/q27's drift corpus): 98.3% read as intended with it, 92.9% without."
Claude Code (Strata 0.1.17 or newer) needs ANTHROPIC_BASE_URL=http://127.0.0.1:8080, ANTHROPIC_MODEL set to "a Claude model name it knows (it refuses names it doesn't; Strata ignores the name)" and any ANTHROPIC_AUTH_TOKEN.
"Claude Code stamps its system prompt with a billing header that changes on every request (cch=...) and every session", and the server pins both stamps so that the system prompt and tool list are reused from the cache.
"anthropic_thinking": "on_request" (opt-in, 0.1.32) renders Anthropic requests that do not ask for thinking without it, which is "what Claude Code's short helper calls (a session title in a few dozen tokens) need".
/v1/responses (0.1.39, #451) "speaks OpenAI's newer Responses API, which Codex CLI uses (it no longer speaks Chat Completions)".
- "It is stateless", and previous_response_id, conversation, background and the retrieve, delete and cancel endpoints are refused.
- Hosted tools (web_search, file_search, ...) are left out, and tool_choice cannot force a tool.
The Codex CLI setup in ~/.codex/config.toml sets model_provider = "strata", base_url = "http://127.0.0.1:8080/v1", wire_api = "responses", model_context_window = 32768 and stream_idle_timeout_ms = 600000.
"Measured with Codex CLI 0.160.0 and Q2_0 on an RTX 5070: its first prompt (instructions and tool descriptions) was 9,443 tokens, read in 10 s; in a tool loop, each later turn reused about 96% of the prompt from the cache and read only the new part in 1-2 s."
On Windows, Codex's sandbox rejected every shell command until Codex was started with -c 'windows.sandbox="unelevated"', "a Codex setting, not Strata's".
With the opt-in "codex_compaction_cache": true, a Codex compaction after an 85,000-token conversation reused 84,895 of its 84,997 tokens, against 41 of 80,683 without it, by the author's measurement.
OpenCode (#543) connects through @ai-sdk/openai-compatible with the base URL http://127.0.0.1:8080/v1, and Zed's llama.cpp provider reads /props to offer tools.
The context is chosen in setup (8K-262K), and "Requests longer than that are refused, never silently cut".
A conversation cache keeps up to 6 checkpoints in RAM (~118 MB each), and a system prompt of 2,048 tokens or more is checkpointed so that agent clients with long system prompts and tool lists reuse it.
The experimental speed projection (ESP) is "A 480 KB control vector" applied after layers 4-44, which its own package describes as "a refusal-direction projection".
- With it "the model declines far fewer requests (it reports 1 of 50 vs 50 of 50 on its test set), and removing refusals removes a safety behaviour - you are responsible for what the model writes with it on".
- It is off by default, and on Q2_0 it changed the top-1 token at 10% of positions and raised perplexity by 15% on code.
The ESP vector is under the Qwen Community License 1.0, and the model files "are not part of it; their licenses apply to them".
The credits name ideas from Splash, ninfer and HyperQwen, and llama.cpp / ggml (MIT) for the i-quant formats, GPU dot products, the CPU backend and the mtmd image library.

[A] Niko1221 — Strata docs: OLDER_GPUS.md, AI_SETUP.md and MCP_SERVER.md (as fetched on 2026-10-08)

https://github.com/Niko1221/Strata/blob/main/docs/OLDER_GPUS.md / https://github.com/Niko1221/Strata/blob/main/docs/AI_SETUP.md / https://github.com/Niko1221/Strata/blob/main/docs/MCP_SERVER.md

Supported cards are NVIDIA RTX 20 / 30 / 40 / 50 and the AMD cards in AMD_HIP.md, and older cards run through "opt-in, experimental paths that community members wrote and measured on their own machines".
"The maintainers have none of these cards: each path is compile-checked and unit-tested here, and the ready-made engines and their output stay exactly as they were."
"CUDA 13 dropped Pascal and Volta", so setup keeps a second engine built with CUDA 12.9 for them, which also serves NVIDIA drivers older than 580 (528 or newer on Windows, 525 on Linux).
Reported numbers include a Tesla P40 with IQ3_S at prompt 217-374 and decode 30-33 tok/s (#395), a V100-PCIE-32GB with UD-IQ4_XS at prompt 1,123-1,251 tok/s (#600), and two MI50 cards with the Coder at decode 50.1 / 47.8 / 45.7 tok/s at 4K / 32K / 128K (#677).
An 8 GB RX 5700 XT ran the Coder at 18.0-23.3 tok/s decode with 607 of 12,288 experts in VRAM.
AI_SETUP.md is "written for an AI coding assistant (Claude Code, Cursor, Codex, GitHub Copilot, ...) that a user asked to set up Strata on their PC".
Its first ground rule is "Never expose the server without an API key."
It tells the assistant to confirm the ~70 GB download (94 GB for UD-IQ4_XS, 111 GB for UD-Q4_K_XL) and to run setup, which can take "an hour or more on a slow connection", in the background.
tools/strata_mcp.py is an MCP server "for the AI assistant you already use (Claude Code, Claude Desktop, Cursor, VS Code, Codex ...)", with tools to install, start, stop and check Strata.
- "It is one Python file that uses only the standard library", and it needs Python 3.10 or newer.

[A] Strata — Running a 125-Billion-Parameter Model on a Normal PC, paper (September 2026)

https://github.com/Niko1221/Strata/blob/main/docs/paper/Strata-Paper.pdf

The subtitle calls Strata "a CUDA and CPU inference engine that serves Qwen3.8-Flash-Next from one 12 GB graphics card, 64 GB of RAM and a six-core desktop processor".
The extracted text names no author and no affiliation.
The paper gives the model's smallest good-quality quantization as a 66 GB file, five and a half times the memory of a 12 GB card.
"Strata is an inference engine written for this one model."
On an RTX 5070 (12 GB), a Ryzen 5 7600 and 64 GB of DDR5 it reports 95 tokens/s at a 4K context with Q2_0, 45-95 tokens/s across all three quantizations from 1K to 262K, and prompt reading at 285-571 tokens/s.
Running the rest from RAM on the CPU with a general-purpose engine such as llama.cpp "works but leaves most of the machine idle most of the time".
Of the 48 layers, 36 use Gated DeltaNet and 12 use Qwen Sparse Attention, which has two key/value heads and attends to at most about 2,048 selected positions.
Each layer ends in 512 experts of which the router picks 10, so a token touches 2% of the expert weights, and the 51-billion-parameter n-gram table is addressed by the last three token ids.
The byte census of the Q2_0 file gives the routed experts 34.0 GB stored and 0.66 GB read per token, the mixers, attention, shared experts and routers 1.8 GB, the gated residual 1.3 GB, the output head 0.44 GB, the n-gram table 28.8 GB with at most 23 KB read per token, and the MTP layer 0.8 GB.
The GPU-resident part is about 3.5 GB, and the test machine has PCIe 4.0 x16 (~26 GB/s) and 64 GB of DDR5 (~41-52 GB/s).
For each layer the GPU writes the ten chosen expert ids into pinned host memory (a "doorbell"), and the CPU sends the cached experts to the GPU, copies a share of the misses over PCIe (55% for the i-quant files, 20% for Q2_0) and computes the rest.
Strata fetches the MTP head's tensors (5 GB) from the BF16 checkpoint and keeps them in VRAM with a reduced output head over 40,525 likely tokens.
"The result is exact: the text is identical, token for token, to plain greedy decoding, which we test with forced wrong drafts and rollbacks."
A profile-filled expert cache serves 50% of the routed experts from 4,500 VRAM slots, and swapping in the conversation's own hot experts raises that to about 72%.
Q2_0's time to first token is 2.7 s at 1K, 6.7 s at 4K, 55.3 s at 32K, 114.4 s at 64K, 236.7 s at 128K and 523.8 s at 262K, while the experts in VRAM fall from 4,517 to 1,588.
At 4K a Q2_0 verify window takes 34.3 ms, of which 14.6 ms wait for the GPU, 13.4 ms for the CPU experts, 2.0 ms drafting and 4.3 ms other, at 3.23 tokens per round.
Speculation with the MTP layer is "worth 1.6–1.8×", taking plain decoding at 4K from 47-57 tokens/s to 82-92.
Against llama.cpp the mean KL divergence of the next-token distribution is 0.022, below the 0.058 by which llama.cpp's own CPU and GPU builds differ.
On a DDR4 system the CPU half of a Q2_0 round takes about twice as long, and "a bigger GPU cache is the best compensation".
The paper lists keeping the conversation's state between requests as future work, because "Today every request processes its whole prompt again".
Related work named: Fiddler, KTransformers, MoE-Infinity, Pre-gated MoE and PowerInfer, with the idea of one engine for one model taken from Splash, ninfer and HyperQwen.
It cites the Qwen Team's report "On the Design of Qwen3.8-Next Architecture" (arXiv:2608.30320, August 2026) and the Qwen blog post.

[C] hagope — Community benchmark: RTX 5090, Core Ultra 9 285K, in the Strata repository (2026-09-30)

https://github.com/Niko1221/Strata/blob/main/bench/results/2026-09-30-community-rtx-5090/README.md

The run used Strata 0.1.29 with the original IQ2_XS on one RTX 5090 (32,607 MiB, 575 W), a Core Ultra 9 285K and 64 GB of RAM on Linux, with a 131,072-token context.
Median decode was 179.4 tok/s at 4,096 prompt tokens, 175.7 at 32,768 and 165.0 at 128,000, on synthetic code-explanation requests with greedy decoding and a 256-token cap.
Median prompt throughput was 4,269.8 / 5,543.2 / 5,778.7 tok/s and time to first token 0.974 / 5.950 / 22.262 s at those lengths.
Decode expert-cache hit rates were 97.8-99.7%.
"They do not establish general answer quality or performance on other workloads."

[A] Qwen — Qwen3.8-Flash-Next model card, metadata and license on Hugging Face (as fetched on 2026-10-08)

https://huggingface.co/Qwen/Qwen3.8-Flash-Next / https://huggingface.co/Qwen/Qwen3.8-Flash-Next/blob/main/LICENSE / https://huggingface.co/api/models/Qwen/Qwen3.8-Flash-Next

"This experimental preview of the architecture that will underpin Qwen4 is built around a fundamental rethinking of how the core components of modern large language models (LLMs) interact at scale."
Qwen3.8-Flash, "the official version based on Qwen3.8-Flash-Next", adds production features on Qwen Cloud such as a 1M context by default and official built-in tools.
The highlights are hybrid attention of Gated DeltaNet and Qwen Sparse Attention (QSA) working at micro-block level, Gated Residual, N-gram Embedding and a training recipe that applies Muon and AdamW to specific weight categories.
"Embeddings provide a unique axis for parameter scaling that requires less computation and is more amenable to offloading than Mixture-of-Experts (MoE)."
The model is a "Causal Language Model with Vision Encoder" with 125B parameters and 6B activated, "plus 51B n-gram embedding and 4B MTP", a hidden dimension of 2560 and 48 layers laid out as "12 × (3 × (Gated DeltaNet → MoE) → 1 × (Qwen Sparse Attention → MoE))".
QSA has 24 query heads and 2 KV heads, an MQA indexer and a budget of "512 blocks or 2048 tokens".
The MoE has 512 experts with "10 Routed + 1 Shared" active and an expert intermediate dimension of 640, the gated residual has 4 branches, and MTP is 1 layer.
"Context Length: 262,144 natively and extensible up to 1,000,000 tokens."
Language benchmarks, in the order Qwen3.8-Flash-Next / Qwen3.8-27B / Qwen3.7-Plus / DeepSeek-V4-Flash-0731 / Claude-Opus-4.6 (Max):
- DeepSWE 1.1: 58.7 / 42.2 / 16.5 / 54.4 / not reported.
- SWE-bench Pro: 62.5 / 61.7 / 55.8 / 56.0 / 53.4.
- SWE-bench Multilingual: 81.0 / 73.8 / 75.8 / not reported / 77.5.
- NL2Repo-Bench: 48.1 / 42.3 / 41.1 / 54.2 / 47.6.
- CoWorkBench: 73.9 / 70.7 / 65.1 / 45.1 / 68.2.
- JobBench: 55.7 / 33.4 / 27.6 / 41.3 / 36.6.
- Toolathlon Verified (Pass@1): 73.5 / 67.1 / 50.6 / 70.3 / not reported.
- IFBench: 81.3 / 79.5 / 79.1 / 79.2 / 62.5.
- GPQA Diamond: 91.7 / 89.2 / 90.3 / 90.8 / 91.3.
- HLE: 35.9 / 30.8 / 34.7 / 33.8 / 40.0.
- LiveCodeBench v6: 91.9 / 90.3 / 89.6 / 90.6 / 88.8.
DeepSWE 1.1 was run "with the Claude Code and mini-SWE-agent harnesses" and reports the higher of the two, and SWE-bench Pro and NL2Repo-Bench used the Claude Code harness with a 256K context window.
"For production workloads or high-throughput scenarios, dedicated serving engines such as SGLang, KTransformers or vLLM are strongly recommended."
The model thinks by default, and the card's example sets reasoning_effort="xhigh" with the comment "xhigh by default; supported levels are xhigh, medium, and low".
Recommended sampling is temperature=1.0, top_p=0.95, top_k=20 for thinking mode and temperature=0.7, top_p=0.80, presence_penalty=1.5 for instruct mode.
Preserved thinking, on by default, keeps the thinking blocks of all earlier messages, which the card says suits agents and improves KV cache use.
The Hugging Face API lists the repository as created on 2026-08-24 and last modified on 2026-08-27, with 1,609,433 downloads, 6,011 likes, the tag qwen4_exp and the license qwen-community-1.0.
The Qwen Community License 1.0 grants the rights to "use, copy, modify, merge, publish, distribute, sublicense, sell, deploy, host, fine-tune, and create derivative works" free of charge, under two conditions.
- A licensee's commercial product or service with "more than 100,000,000 monthly active users or US$ 20,000,000 (or equivalent in other currencies) monthly revenue" must prominently display the model name.
- "If the licensee or any of its affiliates conducts a Model as a Service or AI Work Assistant business, the licensee shall obtain a separate license from Qwen before Using the Software or its derivative works for any commercial purpose."
- That requirement "shall not apply to the licensee's internal Use of the Software, provided that such Use does not make the Software, its outputs, or its underlying model capabilities available to any third party".
- An "AI Work Assistant" is "an independent AI-powered product primarily designed for AI-assisted coding or office productivity (e.g., Qoder and QwenWork)".

[A] Qwen — QwenLM/Qwen3.8-Flash-Next repository README (2026-08-26)

https://github.com/QwenLM/Qwen3.8-Flash-Next

"2026-08-26: We release Qwen3.8-Flash-Next."
The model is "a multimodal MoE model that also serves as an early preview of the architecture used in Qwen4", playing "the same role that Qwen3-Next played for Qwen3.5".
N-gram Embedding "looks up a table using the local context to scale model capacity with very little extra computation; the embedding table can be offloaded to host memory and overlapped with model computation through asynchronous prefetching".
"Compared with Qwen3.7-Plus, Qwen3.8-Flash-Next substantially reduces both training and inference cost — training takes only about 1/9 as much, yet it delivers superior capabilities in coding and office tasks."
It powers the "Standard" mode of QwenWork, and QwenCloud serves it through OpenAI- and Anthropic-compatible APIs.
The local options listed are transformers serve, llama.cpp ("llama.cpp supports the Qwen3.8-Flash-Next (text & vision)"), mlx-vlm on Apple Silicon and Unsloth.
The SGLang and vLLM examples serve it with a tensor-parallel size of 4, a 262,144-token context and the qwen3 reasoning and qwen3_coder tool-call parsers.
The tech report is cited as "On the Design of Qwen3.8-Next Architecture: Evaluation, Efficiency, and Training Stability" (Qwen Team, Alibaba Group, August 2026).

[B] PC Watch (Impress) — Trying Strata, which runs Qwen3.8-Flash-Next on a slightly old gaming PC, column by 西川和久 (2026-10-06, in Japanese)

https://pc.watch.impress.co.jp/docs/column/nishikawa/2145673.html

The column opens by saying the AI scene has been lively since October because word spread that Qwen3.8-Flash-Next (125B total, 6B active) runs on a 12 GB VRAM card.
To check, the author revived a spare PC with a Core i9-12900, 64 GB of DDR4, 1 TB and a GeForce RTX 3060 (12 GB).
His table of the model lists 125B total parameters (plus 51B n-gram embedding and 4B MTP), 6B active, 48 layers repeating "3×(Gated DeltaNet→MoE)+1×(QSA→MoE)" 12 times, 512 experts (10 routed + 1 shared) with an intermediate dimension of 640, a native 262,144-token context (up to 1,000,000), text, image and video input, MTP speculative decoding and the license qwen-community-1.0.
He places it slightly above gpt-oss-120b (5.1B active) in size.
Against the dense Qwen3.8-27B he lists SWE-bench Pro 62.5 vs 61.7, SWE-bench Multilingual 81.0 vs 73.8, DeepSWE 1.1 58.7 vs 42.2, LiveCodeBench v6 91.9 vs 90.3, GPQA Diamond 91.7 vs 89.2 and IFBench 81.3 vs 79.5, and calls the gap subtle, small on some items and sizable on others.
Even at Q2 the 125B model is just under 40 GB, so it does not fit even the 32 GB of a GeForce RTX 5090.
He describes Strata's split as VRAM for the always-used parts plus a cache of "hot" experts computed on the GPU, RAM for all experts computed in parallel by the CPU, and the SSD for the n-gram lookup table of about 29 GB, read row by row.
He explains that the n-gram table is a dictionary lookup keyed by the last few tokens and is not used in matrix multiplication, which is why it need not stay in VRAM or RAM.
He gives the requirements as RTX 20/30/40/50 or a supported AMD GPU with 12 GB of VRAM or more, noting that 8 GB also works but slowly.
Because the Coder is weak outside code and on CJK text, he judges 48 GB of RAM the practical floor for normal use.
He calls the test PC almost the minimum of the author's standard of 12 GB of VRAM plus 64 GB of RAM: RTX 3060, Core i9-12900 without AVX-512, 64 GB of DDR4-2667 (16 GB×4, about 43 GB/s), a 1 TB NVMe drive, Windows 11, IQ2_XS (39.2 GB) and engine 0.1.38.
RAM plus VRAM total about 76 GB, so IQ3_S (54.8 GB) would also fit, but he chose the IQ2_XS recommended for 64 GB.
He installed from the command line with Python 3.12 under miniconda and python setup.py --setup --family qwen --model IQ2_XS --context 262144 --vision yes --gpu 0 --yes, which downloads the model (about 72 GB), fetches the MTP draft layer and writes the start script.
He starts it with python serve\server.py --engine strata --config strata-iq2_xs.json --host 0.0.0.0 --port 8080 --fit-max-tokens, and it is ready in about 30 seconds.
The thinking level is set per request with reasoning_effort none / low / medium / high, the server default is high, and he switched the default to none for coding.
He first installed on a SATA drive, where loading the experts (about 33 GB) had not finished after 3 minutes, and moving to the NVMe drive cut the start to about 30 seconds, so the model must sit on NVMe.
He praises the bundled web UI (Chat, a live Monitor of the model and the GPU, CPU and RAM, and About with settings and addresses), unlike vLLM servers that only offer an API.
The endpoints are the OpenAI-compatible /v1 (/v1/chat/completions, /v1/models), the Anthropic-compatible /v1/messages and /health, with model ids such as qwen3.8-flash-next-iq2_xs and qwen3.8-flash-next-iq3_s.
With a benchmark designed by Sonnet 5.5 (the same he uses for other LLMs), IQ2_XS decoded at 34-44 tok/s, which he calls well within practical use.
The averages of three runs without thinking were 43.9 tok/s for code, 37.3 for logic puzzles, 33.7 for prose and 38.5 for Japanese.
Prefill ran at about 850-880 tok/s for about 5.9k tokens (about 7 seconds to the first character) and about 930 tok/s for about 23k tokens (about 25 seconds), with 3,031 experts on the GPU (about 4 GiB) and a cache hit rate of about 72%.
Single runs vary by about ±20% with the MTP acceptance rate, and low thinking changed tok/s only within noise.
He finds decoding practical but prefill slow, so coding agents that read many files and logs feel slow, while short exchanges are comfortable.
Missed experts are computed by the CPU from RAM, so the DDR4 bandwidth and the CPU without AVX-512 slow it down.
With IQ2_XS, quality on images, Japanese and tool calls held up broadly, but code generation was a notch below IQ3_S.
He compares the results with his DGX Spark (vLLM, FP8 base): prose and Japanese at about 37 tok/s are on a par (33.7 and 38.5), while code reaches about 60% (44 vs 72 tok/s).
He finds it significant that a model that should not run on a two-generation-old entry GPU runs at practical speed, and attractive that gamers can try local LLMs without buying a new GPU.
With IQ3_S on the same PC (context 128K, as Strata recommends) the averages were 31.8 tok/s for code, 27.3 for logic puzzles, 24.8 for prose and 29.0 for Japanese.
- Prefill was about 440-460 tok/s for about 5.9k tokens (about 13 seconds) and about 475 tok/s for about 23k tokens (about 49 seconds), with 1,104 experts on the GPU (about 2.1 GiB) and a hit rate of about 56%.
- Decode was about 0.72-0.75 times IQ2_XS and prefill about half, and memory use was about 54 GB including the OS.
On a second PC with a Core i9-13900HK, 128 GB of DDR5-5200 (about 83 GB/s), 2 TB and an RTX 4090 modified to 48 GB of VRAM (24 GB retail) and limited to 250 W (normally 450 W), he ran IQ3_S (about 90 GB download) on engine 0.1.38.
- Code ran at 128.5 tok/s, logic puzzles 113.3, prose 86.6 and Japanese 101.5, with peaks above 130 tok/s, the fastest he has seen for this model including DGX Spark.
His quality checks on IQ3_S passed logic puzzles, answered "9.11 vs 9.9" correctly 6/6 times and passed 46/48 code-execution tests (LRU cache, interval merge, recursive-descent parser, 8 runs each with thinking none and low; none 24/24, low 22/24, both failures on the parser at low).
- Japanese output was clean with no Chinese mixed in, three shapes and text in an image were read exactly, and a tool-call task to fix code with 4 bugs succeeded in 4 turns in about 10 seconds.
- He saw no large degradation from the IQ3_S quantization in this scope, but did not test long Japanese documents or large code generation.
He tried and dropped the experimental speed projection (ESP), which projects out the refusal direction (close to uncensored), because speed barely changed and code quality fell.
He used Strata's IQ3_S from DeepSeek Harness, for example to build a 3D invader game.
The web chat supports MCP, and he added web search through mcp-searxng (Node 22 or newer) pointing at his own SearXNG, with "mcp_servers" and "mcp": {"timeout_s": 60, "max_result_chars": 20000, "max_rounds": 8} in strata-<model>.json.
- The log then shows "MCP server 'searxng': 4 tools", and the chat setting "Use tools from MCP servers" is on by default.
Beyond web search he finds pointing an agent harness's endpoint at Strata more convenient than extending the chat with MCP.
He hopes Strata will support more models than Qwen3.8-Flash-Next if the mechanism allows.
He relays, doubtfully, a report that 12 GB GPUs have started selling in shops because of the news.

[B] PC Watch (Impress) — Strata arrives and runs Qwen3.8-Flash-Next very fast on a gaming PC, by 劉尭 (2026-10-02, in Japanese)

https://pc.watch.impress.co.jp/docs/news/2145142.html

The article says a 125B-total, 6B-active model runs at 60-95 tokens per second on a gaming PC with one graphics card, through the inference engine Strata that Niko1221 publishes on GitHub under the MIT license.
It describes the goal as running the model, which normally needs hundreds of GB of VRAM, on one NVIDIA card with 12-24 GB of VRAM and 64 GB of main memory.
It lists RTX 20/30/40/50 cards with 12 GB of VRAM or more, main memory depending on the quantization, about 80 GB of free disk, and Windows 10/11 or Linux.
On the published RTX 5070 benchmark, Q2_0 runs at 93 tok/s in a short chat and 74 tok/s at a 128K context, and IQ2_XS at 79 tok/s with prompt reading at 2,090 tok/s.
An RTX 3090 (24 GB) is expected to reach 100-140 tok/s, and two or three NVIDIA cards can share the model.
Setup on Windows is unzipping and double-clicking START-HERE.bat, with Python, the engine and the model (about 70 GB) downloaded automatically, while Linux uses setup.sh and a Dockerfile is provided.
With OpenAI-compatible http://127.0.0.1:8080/v1 and Anthropic-compatible /v1/messages endpoints, existing AI coding agents can use it as a local model.
It reads images, offers four thinking levels (off, low, medium, high) and supports AMD Radeon RX 7900/9070 series experimentally on Linux.
It lists the quantizations as Q2_0 (37.6 GB), IQ2_XS (39.2 GB), IQ3_XXS (47 GB) and IQ3_S (54.8 GB), says IQ3_S matches the full-precision model on the published benchmarks, and mentions UkisAI's Swift 1.5.
With an RTX 5080 plus an RTX 3090, prompt reading was 18-20% faster than with the 5080 alone.
The explanation covers the 24,576 experts with 10 used per token, the VRAM, RAM and SSD split, the cache that learns which experts are used, MTP-based speculative decoding at 1.6-1.8 times, and prompt reading in chunks of up to 8,192 tokens at over 1,000 tok/s.
The article had 63 Hatena Bookmark users when checked on 2026-10-08.

[B] npaka (note) — Overview of Strata, which runs a 125B model on 12 GB of VRAM (2026-10-02, in Japanese)

https://note.com/npaka/n/n4a1185074686

npaka summarizes Strata as an open-source engine that splits computation between GPU and CPU and uses VRAM, RAM and SSD to run large MoE models on ordinary PCs, currently centred on Qwen3.8-Flash-Next and its derivatives and quantizations.
He describes the GPU holding attention, routers, the KV cache and frequently used experts, RAM holding the other experts computed by the CPU, some experts copied over PCIe, and the SSD holding the large lookup table.
He relays the developer's RTX 5070 figures of about 93 / 79 / 62 / 53 tokens/s for Q2_0 / IQ2_XS / IQ3_XXS / IQ3_S in short chats and 74 / 63 / 49 / 46 at 128K.
He stresses that these are the developer's measurements and that real speed depends on the GPU, CPU, RAM, PCIe bandwidth and context length.
His requirement list is NVIDIA RTX 20-50, 12 GB of VRAM recommended (8 GB works but is slower), 64 GB of RAM recommended, an AVX2 x86-64 CPU, an NVMe SSD recommended, and Windows 10 / 11 or Linux, with 70-120 GB of storage possibly needed.
He notes that the Monitor shows GPU use, VRAM, CPU, RAM, PCIe traffic and generation speed.
He shows the OpenAI Python SDK pointed at http://127.0.0.1:8080/v1 with model="strata", and notes that the Anthropic Messages-compatible API lets coding agents use it as a local LLM.
He concludes that local LLMs used to mean picking a model that fits in VRAM, and that Strata relaxes this by using the whole PC to run 100B-plus models on ordinary GPUs.
In an aside he notes that the standard model uses about 34 GB of RAM even at Q2_0, so 32 GB is generally not enough, and suggests the Coder (shard 1 about 29.6 GB) for 32-48 GB and Q2_0 / IQ2_XS from 48 GB.
The post had 241 Hatena Bookmark users when checked on 2026-10-08.

[B] GIGAZINE — Strata, an app that runs quantized Qwen3.8-Flash-Next (125B) fast and locally on gaming PCs (2026-10-05, in Japanese)

https://gigazine.net/news/20261005-strata-local-ai/

GIGAZINE frames frontier open models as too large to run locally without data-center-class infrastructure, and Strata as making a quantized 125B Qwen3.8-Flash-Next run on relatively obtainable high-end gaming PCs.
It names two mechanisms: loading the whole MoE model into RAM with frequently used experts in VRAM, and speculative decoding with a light model predicting the next tokens.
It lists the requirements as an NVIDIA or AMD GPU with 12 GB of VRAM or more, 32 GB of RAM or more, 80 GB of storage or more (SSD recommended), and Windows 10/11 or Linux.
With 32 GB of RAM only the Coder runs, with 64 GB the IQ2_XS, IQ3_XXS and IQ3_S quantizations, and with more RAM higher-precision versions.
On an RTX 5070, a Ryzen 5 7600 and 64 GB of RAM, Q2_0 ran at 94 tokens/s and IQ3_S at 53, and on an RX 9070 XT, a Ryzen 9 3900X and 47 GB of RAM, Q2_0 ran at 60 tokens/s.
It reports that Strata became a big topic online with many reports on X, embedding @murasametech's video of IQ2_XS running fast on an RTX 5070 12 GB with a task to scrape and display a ranking of graphics card prices.
It also notes reports that quantization degrades the model badly, embedding @dimeiza's post in which IQ2_XS on an RTX 4090 with 64 GB of RAM, a Core i9-12900 and a SATA SSD ran at 140 TPS but fell into a loop repeating the same token when asked to output pi.
The article had 12 Hatena Bookmark users when checked on 2026-10-08.

[B] GIGAZINE — Qwen3.8-Flash-Next released as an open model with Qwen4's next-generation architecture (2026-08-27, in Japanese, background)

https://gigazine.net/news/20260827-qwen3-8-flash-next/

Qwen released Qwen3.8-Flash-Next on 2026-08-26, built on the next-generation architecture planned for the Qwen4 series.
It embeds Qwen's announcement on X: "The production version Qwen3.8-Flash will be available soon via QwenCloud API at just $ 0.16/1M input tokens and $ 0.47/1M output tokens."
It describes the hybrid of Gated DeltaNet and Qwen Sparse Attention and the N-gram Embedding, with 125B total, 6B active and 51B n-gram parameters, a standard 262,144-token context and up to 1M tokens with YaRN.
Its benchmark summary compares Qwen3.8-Flash-Next, Qwen3.8-27B, Qwen3.7-Plus, DeepSeek-V4-Flash-0731 and Claude-Opus-4.8 (Max), and says the model beats Claude-Opus-4.8 (Max) on many tests.
It writes that training took one ninth of the time Qwen3.8-27B needed.
At 1M tokens, prefill is 8.6 times faster than Qwen3.7-Plus.
The weights are on Hugging Face and ModelScope, and Unsloth published quantizations the same day, a 1-bit version running on machines with 75 GB of RAM or more and keeping 80% of the full model's accuracy.

[B] Hackaday — AI On Your Gaming PC, by Al Williams (2026-10-04)

https://hackaday.com/2026/10/04/ai-on-your-gaming-pc/

"If you want to experiment with LLMs, you typically have a choice of sending your requests to someone else's computer or fielding a very large GPU and CPU setup to run models locally."
Strata "lets you run a 125-billion-parameter LLM on hardware you might already have for gaming".
"The clever part is that Strata effectively treats VRAM as a cache for the much larger model."
The model also includes "a roughly 29 GB lookup table that stays on the SSD and is accessed as needed".
"According to the project, an RTX 5070 with 12 GB of VRAM can produce roughly 50 to 90 tokens per second, depending on quantization."
"We did have some trouble setting everything up due to some incompatibility with the NVIDIA C compiler, our gcc version, and some headers, but your problems will surely be different."
It "exposes OpenAI- and Anthropic-compatible APIs on localhost, so existing chat front ends, coding assistants, and other tools can use the local model without much special handling".
Asked about Hackaday, it got much right but confused who founded the site and who its authors are, and raising the thinking level and lowering the temperature only moved the confusion to other facts.
"It did better when asked to identify some problem code or outline how to port a particular C compiler to a new target."
"You'll still want at least 32 GB of system RAM, 12 GB of VRAM, and around 80 GB of storage, so 'modest' is relative."

[B] Latent Space (AINews) — [AINews] Reflection Beam - 501B-A23B American Open Model (2026-10-06)

https://www.latent.space/p/ainews-reflection-beam-501b-a23b

Under inference systems the issue lists llama.cpp "v0.6.0: Adds Clef text and vision support, Qwen3.8-Flash-Next, and a new llama_batch_ext API", citing Georgi Gerganov.

[C] Hacker News — Run Qwen 3.8 Flash Next (125B) on consumer hardware (RTX 4090) at 100T/s (2026-10-04)

https://news.ycombinator.com/item?id=49953495

The story was submitted by snehesht on 2026-10-04 at 12:51 UTC and had 927 points and 422 comments when fetched on 2026-10-08.
The submitter reports 124 tokens per second on an Nvidia 4090 with 128 GB of DDR5 and a Ryzen 7950x3d.
The most-answered comment (63 replies): "I'm a little skeptical of going below 4-bit quants due to the potential for significant degradation in quality."
- Its author runs 4-bit quants on an RTX Pro 6000 rented for about $1/hour, getting about 1.2 million tokens out and 40 million in per hour with caching.
On the AI-driven install line, one reply reads "And I thought piping to bash was bad", and the submitter answered that he had to read setup.py and setup.sh to see what it does.
One user asks "Why isn't this type of expert caching in the native llama.cpp yet?"
- Replies say mainstream engines are slow to integrate such work and that "the llama.cpp team (GGML) has strict requirements that a human must understand the code they are contributing", so fully AI-written kernels stay in separate projects.
One user benchmarked ninfer with Qwen3.8-27B (Q4/Q5) against Strata with IQ3_XXS on a power-capped 3090, 64 GB of DDR4 and PCIe x8: Strata passed 114/128 code tasks against 92/128, with 142 against 122 minutes of generation, and he gets 40-60 t/s after tuning.
One user's 50-image vision benchmark of object coordinates gave Strata a median error of 154.8 pixels (average 168.8) against 46.5 (average 81.4) for llama.cpp with the same GGUF and vision adapter.
- Another user reports that the same model on Strata "made more mistakes and hallucinated more when compare to llama.cpp".
One user writes that "LLM threads the world over are spammed with Strata links", and that "the speed is definitely there" but the accuracy has not impressed him.
Others dismiss the Q2 quantization ("if you quant it to hell (Q2) it'll go real fast") and ask that every headline about LLM speed name the quantization.
One user notes that the Coder drops half the experts and that low quantization costs quality, calling it "a net win" where "anything is better than nothing".
One user ran the Coder on a 16 GB RTX 4090 with 96 GB of RAM: in Strata's chat it failed to write a Rust binary tree that compiles, and under OpenCode it thought in a loop until the thinking budget ran out.
One user reports that on low effort Flash Next beats Qwen3.8-27B and is faster on an RTX 3090 with 128 GB of DDR4, while another asks why a model about six times the file size of the 27B gains hardly 10% on the model card's benchmarks.
One user asks whether this is another repository where Claude quantized the KV cache, adding "it's all AI generated", and others point to other engines that run the same model (ds4, ninfer, FreeToken, llama.cpp with Unsloth's quants).
Another user reports running ds4's Q4 quant on an RTX 6000 Pro at 255 tok/s decode for code and 4 concurrent streams at 400+ tok/s.

[C] Hackaday — reader comments on "AI On Your Gaming PC" (2026-10-04 to 2026-10-05)

https://hackaday.com/2026/10/04/ai-on-your-gaming-pc/#comments

One reader runs the Coder in Docker in low-RAM mode (32 GB cap) with a 256K context at an average of 35 tps on a 12 GB RTX 3060, and calls a well-specified C# migration "a decent job".
Another notes that the container instructions cover only Nvidia GPUs.
Asked how this differs from llama.cpp, Ollama or vLLM with any MoE model, a reader answers that it "cuts the hardware requirement for specific MoE models in 4", from about 100 GB of VRAM to 12 GB of VRAM plus 32 GB of RAM.
A reader warns not to drive the display from the GPU that runs the LLM, after freezing the system many times.

Notes

Every speed figure in the README, the docs and the paper is the developer's own; the independent measurements are the PC Watch column (IQ2_XS 34-44 tok/s on an RTX 3060 with DDR4, IQ3_S 86.6-128.5 tok/s on a 48 GB-modified RTX 4090), the community RTX 5090 report (165.0-179.4 tok/s) and single users on Hacker News and Hackaday.
- The RTX 3060 results fit the paper's statement that DDR4 roughly doubles the CPU half of a round.
Prompt reading is the weak point for coding agents: the paper's TTFT for Q2_0 is 55.3 s at 32K, the README says the first message reads at about 1 minute per 30,000 tokens, and PC Watch measured about 25 s for 23k tokens on the RTX 3060.
- The conversation cache and the system-prompt checkpoint in DETAILS.md are what make later agent turns read only the new part (Codex: about 96% reused, 1-2 s per turn on an RTX 5070).
The paper's prompt speeds (285-571 tokens/s) predate the current README (1,160-2,650 tokens/s); DETAILS.md says engine 0.1.13 about doubled prompt speed, and later releases added more.
The minimum RAM differs by source: 32 GB in the README, GIGAZINE and Hackaday (enough only for the Coder, or for Q2_0 and IQ2_XS with a 24 GB card in low-RAM mode), 48 GB as the practical floor in the PC Watch column, and 64 GB recommended by npaka and in the PC Watch news piece.
Quality is the open question: low-bit quantizations (Q2_0, IQ2_XS), a Coder that is weaker on Chinese and other CJK text (#438, which matters for Japanese use), a looping IQ2_XS answer relayed by GIGAZINE, PC Watch finding IQ2_XS code a notch below IQ3_S, and one Hacker News user's vision test in which Strata was about three times worse than llama.cpp on the same weights.
- Only PC Watch's small IQ3_S checks (46/48 code tests, clean Japanese, correct images and tool calls) point the other way, and nobody has published a larger eval of Strata against llama.cpp on the same file.
No source shows a link between the Strata author and the Qwen team: the GitHub profile lists Ljubljana and no company, the paper names no author, and every source treats Strata as an independent project built on Qwen's open weights.
The claim on Hacker News that the code is AI-generated is unverified; the docs themselves say several hardware paths are only compile-checked and that the Windows AMD fix in 0.1.40.3 was untested on such a card.
The model's license matters for team use: Strata is MIT, but the weights and the ESP vector are under the Qwen Community License 1.0, which requires a separate license from Qwen for commercial use by a "Model as a Service" or "AI Work Assistant" (AI coding or office productivity product) business, while internal use that exposes nothing to third parties is exempt.
- The Coder (Apache-2.0 per its card) and Swift 1.5 (Swift Open License 1.0) carry further licenses of their own.
The reasoning levels do not line up: the model card lists xhigh (default), medium and low, while Strata exposes none, low, medium and high with high as the model's default; how Strata maps them onto the trained levels is not documented in what was read.
GIGAZINE's background article differs from Qwen's own pages twice: it gives the training cost as one ninth of Qwen3.8-27B where the QwenLM README says one ninth of Qwen3.7-Plus, and it names the comparison column Claude-Opus-4.8 (Max) where the model card read on 2026-10-08 shows Claude-Opus-4.6 (Max).
AINews says llama.cpp v0.6.0 "Adds" Qwen3.8-Flash-Next, but the QwenLM README already lists llama.cpp support (text and vision) and Hacker News users run Unsloth's GGUFs on llama.cpp, so what v0.6.0 adds for this model is unclear.
The Hacker News title mentions an RTX 4090 at 100 T/s, a 24 GB card, while the project's headline claim is about 12 GB cards.
The docs disagree on how the n-gram table is read: HOW_IT_WORKS.md and the paper say through the OS page cache, while DETAILS.md says the default --ple-io direct reads it unbuffered past the OS cache, with --ple-io ram for rotational disks (#605).
The Qwen blog post (qwen.ai) did not render through the page cache or WebFetch, so the architecture facts here come from the model card and the QwenLM README.
The Qwen3.8-Flash API price ($0.16 / $0.47 per 1M input / output tokens) comes from Qwen's post on X as embedded by GIGAZINE on 2026-08-27, and the current QwenCloud price was not checked.

Ideas for practice and output

Run a one-day spike on a spare desktop with a 12-24 GB NVIDIA card, 64 GB of RAM and an NVMe SSD: install IQ2_XS and IQ3_S, point Claude Code (ANTHROPIC_BASE_URL, ANTHROPIC_MODEL) and Codex CLI (wire_api = "responses") at it, and record the first-prompt TTFT, decode tok/s and cache reuse on later turns.
Score 10-20 of the team's own small coding tasks, including Japanese prompts and comments, on Strata IQ2_XS, IQ3_S and the Coder against the hosted model the team uses today, to see whether the quality loss reported for low-bit quants and CJK text matters for its work.
Run the same GGUF on llama.cpp for the same tasks to separate engine effects from quantization effects, since the Hacker News vision test suggests the engine itself can cost quality.
Before any use beyond personal experiments, review the Qwen Community License 1.0 with legal: an internal coding assistant served to colleagues may count as internal use, but anything offered to customers as a coding or office assistant may need a separate license from Qwen.
Write a short security checklist for local model servers from Strata's own rules: keep 127.0.0.1, set --api-key before --host 0.0.0.0, use 0.1.38 or later for the DNS-rebinding protection, leave the experimental speed projection off, and read docs/AI_SETUP.md before letting an agent run the installer.
Compare the monthly cost of a local box (hardware amortization and power) with the team's token volume at the Qwen3.8-Flash API price relayed by GIGAZINE ($0.16 / $0.47 per 1M tokens), and write the result up as an internal note or a short Zenn article on when local 125B MoE serving pays off.

4. 🔦 Reflection announced Beam, a 501B-parameter (23B active) open-weight mixture-of-experts model for coding and agentic work, with early access now and Apache 2.0 weights promised later in October

Selected / impact 1 / potential 1 / attention 2 / anchor 10-05, before the window / kind: release / areas: models.
Feed items in this topic:
- ainews 10-06 Reflection Beam - 501B-A23B American Open Model — Reflection's post drew 549 points and 174 comments on Hacker News when fetched
Anchor: Reflection announced Beam on 10-05, a day before the window, and AINews brought it to the feeds on 10-06.

Collected information

[A] Reflection — Introducing Beam: Reflection's 501B open-weight model (2026-10-05)

https://reflection.ai/blog/introducing-beam

"We are introducing Beam, Reflection's first open-weight model."
"Beam is a sparse Mixture-of-Experts model with 501 billion total parameters, 23 billion active, built for coding, reasoning, and agentic workloads."
Reflection pretrained it on "23.8 trillion diverse, curated, high-quality tokens from the web and proprietary licensed datasets, matching or outperforming available similar-sized open base models".
"Our high-compute RL run generated over 100 million rollouts on 10.5K NVIDIA GB300 GPUs over 4 weeks of training."
"Together, these efforts produced competitive open-weight performance with frontier inference compute efficiency."
"Beam is undergoing final red-teaming and evaluations."
Early access is a sign-up at platform.reflection.ai, and "We will release the weights, technical report, model card, and developer artifacts later this month."
"We trained Beam with a particular focus on coding and agentic performance."
"Beam advances the Western open-weight frontier and is competitive with larger open models like GLM 5.2 and approaching Qwen 3.8-Max on coding and agentic tasks."
"Where frontier open models like Kimi K3 remain ahead on raw capability, Beam's advantage is efficiency at inference time."
The benchmark table uses "NR" for "scores that have not been reported", in the column order Beam / Inkling / Nemotron 3 Ultra / GLM 5.2 / GLM 5.3 / Kimi K3 / Qwen 3.8 Max / DeepSeek V4.1 Flash.
Agentic coding and terminal rows:
- DeepSWE v1.1: 44.4 / NR / NR / 44.0 / 61.0 / 68.0 / 51.0 / 74.2.
- SWE Bench Pro v2-Hard: 77.2 / 56.9 / NR / NR / 84.3 / 88.2 / NR / NR.
- SWE Bench Pro v1: 65.5 / 54.3 / 46.4 / 62.1 / NR / NR / 67.7 / NR.
- Terminal Bench v2.1: 80.1 / 63.8 / 56.4 / 81.0 / 88.2 / 88.3 / 86.6 / 90.6.
- SWE Atlas Codebase QnA: 34.6 / NR / NR / NR / 61.0 / 68.0 / NR / NR.
- SWEBench Multilingual: 78.0 / NR / 67.7 / NR / NR / NR / NR / NR.
- SWEBench Verified: 80.9 / 77.6 / 70.7 / NR / NR / NR / NR / NR.
Reasoning rows:
- AIME 2026: 97.8 / 97.1 / NR / 99.2 / NR / NR / NR / NR.
- HLE no tools: 36.2 / 29.7 / 26.7 / 40.5 / 42.3 / 46.9 / 43.6 / 39.1.
- SciCode: 49.7 / 46.1 / 44.6 / NR / 59.0 / 58.7 / 52.1 / 52.0.
- CriPT AA: 16.3 / 5.4 / 3.1 / 20.9 / 19.1 / 23.4 / 20.0 / 14.3.
- GPQA Diamond: 90.5 / 87.2 / 87 / 91.2 / 91.7 / 93.5 / 92.6 / 90.9.
Tool calling and search rows:
- AutomationBench public: 37.0 / NR / NR / 26.2 / 48.2 / 46.7 / 39.8 / 54.8.
- MCP Atlas: 78.7 / 76.0 / 63.1 / 77.8 / 84.2 / 82.3 / 84.5 / NR.
- tau3 banking: 38.0 / 25.0 / 22.6 / 37.1 / NR / 37.1 / 55.2 / NR.
- BrowseComp with context management: 77.4 / 77.1 / 44.4 / NR / NR / 91.2 / NR / NR.
- DeepSearchQA with context management: 80.1 / NR / NR / NR / NR / 95.0 / NR / NR.
General capability rows:
- AA-LCR: 79.3 / 77.3 / 79.3 / 78.3 / 79.7 / 88.7 / 80.3 / 84.0.
- LongBench v2: 65.5 / NR / 61.9 / 64.0 / NR / NR / 66.3 / NR.
- IFBench: 79.7 / 79.8 / 81.7 / 73.3 / NR / NR / 82.8 / NR.
- AA Omniscience (index), "public split only (our results)": 13.0 / 14.2 / 8.6 / NR / 22.6 / NR / NR / 6.6.
"On advanced reasoning benchmarks, it achieves scores comparable to GLM-5.2 while using 3–4× less inference compute."
"Efficiency gains are even more pronounced when comparing to models in the 2T+ parameter family like Qwen 3.8-Max, which require significantly more inference compute per token."
Reflection calls Beam "a powerful workhorse model for enterprise coding and agentic workloads".
The efficiency figure covers DeepSWE, Humanity's Last Exam and Terminal Bench 2.1, measured in FLOPs and in token count, with data from Artificial Analysis and DataCurve.
- Compute is estimated as "FLOPs ≈ 2 × active parameter count × mean generated tokens per attempt", counting reasoning and answer tokens and, for MoE models, the active parameters.
- "These estimates exclude prompt prefill, context-dependent attention operations, and serving overhead, so they represent an approximate compute comparison rather than measured inference cost."
"To scale reinforcement learning, we deployed 10.5K NVIDIA GB300 GPUs for four weeks generating more than 100 million rollouts with a maximum context length of 256K tokens."
"Training and grading used approximately 1.3 billion sandboxes."
Reflection "sourced one million high-quality coding, agentic, and STEM environments" for the run.
"We believe this is one of the largest scale RL runs conducted by any open lab to date."
"Across our evaluation suite, capabilities continued to improve as we increased RL compute, with no sign of a plateau."
The RL scaling figure covers the reasoning expert's 80M of the over 100M rollouts, and "For comparison, Inkling was trained on 30M rollouts and MiMo on 753K."
Beam was trained with asynchronous policy gradients, where policy staleness and training-inference mismatch are the main sources of instability.
- New algorithms keep "fully asynchronous RL at scale that remains stable, even when learning from interactions generated more than a day earlier".
- "Even when training Beam with one-day staleness—107 weight versions behind the current policy—the numerics remain stable."
A controllable length penalty first shortened completions as performance rose, and later longer completions brought further gains as agentic skills grew.
"Users can control this tradeoff through Beam's reasoning effort parameter: lower settings favor shorter responses, while higher settings allow longer reasoning to improve performance on demanding tasks."
During training on reasoning, software engineering and terminal tasks, browsing improved "despite the absence of browsing tasks from the RL mixture".
- "When given web access, it organically learned to search for and query other large language models, and to use OCR APIs to read documents."
"Although Beam is text-only, it can work with information from other modalities when represented as text."
The demos are a p5.js astronaut game, a land/water grid puzzle, a live NYC subway map built from NYC MTA data, and a Gemma-4 fine-tuning notebook.
- In the land/water demo (a 180×90 grid, 16,200 points) Beam "gets 95.5% coverage right, putting us between Opus 5 (92.5%) and Fable 5 (97.8%)".
- For the notebook, "We plugged Beam into OpenCode, asked it to look at Unsloth", and Beam raised Gemma's accuracy on its held-out Text2SQL test set by 66.5%.
The pool of "nearly one million environments" was built "primarily through synthetic data pipelines, supplemented by proprietary vendor data and open-source sources".
- Tasks were filtered for difficulty and for quality ("not underspecified, misleading, guessable, hackable, or otherwise broken or noisy"), then tested through RL.
- "Throughout Beam's development, we found that compromises in data quality led to capability plateaus and other training issues."
"During Beam's training, we sustained an average of 110K concurrent rollouts."
The RL platform tags every token with the model version that produced it.
It ran at inference-to-training GPU ratios from 3.9:1 to 5.4:1 and resized the trainer across five GPU mesh configurations without losing state.
New weights reached the inference fleet in a median of about 12 seconds, through RoCE across racks and NVLink within them, cutting cross-rack traffic by 75% and making fleet-wide adoption 2.2× faster.
"During the run, 71 inference incidents were handled without terminating the training job", with a median recovery of eight minutes and lost capacity of 0.02% of serving GPU-minutes.
"We supported up to 170K concurrent sandboxes during the run."
- "Across the platform, we processed more than one billion sandbox creation requests, spanning over 20 clusters, two clouds, and four regions."
- "90% of new sandboxes were ready in under 10 seconds."
Dynamic packing kept training batches 99.99% full and per-GPU trainer throughput within 1.5% as mean rollout length grew almost 70%.
"Independent judges re-screened passing solutions for verifier exploits, while replayable records made rewards and their use in training inspectable."
Reflection pretrained "a series of iteratively bigger models" and decontaminated the training data against its own validation sets.
- "The scaling held; the final Beam Base matches its predicted performance, and also matches or outperforms accessible similar-sized open-source base models."
The architecture "combines interleaved local and global attention, fine-grained routed experts, a controlled residual stream, and multiple forms of load balancing".
Expert balancing builds on auxiliary-loss-free load balancing (DeepSeek-AI et al., 2024) with "cosine decay of expert-bias updates", plus sequence-level balancing.
- "The busiest expert's load, averaged across MoE layers, reaches just 1.04× at pretraining completion."
A depth-based residual scaling, SandwichNorm, elementwise attention gating and FP32 residual accumulation keep activations bounded, and "Residual stream RMS remains bounded throughout pretraining across all 52 layers of Beam".
"We train on almost all publicly accessible and unrestrictively-licensed code and code documentation on the web."
"about 95% of raw Internet tokens are eliminated through parsing, deduplication, and curation", while "conventional techniques would have missed roughly 1.8 trillion high-quality tokens we retain, including 87% of our curated web-code tokens".
A PDF pipeline combines "a vision-language OCR model with in-house quality classifiers and artifact detectors", run across thousands of GPUs over petabytes of technical data.
Code and technical content were repeated several times over the training horizon.
"Beam was pretrained end-to-end in under four weeks on a cluster of 6,144 NVIDIA GB300 NVL72 GPUs."
The pretraining stack was built almost entirely in-house, including a topology-aware Kubernetes-based scheduler and a silent data corruption (SDC) detection system.
- The run had nine semi-automatic rewinds, and its goodput "reached 92.3% towards the end".
"Midtraining also extends Beam's effective context length to 1M tokens."
For safety and alignment Reflection trained a second model from the pretrained checkpoint with a separate SFT and RL pipeline, and merged the two teachers "via multi-teacher on-policy distillation (MOPD)".
The principles come in three tiers: rules Beam should not break, qualities it should satisfy (using its context, accurate claims, acknowledging uncertainty, following the user's request transparently), and a default style ("direct, thorough, efficient, and proactive").
Forecasting reward effects before RL predicted RL gains better than the Best-of-N ceiling alone ("r = 0.79 compared to r=0.46 with BoN ceiling").
Safety training used deliberative alignment (Guan et al., 2024) with an adversarially built dataset, and safety RL covered single-turn, multi-turn, jailbreak and agentic scenarios with a simulated adversary.
"We will publish the results of our safety evaluations in our model technical report and will open-source safety evaluations we developed and used internally to create a shared, inspectable standard that the open ecosystem can test against and contribute to."
"We are making this early version of Beam available to a select group of users; you can sign up for the waitlist here."
"This month, we will release the weights under an Apache 2.0 license, along with documentation and the full stack for running, evaluating, and fine-tuning the model."
"We will be launching Beam with an ecosystem of distribution partners, as well as integration with a broad range of open source libraries and harnesses, so developers can use Beam across existing open-source workflows."
"Beam is the first model in a series", and "We are already training what comes next".

[B] Latent Space (AINews) — [AINews] Reflection Beam - 501B-A23B American Open Model (2026-10-06)

https://www.latent.space/p/ainews-reflection-beam-501b-a23b

The issue is subtitled "A small win for US open source" and covers AI news for 10/03 to 10/05.
It recalls that Reflection launched with Latent Space over a year earlier "with big goals on coding" and "stayed 'stealth' longer than Thinking Machines".
"They compare themselves to Inkling, Nemotron, and GLM 5.2, but the SOTA GLM 5.3, Kimi K3, Qwen 3.8 Max, and DeepSeek V4.1 Flash are generally ahead."
"Still, since this is US-trained from scratch, there's a segment of the market that has been eagerly waiting for more options here, and more importantly, Reflection has now announced its arrival as a functional neolab!"
The recap describes "a text-only 501B-total / 23B-active MoE for coding, agentic and scientific work", trained from scratch, with "full weights under Apache 2.0" due this month.
Team posts cite 23.8T pretraining tokens, "partly from an OCR pipeline over hundreds of millions of PDFs", and "a stable RL/OPD run on 10K GB300s with more than 100M rollouts across ~1M tasks".
A relayed summary of Reflection's claims gives "80.9 on SWE-bench Verified, 3–4x the inference efficiency of GLM 5.2, and four weeks each of pretraining and RL on ~10,500 GB300s".
Alex Polozov promises a tech report and OSS integrations.
Axios reported the launch ahead of time, and per a relayed summary it "said Reflection pays $150M/month for Colossus compute plus a $1B Nebius deal, and that other unnamed US labs will ship open models this month".
"Artificial Analysis has early access and expects Beam to be among the most token-efficient open models for its intelligence."
"Elie Bakouch estimates only ~12% BF16 MFU in pretraining."
- "He reads the architecture as 3:1 interleaved global/sliding-window attention and notes better held-out code perplexity than DSv4."
"Teortaxes calls Beam an iso-FLOP replication of DeepSeek V3."
- "He infers ~1.3B RL sandboxes over 4 weeks, with up to 170K running at once."
Observers place Beam around GLM-5.2 level (iScienceLuvr) and below DSv4 Flash on some benchmarks (a critique on X).
"Nathan Lambert groups it with Nvidia and Thinking Machines as strong US releases that still trail Chinese counterparts."
Among the top tweets by engagement, "Reflection introduces Beam" is listed at 7.4K.

[B] Latent Space (AINews) — [AINews] Quasi-Riemann-Hypothesis: OpenAI publishes 722 math papers solving 90 of the top 500 open math problems (2026-10-07)

https://www.latent.space/p/ainews-quasi-riemann-hypothesis-openai

"A Zhihu analysis of Beam describes a 501B/23B MoE with 23.8T pretraining tokens."
"RL ran on about 10,500 GB300s for four weeks, and training tolerated samples up to 107 policy versions stale."
"Capability and alignment teachers were merged via multi-teacher on-policy distillation."
The same list of open releases gives Ling 3.1 Flash as 560B total and 25B active parameters, scoring 41 on Artificial Analysis's index, priced at $0.30/$0.90 per million tokens, with weights coming.

[B] TechCrunch — Reflection debuts Beam, an open-weight AI model to rival Chinese models at lower compute cost, by Rebecca Bellan (2026-10-05)

https://techcrunch.com/2026/10/05/reflection-debuts-beam-a-open-weight-ai-model-to-rival-chinese-models-at-lower-compute-cost/

"Reflection AI is officially unveiling Beam, its first frontier, open-weight AI model."
The "two-year-old, Brooklyn-based startup claims Beam matches the performance of leading Chinese open models on advanced reasoning benchmarks at dramatically lower costs".
The announcement confirms Axios's weekend report that the startup was close to a launch.
The blog describes Beam as a text-only MoE model trained with high-compute RL for reasoning, coding and agentic tasks at "a fraction of the token cost and inference time compute" of rivals.
"Beam is a 501-billion-parameter model with 23 billion active parameters."
"It was pretrained on 23.8 trillion tokens and has a 1 million token context window."
"To compare, Z.ai's GLM-5.2 has roughly 744 billion total parameters with 40 billion active."
"Reflection's performance claims haven't been independently verified", and the company calls Beam a "workhorse model" for enterprises, the public sector and developers.
Its most direct US rival "might be Inkling", Thinking Machines Lab's open model from July.
- "Reflection's own benchmarks show that Beam outscores Inkling on four coding tests where both report results, but Inkling is a multimodal model and Beam is text-only."
Reflection was founded in 2024 by two former Google DeepMind researchers and has raised roughly $4.7 billion per PitchBook, at a $25 billion pre-money valuation in its last round.
Its compute deals with SpaceX and Nebius, worth more than $7 billion together, secure Nvidia GB300 chips through 2029.
Reflection aims Beam at enterprises and sovereign nations through "AI factories", which let institutions train its models on their own data, and is testing a sovereign AI factory partnership with Shinsegae Group in South Korea.
"Reflection says it will release Beam's weights and full technical details this month, with distribution through hyperscalers and neoclouds and integrations across open source libraries at launch."
"Reflection did not respond in time to TechCrunch's requests for more information."

[B] SiliconANGLE — Reflection AI debuts open-source Beam model with 501B parameters, by Maria Deutscher (2026-10-05)

https://siliconangle.com/2026/10/05/reflection-ai-debuts-open-source-beam-model-with-501b-parameters/

Reflection AI "introduced Beam, an open-source large language model with 501 billion parameters".
Reflection reportedly signed a $6.3 billion deal with SpaceX to rent Nvidia GB300 NVL72 appliances, each with 72 graphics cards, and used them to train Beam.
GLM-5.2 "includes about 250 billion more parameters", and Reflection says Beam can do some tasks better "while using between one third and one fourth the hardware".
Beam approaches Qwen 3.8-Max, "a model with over 2 trillion parameters".
"Beam is the first open-source model from a U.S. startup to have demonstrated comparable or better performance."
"However, free LLMs continue to trail frontier models such as Anthropic PBC's Claude Fable 5.1."
Reflection built Beam Base from a small prototype through successively larger models, on "a cluster of 6,144 graphics cards", with 23.8 trillion tokens and custom filters for each programming language, in under four weeks.
Midtraining extended the context window and strengthened reasoning before the RL phase.
"Reflection AI spun up 10,000 GB300 graphics cards and used them to launch 1.3 billion reinforcement learning sandboxes."
The RL phase took four weeks, with a median recovery time of eight minutes across 71 errors.
"Beam is initially available through an early access program", and the weights, documentation and fine-tuning tools are due later this month.

[B] The Decoder — Reflection's Beam becomes the most capable open-weight model built outside China, by Jonathan Kemper (2026-10-06)

https://the-decoder.com/reflections-beam-becomes-the-most-capable-open-weight-model-built-outside-china/

"AI startup Reflection is releasing Beam, its first open-weight model built for coding and reasoning, with a focus on compute efficiency over raw performance."
"Beam activates just 23 billion of its 501 billion parameters per token and matches GLM 5.2 on key benchmarks while using three to four times less compute, according to Reflection."
"The model was trained with reinforcement learning on 10,500 Nvidia GPUs over four weeks."
- "It will ship 'later this month' under the Apache 2.0 license."
"Instead of chasing peak performance, Beam aims to deliver strong results with minimal compute, putting it in direct competition with Chinese open-weight models from Deepseek and Qwen."
It comes close to "the much bigger Qwen3.8-Max" on coding and agent benchmarks, Kimi K3 still beats it on raw performance, and Reflection says a successor is in training.
The article reproduces Reflection's agentic coding table with the same numbers.
It reports the "emergent capabilities" in browsing, the tunable reasoning parameter, the demos and that Beam is text-only.
"Beam is still going through final safety testing, and an early version is available to select users for now."
Reflection was founded in 2024 by Misha Laskin, who led reward modeling for Gemini, and Ioannis Antonoglou, who helped build AlphaGo, and released the codebase agent Asimov in summer 2025.
"The company releases its model weights but keeps training data and pipelines proprietary."

[B] GIGAZINE — Reflection announces Beam, a 501-billion-parameter open model to counter China's open-source AI, claiming GLM 5.2 parity at a third to a quarter of the compute (2026-10-06, in Japanese)

https://gigazine.net/news/20261006-beam-reflection-501b-open-weight-model/

GIGAZINE introduces Reflection as a US AI startup and Beam as a 501B-parameter open model with 23B active, citing Reflection's post and Semafor.
It relays the 23.8T-token pretraining and an RL phase on 10,500 NVIDIA GB300 for 4 weeks generating over 100M rollouts, which it explains as trials in which the model produces an answer or a sequence of actions.
At the time of writing the model was not public because of final red-teaming and evaluation, the full weights were planned within October 2026, and a waitlist was open at "Reflection Playground" (platform.reflection.ai/login).
It lists the benchmarks in Reflection's comparison figure (DeepSWE, Terminal Bench, HLE No Tools, SWE Bench Pro, SWE Bench Verified, CritPT AA) and says Beam performed on a par with the compared open models (GLM 5.2, Qwen 3.8-Max, Inkling, Nemotron Ultra) on each.
It restates the efficiency claim as GLM-5.2-level scores at a third to a quarter of the inference compute, with a larger gap against 2T-plus models such as Qwen 3.8-Max.
It embeds CEO Misha Laskin's post: "Beam is very token-efficient, pre-trained from scratch, and scaled with the largest RL run documented openly we are aware of."
- "Open also means safer."
- "AI is both foundational as a science and a technology, and the safest way that also ensures the benefits of AI are distributed evenly is by making it open."
It embeds technical staff member Zach Wentz: "On the tech side of things 1.3B sandboxes is truly a frontier open RL run, and we did so with a dramatically smaller team and less compute than the one I led at Meta."
It embeds Alex Polozov, who joined in November 2025 when pretraining had "only 5-10 people and a bit of code!"
- He adds that "later this month we will also drop the full weights release under Apache 2.0, a detailed tech report with the cool LLM science, and partner integrations with the OSS ecosystem".
It embeds data platform lead Jake Nations: "I'm most proud of the OCR pipeline we put together generating trillions of tokens from hundreds of millions of PDFs."
It embeds Ollama's welcome: "More US models coming to Ollama!"
It links Alex Heath's interview with CEO Misha Laskin and CTO Ioannis Antonoglou, whose description says "Reflection has raised $4.6 billion from investors that include Nvidia, Sequoia, and Lightspeed."
The article had 16 Hatena Bookmark users when checked on 2026-10-08.

[B] Mynavi News — US-based Reflection AI's 501B open-weight AI Beam: the US counters China in open-weight models (2026-10-07, in Japanese)

https://news.mynavi.jp/article/20261007-5091137/

Reflection AI announced Beam on October 5 (local time) as a 501B-parameter model focused on coding, reasoning and AI agents, its first open-weight model, with the weights due in October.
Beam is an MoE model that uses 23B of its 501B parameters at inference, pretrained on 23.8T tokens, with RL on 10,500 NVIDIA GB300 for 4 weeks generating over 100 million rollouts.
By the company's own evaluation it competes with Z.ai's GLM-5.2, approaches Alibaba's Qwen3.8-Max on coding and agent tasks, and falls short of some large open models such as Kimi K3, with inference efficiency as its strength.
Reflection AI was founded by former Google DeepMind researchers, and the weights are not yet public because final red-teaming and evaluation are under way.
The weights are to be published in October under Apache 2.0, with a technical report, a model card and the software for running, evaluating and fine-tuning the model.
The date is taken from the article URL, and the article had 0 Hatena Bookmark users when checked on 2026-10-08.

[C] Hacker News — Beam: Reflection's 501B open-weight model (2026-10-05)

https://news.ycombinator.com/item?id=49969183

The story was submitted by Philpax on 2026-10-05 at 19:16 UTC and had 549 points and 174 comments when fetched on 2026-10-08.
The top comment (36 replies): "This appears to be larger than DeepSeek v4.1 Flash, more expensive to run, and worse on every measured metric."
- Replies point to the framing "Beam advances the Western open-weight frontier", and one says "Reflection raised on the idea of creating the 'American Deepseek Project'".
- Another expects the US origin to help Reflection win deals with American companies and Western governments even if it never fully beats DeepSeek.
One user quoted the earlier caption of the land/water demo, which said the puzzle "is a few days old, so could not appear in the training data", and showed the idea on LessWrong from at least August 2025.
- A Reflection team member replied "The team did not realize that the trend went that far back" and said the caption had been updated.
One user compared Beam with DeepSeek V4.1 Flash: 552B total, 8B active in prefill and 16B in decode, 196B n-gram parameters, 45T pretraining tokens, vision and MIT weights on launch day, against Beam's 501B, 23B, no n-gram table, "28T" tokens, no vision and Apache 2.0 weights "This month".
- "Talk is cheap, show me the weights."
One user notes that GLM 5.3 and DeepSeek V4.1 Flash are in the table but not in the charts, and that there are no Artificial Analysis Index or Arena results.
Another says "the performance chart puts the better open source models behind the fold making it seem like it outperforms them".
One commenter confused Reflection AI with the 2024 Reflection 70B, and another replied that "Reflection AI is a completely different company with no relation (as far as I can tell) to the model you are referencing from 2024".
One user calls announcing before the weights "a marketing miss", because without the weights on disk he is likely to forget the model by its release.
"The meaningful test begins after the weights arrive: fixed harness, network disabled, repeated trials, and real latency, memory, energy and cost per completed task."
Several users ask what hardware runs Beam, and one wishes for more 90B-133B MoE models that fit Mac workstations with disk offload.
One user guesses Beam uses global attention layers everywhere and needs a large KV cache, which the post's "interleaved local and global attention" contradicts.
One user asks why open models after Qwen3.8-Flash and DeepSeek V4.1 Flash do not use n-gram embeddings, which can be served from SSD or CPU RAM.
One user wishes a Western lab had started, as Qwen did, by post-training existing weights instead of pretraining from scratch.
One commenter writes of having been "in the room with pretraining day 1 to help monitor the training job launch".

Notes

The weights, model card and technical report are not out: Reflection promises them "later this month" (October 2026), and a Hugging Face API search for models by reflection-ai, ReflectionAI, reflectionai and reflection returned none on 2026-10-08.
The early-access platform (platform.reflection.ai) did not render through the page cache or WebFetch, so no price, rate limit, context limit or API format for early access could be checked.
Every benchmark number is Reflection's own, as TechCrunch notes, and the only independent signal so far is Artificial Analysis's qualitative expectation, relayed by AINews, that Beam will be among the most token-efficient open models for its intelligence.
The "3–4× less inference compute" claim is an estimate built from Artificial Analysis and DataCurve token counts that excludes prefill and attention costs, which dominate long agentic coding sessions, so it says little yet about cost per completed agent task.
On the rows where GLM 5.3, Kimi K3 or DeepSeek V4.1 Flash have scores, Beam trails on most, with three exceptions: tau3 banking (38.0 against Kimi K3's 37.1), CriPT AA (16.3 against DeepSeek V4.1 Flash's 14.3) and AA Omniscience (13.0 against DeepSeek V4.1 Flash's 6.6).
- The Hacker News claim that Beam is "worse on every measured metric" than DeepSeek V4.1 Flash is therefore not exact, although it holds on 7 of the 9 rows both report.
The Decoder's headline calls Beam the most capable open-weight model built outside China, but in Reflection's own table Inkling leads on IFBench (79.8 against 79.7) and AA Omniscience (14.2 against 13.0), Nemotron 3 Ultra leads on IFBench (81.7), and Beam and Nemotron 3 Ultra tie on AA-LCR (79.3).
The RL GPU count is 10.5K in the post, about 10,500 in The Decoder, GIGAZINE, Mynavi News and the AINews summary, 10,000 in SiliconANGLE and 10K in a team post relayed by AINews.
A summary relayed by AINews gives "four weeks each of pretraining and RL on ~10,500 GB300s", while the post gives pretraining as under four weeks on 6,144 GB300 NVL72 GPUs.
The pretraining corpus is 23.8T tokens in every source except one Hacker News comparison that gives "28T" without a source.
The context length is described as an effective 1M tokens after midtraining (RL rollouts went up to 256K), and TechCrunch reports "a 1 million token context window"; what the release or early access will serve is not stated.
The land/water demo caption was changed after the Hacker News critique, and the post as fetched on 2026-10-08 shows the revised caption without the claim that the puzzle is a few days old.
Comparing with the Strata topic's model is not like-for-like: Qwen3.8-Flash-Next (125B total, 6B active) self-reports 58.7 on DeepSWE 1.1 (best of the Claude Code and mini-SWE-agent harnesses), against Beam's 44.4 on DeepSWE v1.1 in Reflection's table, with different evaluators and harnesses.
Reflection has not stated serving hardware, quantized variants or the distribution partners, so whether Beam reaches Bedrock, Vertex AI or Foundry, or runs on anything short of a multi-GPU server, is open.
Funding figures differ between sources ($4.7 billion per PitchBook in TechCrunch, $4.6 billion in Alex Heath's interview description) and are out of scope here except as context for the lab's staying power, which a Hacker News commenter raised.

Ideas for practice and output

Put Beam on the open-model evaluation backlog for when the weights and technical report land later in October, and run it in a fixed harness with the network disabled and repeated trials against GLM 5.3, DeepSeek V4.1 Flash and Qwen3.8-Flash-Next on the team's own agentic coding tasks.
- Record solved tasks, tokens per solved task, latency and cost per completed task, since token efficiency is Beam's main claim and Reflection's figure excludes prefill.
If the organization restricts models of Chinese origin, prepare a one-page comparison of US and European open-weight options (Beam, Inkling, Nemotron 3 Ultra) covering license, modality, context, serving hardware and availability on Bedrock, Vertex AI or Foundry, and fill in Beam's column when its model card and distribution partners appear.
When the technical report ships, read the safety evaluation results and check whether the open-sourced safety evaluations can be reused in the team's own red-teaming of open models.
Watch Artificial Analysis for an index score and token counts for Beam, which would be the first independent test of the efficiency claim, and update the team's model shortlist only after that.

5. 🔎 Google DeepMind released EmbeddingGemma 2, a 740M-parameter Apache 2.0 embedding model that maps text, code, images, audio and video into one vector space for on-device retrieval

Selected / impact 1 / potential 1 / attention 2 / anchor 10-06 / kind: release / areas: models, agent building.
Feed items in this topic:
- deepmind-blog 10-07 EmbeddingGemma 2: an open, lightweight multimodal embedding model — 415 points and 46 comments on Hacker News when fetched
- google-developers-blog (undated in the feed) Bring multimodal semantic search to the edge with EmbeddingGemma 2

Collected information

[A] Google DeepMind — EmbeddingGemma 2: an open, lightweight multimodal embedding model, by Sahil Dua and Henrique Schechter Vera (2026-10-06)

https://blog.google/innovation-and-ai/technology/developers-tools/embeddinggemma-2/

The feed's DeepMind blog URL redirects to this blog.google post, and both saved copies carry the same text, dated Oct 06, 2026.
Both authors are Research Engineers at Google DeepMind.
Lede: "EmbeddingGemma 2 is the most capable model for on-device multimodal embeddings, natively mapping combinations of text, images, audio, and video into a unified embedding space."
The first EmbeddingGemma, a text embedding model, passed "more than 20 million downloads", used for "smarter on-device search tools and privacy-first retrieval augmented generation (RAG) pipelines".
"Today, we're launching EmbeddingGemma 2, expanding beyond text to unify code, images, video, and audio in a shared embedding space."
"Built on the Gemma 4 architecture and released under a commercially permissive Apache 2.0 license, EmbeddingGemma 2 has 740 million parameters, making it optimal for on-device inference."
Example uses: "find a specific video clip from a voice memo, or search through hours of audio recordings based on a text query, all processed by a single, natively multimodal model."
It is "Built from the same technology as Gemini Embedding models".
Best-in-class for its size: "Achieves leading scores among sub-1B multimodal embedders for its size across benchmarks like MTEB (Massive Text Embedding Benchmark) Code and MAEB (Massive Audio Embedding Benchmark), while matching or outperforming many larger models across text, vision, and audio tasks."
Modular by design: "Requires as little as 270M parameters for text-only workloads with optional vision (170M) and audio (300M) encoders for full multimodal support."
Storage-efficient: with Matryoshka Representation Learning (MRL), "developers can dynamically truncate output vectors from 768 dimensions down to 512, 256, or 128 dimensions", which "provides up to 6x storage reduction for local vector databases and memory usage."
On-device: "With quantization, on a Google Pixel 11 Pro, EmbeddingGemma 2 requires as little as ~191MB active RAM for text-only weights and ~567MB for the full multimodal model."
Context: "an 8K token context window (4x larger than EmbeddingGemma 1), allowing it to process up to 5.5 minutes of audio, 29 images, 58 video frames, or interleaved combinations thereof directly on local hardware."
Quality: it "matches the strong multilingual text performance of EmbeddingGemma while delivering a significant 9.92-point improvement on code performance (in MTEB Code, from 68.76 to 78.68)".
- The post calls it "well-suited for local codebase indexing, semantic code search, and coding agent retrieval."
"Across image, video, documents, and audio, it sets a new standard in quality-per-parameter for sub-1B models and even outperforms some specialist models more than twice its size."
- The post names no competing model and gives no competitor scores; it points to the model card for full metrics.
Pairing with Gemma 4: "Because EmbeddingGemma 2 is built on Gemma 4 and shares its text tokenizer and audio encoder, developers can run both models together in a unified pipeline with a lower combined total memory footprint."
Demos: Instant Media Search (text or image to the media library) and Video Moments Finder (text or audio queries to moments in video) in Google AI Edge Gallery, and local file retrieval with Gemma 4 for reasoning in the Google AI Edge Foresight app.
The MediaPipe Decision Task API uses it for "real-time decision engines leveraging multimodal context for classification, routing, and predictive capabilities".
Weights: Hugging Face (google/embeddinggemma-2) and Kaggle, "with Gemini Enterprise Agent Platform Model Garden availability coming soon"; on-device builds in the LiteRT Community on Hugging Face.
On-device deployment: MediaPipe "for turnkey embedding, retrieval & decision tasks" or LiteRT "for custom model integration", and the browser through transformers.js or WebGPU (the webml-community/embeddinggemma-2-webgpu Space).
Serving: transformers, sentence-transformers, MLX (linked to Blaizzy/mlx-vlm), vLLM, llama.cpp (ggml-org/embeddinggemma-2-GGUF), SGLang, Ollama and LMStudio; vector storage in Qdrant; fine-tuning guidance by Unsloth.
"We worked closely with the following partners to ensure EmbeddingGemma 2 works immediately where you build".

[A] Google Developers Blog — Bring multimodal semantic search to the edge with EmbeddingGemma 2, by the Google AI Edge Team and the Android ML Team (2026-10-06)

https://developers.googleblog.com/google-ai-edge-with-embeddinggemma-2/

The page is dated Oct. 6, 2026, although the feed listed it undated.
For local search and media retrieval, "it reduces the latency and memory overhead of chaining separate image captioning, speech-to-text, and text-embedding models."
It repeats the 740M footprint and "~191MB active RAM for text-only weights and ~567MB for the full multimodal model on a Google Pixel 11 Pro".
"Most notably, EmbeddingGemma 2 can act as an ultra-low-latency on-device decision engine."
- "Without requiring any training data or fine-tuning, it matches user inputs directly against classification labels and descriptions, delivering instant, zero-shot intent routing in a matter of milliseconds."
Android: "In the coming weeks, we will also make this model available as a service on Android, accessible through ML Kit, including using NPU acceleration".
- Through ML Kit, developers get it "without having to manage the model or worrying about APK bloat", with "automatic model updates".
Instant Media Search embeds the query and the media on device, stores the media vectors "in a local SQLite database", and returns the items with the largest cosine similarity.
- It runs on MediaPipe UniversalEmbedder and SemanticRetriever, and results update on every keystroke.
- The example query is German: "Katze", then "Katze schläft auf Tastatur" re-ranks the grid; image and live-camera queries also work.
Video Moments Finder locates "specific visual moments across local video recordings without transcribing audio or generating intermediate text captions".
- It indexes "vision with audio chunks" of a selected local video and highlights the timestamps that match a descriptive query.
Both demos are in the Google AI Edge Gallery app on Google Play and the Apple App Store, with the source in the google-ai-edge/gallery repository.
Google AI Edge Foresight for Mac is "an experimental app that brings a context-aware meeting companion directly to your device", powered by EmbeddingGemma 2 and Gemma 4.
- It hooks into system audio and the microphone, works with any meeting platform and offline, and offers note enhancement and cross-modal retrieval over images, documents, transcripts and notes "with no cloud subscription costs".
"MediaPipe Tasks is adding support for EmbeddingGemma 2 to the existing Embedder and Semantic Retriever; the new interface to our current RAG SDK", targeting iOS, macOS, Windows, Linux and Web.
- Universal Embedder "Automatically handles image resizing, tensor normalization, and multimodal tokenization", returning "768-dimensional (or truncated 128d–512d) normalized vectors with zero boilerplate."
- Semantic Retriever is "An edge-optimized embedded vector search engine" that runs Approximate Nearest Neighbour (ANN) searches, "returning ranked matches in single-digit milliseconds."
- The Decision Task demo plays chess "with less than 100ms response time to evaluate 500 options each turn".
LiteRT: "a single .litertlm file runs out of the box on both CPU and GPU across all supported edge platforms."
- Visual embeddings take "as little as 37.3 ms (26.9 images per sec) on a MacBook M5 Pro GPU", measured "with a maximum budget of 70 vision tokens per image"; the per-device table did not survive text extraction.
Optimizations: modular loading of encoders, Quantization-Aware Training (QAT) that "Compresses model weights to INT4 and INT8", and an optimal computational graph loaded at runtime for the text and image input size, with developer-set vision token budgets.
MRL slicing in this post is said to cut "local storage and index footprints by up to 8x."
LiteRT also runs on the web (WASM); the device list and benchmarks are on the Hugging Face LiteRT model card, and a benchmark tool runs "across over 200 different real physical devices" in Google Cloud's Developer Device Platform.
Pre-quantized .litertlm bundles are on the Hugging Face LiteRT Community, and a zero-setup web demo runs in the browser.

[A] Google Developers Blog — EmbeddingGemma 2: The Developer Guide, by Maarten Grootendorst and Ian Ballantyne (2026-10-06)

https://developers.googleblog.com/en/embeddinggemma-2-the-developer-guide/

The authors are a Member of Technical Staff and a Senior Developer Relations Engineer.
"Based on Gemma 4, this sub-1B model maps text, code, images, video, and audio into a unified 768-dimensional space."
Load sizes: "270M (text/code), 440M (text + vision), 570M (text + audio), or 740M (full multimodal), all projecting into the same compatible vector space."
Code: it "Significantly outperforms EmbeddingGemma 1 on code search and technical retrieval, making it ideal for local codebase indexing and agentic code search."
Under the hood: text and code use "An adapted Gemma 4 decoder with an 8,192-token context window"; the vision encoder (+170M) handles "images, visual documents (PDFs, slides, charts), and video frames"; the audio encoder (+300M) "directly ingests raw audio".
Demo: they "embedded the Hugging Face transformers codebase with the 270M text-only setup", searched by an agent ("Gemma 4 26B A4B with the Pi agent harness").
It requires sentence-transformers v6.1.0 or later, installed with pip install -U sentence-transformers[image,audio,video] transformers.
Setting vision_config or audio_config to None in config_kwargs skips an encoder: "Disabled encoders are never loaded into memory, so the savings apply to both the weights and peak allocation".
Text uses task prompts through prompt_name, for example SearchQuery for queries and Document for documents.
Media go in a dictionary keyed by modality without a prompt, and interleaved inputs mark positions with <|image|>, <|video|> and <|audio|>.
A Hugging Face Space, the Embedding Draw Challenge (google/embedding-draw-challenge), guesses what the user draws.
MRL: pass truncate_dim (512, 256 or 128) with normalize_embeddings=True, or set it at load time; queries and documents must use the same dimension.
"in bfloat16 precision, storing a million 768-dimensional vectors takes roughly 1.5 GB of memory, while truncating them to 128 dimensions requires just 250 MB."
"In sentence-transformers, all four encoder setups load from the same checkpoint, so they share one vector space: a query embedded with the 270M text-only setup can be matched directly against documents embedded with the full model."
"If you start with a text-only index and later add image or audio embeddings, simply reload the model with the additional encoder enabled."
- "Embeddings you have already computed do not need to be re-computed."
Dimension guidance: 768d or 512d for multimodal and visual document retrieval or when recall matters more than storage.
- 256d (3x reduction) "Keeps most of the full quality of the original embedding on text and code and about 95% on image, video, and speech retrieval".
- 128d (6x reduction) for "Large text-only indexes and first-stage shortlisting": "Text and code retains around 90% quality, but image, video, and speech retrieval quality drop to around 75%."
Inputs: file paths (MP4 for video), URLs (images and audio), or in-memory PIL images, arrays and tensors; video is sampled at 1 frame per second by default and audio should be 16 kHz mono.
"EmbeddingGemma 2 scores 14% higher than EmbeddingGemma 1 on MTEB (Code), adds image, video, and audio retrieval while retaining the accuracy on multilingual text of EmbeddingGemma 1".
Tools listed: vLLM, Hugging Face Transformers, sentence-transformers, SGLang, MLX (linked to ml-explore/mlx-lm), Ollama, LMStudio and LiteRT, with Unsloth for fine-tuning.

[A] Google AI for Developers — EmbeddingGemma 2 model card (2026-10-06)

https://ai.google.dev/gemma/docs/embeddinggemma/model_card_2

The page reads "Last updated 2026-10-06 UTC", names Google DeepMind as author, and labels the license Apache 2.0 with a link to the gemma_4_license page.
"EmbeddingGemma 2 is an open multimodal embedding model built by Google DeepMind which maps text (incl. code), images, video, and audio inputs—and combinations thereof—into a single, unified 768-dimensional vector space."
It "understands 100+ languages, and achieves a ~14% improvement on code tasks relative to its predecessor."
The text backbone is 270M parameters (130M transformer + 140M embedder), with selectively loadable vision (170M) and audio (300M) encoders.
MRL covers 128d, 256d, 512d and 768d, "enabling up to a 6x reduction in vector storage costs with minimal impact on quality."
"Task-steered representations: Uses lightweight text instruction prefixes to optimize embeddings for different tasks".
Architecture: 24 layers, model dimension 512, hidden dimension 2048, a 1024-token sliding window, vocabulary 262,144, 4 heads, KV-heads 2/1 (local/global), local:global 5:1, GQA/MQA, gated FFN with GELU, mean pooling, and a 512→768 projection.
Input and output: text, images, video and audio; an 8,192-token context window; native output 768 dimensions; MRL truncation to 128, 256 and 512.
Benchmarks at 768d, full-precision checkpoint, EmbeddingGemma 2 against EmbeddingGemma 1 where given:
- MTEB (multilingual, v2), Mean(Task): 61.36 against 61.15.
- MTEB (code, v1), Mean(Task), NDCG@10: 78.68 against 68.76.
- MIEB (lite), Mean(TaskType): 64.64.
- MMEB v2 Image, Hit@1: 57.28; MMEB v2 VisDoc, NDCG@5: 67.84; MMEB v2 Video, Hit@1: 50.67.
- MSEB (Retrieval), MRR@10: 69.54; MAEB, Mean(Task): 49.39.
- No other model appears in the tables.
Truncation table (MTEB multilingual / MTEB eng / MTEB code / MIEB lite / MMEB v2 overall / MSEB retrieval / MAEB):
- 768d (1:1): 61.36 / 68.46 / 78.68 / 64.64 / 59.01 / 69.54 / 49.39.
- 512d (1:1.5): 61.17 / 68.41 / 77.24 / 64.32 / 58.38 / 69.18 / 49.21.
- 256d (1:3): 60.41 / 67.78 / 76.18 / 63.13 / 56.24 / 66.76 / 48.91.
- 128d (1:6): 57.89 / 65.68 / 71.41 / 59.06 / 45.65 / 56.71 / 46.92.
"model users can reduce storage requirements, with minimal quality impact down to 256d."
- "128d is best suited to text-only workloads."
Task prefixes apply to text only; "omitting it still works but reduces precision", and images, video and audio take no prefix.
- SearchQuery: task: search result | query: {query}, with documents as title: {title} | text: {content} (or title: none).
- QuestionAnswering and FactChecking use task: question answering | query: {question} and task: fact checking | query: {claim}.
- CodeRetrieval: task: code retrieval | query: {query}, with documents as title: {title or filename} | text: {code}.
- Symmetric tasks (Classification, Clustering, SentenceSimilarity) put the same prefix on every input.
- prompt_name="Document" applies title: none, so titled documents must be formatted by hand.
Effective sizes by config_kwargs: text only 270M, text and image 440M, text and audio 570M, full multimodal 740M; omitting encoders "differs among model libraries".
MRL at runtime: "Re-normalize after truncating", because "Skipping this step degrades ranking quality silently—it produces plausible-looking scores rather than an error."
- "Queries and documents must share a dimension."
- "Quality is close to lossless down to 256 dimensions."
- "128 dimensions degrades multimodal quality substantially and should be validated against your own workload before adoption."
Precision: "Run inference in bfloat16 or float32."
- "Do not use float16."
- "In float16 the model returns NaN or silently degraded embeddings rather than raising an error, so the failure is easy to miss."
Context budget, all modalities sharing 8,192 tokens: text 1 token per subword; image 280 tokens per image by default (~29 images); video 140 tokens per frame by default (~58 frames); audio 25 tokens per second (~327 seconds).
- A lower vision budget allows up to ~114 images or frames; the budget ranges from 70 to 1120 soft tokens per image.
- Video is sampled at 1 frame per second by default (configurable), and audio should be mono at 16 kHz.
Training data has "a cutoff date of January 2025", and its web text spans "over 140 languages".
"Unlike generative models, it does not undergo post-training alignment, safety tuning, or output-level moderation."
- "Developers and deployers are responsible for evaluating and implementing application-level safeguards, like retrieval filtering and fairness testing".
- Deployments must follow the Gemma Prohibited Use Policy.
"while EmbeddingGemma 2 supports 100+ languages, the model may not exhibit equal performance across languages."
Intended uses include "RAG over enterprise knowledge bases, code search from natural language queries, or spoken-query search over audio archives", classification, clustering, semantic similarity and fact verification.

[A] Google AI for Developers — EmbeddingGemma documentation overview (2026-10-06)

https://ai.google.dev/gemma/docs/embeddinggemma

It is "Built on the Gemma 4 decoder architecture" and runs cross-modal workflows "locally and offline on consumer GPUs or CPUs".
The license line links an Apache 2.0 License page under /gemma/apache_2.
"Smaller base footprint: Reduces the base text and code model size from 300M parameters down to 270M parameters."
"Extended context length: Supports up to 8,192 tokens for text and source code across over 100 languages."
The same page describes EmbeddingGemma 1 as "a 308M parameter multilingual text embedding model based on Gemma 3" with a "2K token context", "less than 200MB of RAM with quantization" and embeddings "in less than 22ms on EdgeTPU".

[A] Hugging Face — google/embeddinggemma-2 model page (as fetched on 2026-10-08)

https://huggingface.co/google/embeddinggemma-2

The card repeats the ai.google.dev model card.
Tags include Feature Extraction, Transformers, Safetensors, sentence-transformers and the model type embedding_gemma2.
"Downloads last month 7,562"; Safetensors, "0.7B params", BF16.
"This model isn't deployed by any Inference Provider."
Model tree: 26 finetunes and 30 quantizations; 12 Spaces use it; the Community tab showed 5.

[A] Hugging Face — litert-community/embeddinggemma-2-740m-litert-lm model card (as fetched on 2026-10-08)

https://huggingface.co/litert-community/embeddinggemma-2-740m-litert-lm

Three LiteRT-LM packages: Text 270M, Text Vision 440M and the full 740M, the last two with on-demand modality loading.
Quantization (all QAT, per-channel): transformer and embeddings int4, vision encoder int8, audio encoder "mixed int2/int4/int8".
Download size (CPU/GPU file): 165 MB, 388 MB and 485 MB.
Supported inputs: text tokens 128, 256, 512, 1024, 2048 and 8192; image soft tokens 70 and 140; audio soft tokens 12.
Outputs: 128 (512 bytes), 256 (1024 bytes), 512 (2048 bytes) and 768 (3072 bytes).
Method: the 128 text signature and the 70 vision signature, a 10-second audio file for text + audio and a 5-second one for all three, latency averaged over 5 iterations, and memory from the second load.
- "Memory was measured with each platform's native metrics and is not directly comparable across operating systems."
- Accelerator (GPU/NPU/TPU) memory is not included, except under task_vm_info::phys_footprint on iOS and macOS.
Each device line gives latency for text, text + vision, text + audio and text + vision + audio, then memory in the same order:
- Google Pixel 11 Pro (TPU): 8.3, 49, 193.5 and 149 ms; 112, 125, 121 and 127.5 MB.
- S26 Ultra (CPU): 27.1, 175, 305 and 322 ms; 334, 694, 465 and 811 MB.
- S26 Ultra (GPU): 25.9, 119, 350 and 324 ms; 333, 427, 407 and 493 MB.
- iPhone 18 Pro (CPU): 41.8, 191, 445 and 400 ms; 84, 196, 98 and 196 MB.
- iPhone 18 Pro (GPU): 11.6, 69.8, 165 and 150 ms; 85, 196, 96 and 226 MB.
- Linux, Arm 2.3 & 2.8GHz (CPU): 105, 825, 947 and 1251 ms; 310, 647, 431 and 764 MB.
- NVIDIA GeForce RTX 4090 (GPU): 7.6, 23.9, 169 and 112 ms; 528, 678, 654 and 811 MB.
- MacBook Pro M5 (CPU): 31.3, 151, 314 and 432 ms; 165, 310, 201 and 336 MB.
- MacBook Pro M5 (GPU): 9.5, 37.3, 195 and 131 ms; 233, 403, 320 and 478 MB.
- Dell XPS 16, Intel Core Ultra Series 3 (CPU): 71.7, 338, 813 and 708 ms; 211, 342, 242 and 369 MB.
- Dell XPS 16 (GPU): 19.2, 62.5, 284 and 205 ms; 822, 1769, 1047 and 1962 MB.
- Dell XPS 16 (Intel OpenVINO NPU): 13.3, 49.8, 124.3 and 108.6 ms; 201, 394, 288 and 503 MB.
- Web on a MacBook Pro M5 (GPU): 21.8, 107, 228 and 226 ms.
- Raspberry Pi 5 16GB (CPU): 161, 1761, 946 and 2304 ms; 282, 619, 408 and 736 MB.
- Jetson Orin Nano (CPU): 207, 1741, 1659 and 2507 ms; 302, 627, 417 and 741 MB.
- Jetson Orin Nano (GPU): 88, 485, 1195 and 1069 ms; 523, 1103, 755 and 1228 MB.
- Arduino VENTUNO Q (NPU): 13.6 and 135 ms for text and text + vision, 206 and 460 MB; audio is not supported on the IQ-8275 NPU.
LiteRT-LM "automatically scales and patchifies images of any size" and supports streamed audio of varying length.
"Downloads last month 8,037".

[A] Qdrant — How Small Can Google's New EmbeddingGemma 2 Get? (2026-10-06)

https://qdrant.tech/blog/embeddinggemma-2/

Qdrant is a launch partner named in Google's post: "We got early access ahead of today's Google DeepMind release and tested how much of that memory we could save in Qdrant."
"At 10 million documents, full-size float32 vectors alone take 30.7 GB of RAM."
"Quantized full-size vectors kept 99% of their retrieval quality with 30x less vector RAM."
- "Shorter vectors with rescoring reached 77x less vector RAM and retained 94.5%."
Method: five text retrieval datasets compared with exact search over full-size float32 vectors, quality as the share of the baseline's nDCG@10 retained, rescoring with 4x oversampling, and vector RAM excluding graph indexes, payloads and stored originals.
Recommended start: all 768 dimensions, 1-bit TurboQuant, rescoring off, so "Each vector takes 104 bytes instead of 3,072", about 1 GB of RAM for 10 million documents.
- "On Quora's 523k documents, this setup took less than half the query time of float32 search and retained 99.0% of its retrieval quality."
- "Without rescoring, about 74% of the top 10 results matched exact search."
"Cutting dimensions feels like the obvious way to save memory."
- "In these tests, we'd cut bits first."
- "At 72 bytes per vector, 512 dimensions at 1 bit kept 97.3% of the baseline."
- "At a similar memory budget, the 128-dimensional, 4-bit setup kept 84.0%."
At 256 dimensions with 1-bit TurboQuant, each vector takes 40 bytes; retention was 94.5% with rescoring and 88.1% without.
Storing originals as float16 or turbo4 was not tried, and all results cover text retrieval only.

[A] Unsloth — EmbeddingGemma 2 - Run Locally (as fetched on 2026-10-08)

https://unsloth.ai/docs/models/embeddinggemma-2

The page showed "Last updated 1 day ago".
Recommended settings: BF16 on supported hardware or FP32 elsewhere, start with 768 dimensions, use 512 or 256 to save storage and evaluate 128 for text, and L2-normalize vectors after truncation.
- "Do not use FP16."
- "EmbeddingGemma 2 can produce NaN or degraded embeddings in FP16."
Unsloth Desktop: choose EmbeddingGemma 2 under Settings → General → Documents & RAG.
- "Changing the embedding model only affects newly indexed documents."
- "Re-upload existing documents to use the new model."
Colab notebooks cover multimodal search and text, image-text and audio fine-tuning (file names EmbeddingGemma2_(300M)).
llama.cpp needs a build with EmbeddingGemma 2 support (PR #30054), and Unsloth's 176 MB UD-Q4_K_XL GGUF serves text and code embeddings from a 2,048-token context.
- For longer inputs, raise --ctx-size, --batch-size and --ubatch-size together up to 8192; "Each input must fit in a single physical batch."
- "Add the task prefixes yourself when calling the API."
- "Check that each vector has 768 finite values before building your index."
- "For images, video or audio, use a runtime with explicit support for those encoders and their processor files."
- "The command above covers text embeddings."
Fine-tuning: load the saved text model in 4-bit with LoRA adapters, train with SentenceTransformerTrainer and MultipleNegativesRankingLoss, set bf16=True and fp16=False, and test on held-out queries.
- "Training on images, video or audio requires a separate workflow."
- The embedding fine-tuning guide's notebook still covers the earlier EmbeddingGemma 300M.

[A] Ollama — embeddinggemma-2 library page (as fetched on 2026-10-08)

https://ollama.com/library/embeddinggemma-2

"10.8K Downloads Updated yesterday", with 17 models in the tag list.
Tags: 270m 378MB (input Text), 440m 714MB (Text, Image), 570m 990MB (Text), and 740m, the latest, 1.3GB (Text, Image).
Every tag lists a "256K context window".
Usage: ollama pull embeddinggemma-2 and the /api/embed endpoint; the readme reproduces the model card.

[A] ggml-org — llama.cpp pull request #30054, model: support embeddinggemma2 (text+vision+audio) (2026-10-06)

https://github.com/ggml-org/llama.cpp/pull/30054

Opened by Xuan-Son Nguyen (ngxson) at 2026-10-06T16:02:55Z and merged at 16:20:31Z, with 324 additions and 2 deletions (read with gh).

[A] ggml-org — embeddinggemma-2-GGUF on Hugging Face (as fetched on 2026-10-08)

https://huggingface.co/ggml-org/embeddinggemma-2-GGUF

Run with llama serve -hf ggml-org/embeddinggemma-2-GGUF; "automatically converted using https://github.com/ggml-org/convert".
Model size "0.3B params", architecture gemma-embedding2, 8-bit and 16-bit files, 3,842 downloads last month.

[B] Latent Space (AINews) — [AINews] Quasi-Riemann-Hypothesis: OpenAI publishes 722 math papers solving 90 of the top 500 open math problems, EmbeddingGemma 2 item (2026-10-07)

https://www.latent.space/p/ainews-quasi-riemann-hypothesis-openai

Filed under "Open-Weight and API Model Releases: Embeddings, Image, Decision Models" as "Google's first natively multimodal open embedding model".
Specs, citing Phil Schmid: "740M omni, 440M text+vision, 570M text+audio and 270M text-only variants", Matryoshka dimensions from 768 to 128, 8,192 context and "a reported +14% on MTEB Code".
"Day-0 support covers llama.cpp, vLLM, Ollama and Unsloth."
- "It also runs in the browser on WebGPU at ~20–70ms per query", citing a post by victormustar.
Among the day's top tweets by engagement, "Sundar Pichai introduces EmbeddingGemma 2" ranked third with 7.1K.
The r/LocalLLaMA post "google/embeddinggemma-2 · Hugging Face" had Activity 543; comments were "mostly light", with surprise at another Google embedding model and at audio embeddings.
- One commenter objected that community posts linked to Unsloth conversions rather than Google's model page.
The rest of the issue sits behind a paid wall.

[B] The Next Web — Google launches EmbeddingGemma 2, an open multimodal embedding model for devices (2026-10-06)

https://thenextweb.com/news/embeddinggemma-2-on-device-europe

Subhead: Apache 2.0 and about 191MB of RAM for text-only work on a Pixel 11 Pro "puts multimodal retrieval on hardware a European company already owns".
"It is licensed under Apache 2.0, has had no safety tuning, and Google says performance is not equal across the 100 languages it supports."
"Nothing has to leave the device."
An embedding model "turns content into numbers so software can find things by meaning rather than by matching words", and "That is the step that normally happens in somebody else's cloud."
It recalls Gemma 4 arriving in April "as four open-weight models under the same licence" and Google's August offline translator on an $80 Raspberry Pi.
"Keeping the data on the device avoids the transfer, which is where most European data protection questions begin."
"The company is not doing this out of generosity."
- "It is building the default."
The Gemma family has passed "a billion downloads", 20 million of them for the first EmbeddingGemma.
On the language caveat: "The EU has 24 official languages."

[B] 窓の杜 (Impress) — Google DeepMind announces EmbeddingGemma 2, an open embedding model that handles text through video, by 樽井秀人 (2026-10-07, in Japanese)

https://forest.watch.impress.co.jp/docs/news/2146193.html

Published 2026-10-07 08:05 JST, with the subhead that the 740M-parameter model runs on device even on smartphones.
Framing: a single model replaces pipelines that chained an image model for captions, a speech model for transcription and a text embedding model, for example for video search, promising lower latency, lower memory use and simpler implementation.
It restates 270M for text with 170M vision and 300M audio encoders added as needed, and the Pixel 11 Pro figures (about 191MB text-only, about 567MB in total).
On MRL it adds the caveat that shortening can lower accuracy and that 128 dimensions suits mainly text-only use, while storage drops to at most one sixth.
The 8K window is four times EmbeddingGemma's; under default settings it takes up to about 5.5 minutes of audio, about 29 images or about 58 frames, and mixed inputs share the 8K budget.
It shows Google's chart of MTEB Code mean score against model size, labelled as Google-published.
Availability: Hugging Face and Kaggle now, Model Garden in Gemini Enterprise Agent Platform soon, support in Ollama and LM Studio, and ML Kit on Android in the coming weeks.

[B] ビジネス+IT (SB Creative) — Google releases EmbeddingGemma 2, an embedding AI that also handles audio and video and runs on device (2026-10-07, in Japanese)

https://www.sbbit.jp/article/cont1/187318

Published 2026-10-07 03:28 JST and syndicated to Yahoo! News Japan.
Lead: quantized, it runs in about 567MB of memory on a smartphone.
It restates the model card: 270M text plus 170M image and 300M audio encoders, 768 dimensions cut by MRL to 512, 256 or 128, and 128 dimensions reducing local vector database storage to at most one sixth.
It gives MTEB Code rising from 68.76 to 78.68 (9.92 points) and attributes the best-in-class claim on MAEB to Google.
It lists transformers, sentence-transformers, MLX, vLLM, llama.cpp, SGLang, Ollama and LM Studio for inference, Qdrant for storage and Unsloth for fine-tuning, and dates the first EmbeddingGemma to September 2025 with more than 20 million downloads.
It asks why Google released a small on-device open model when it already has a cloud multimodal embedding model, pointing to a competing model Cohere put out at the end of September and to how the model card's numbers should be read.
A chart compares cloud and open embedding models, built from Google's and Cohere's announcements.
The continuation (how to split work with the cloud Gemini Embedding 2, Cohere Embed 5's competing benchmarks, why the numbers cannot be lined up, and measured speed on real devices) is for registered members and was not read.

[B] GIGAZINE — Google's embedding model EmbeddingGemma 2 arrives, using as little as about 191MB of RAM and running on smartphones (2026-10-07, in Japanese)

https://gigazine.net/news/20261007-google-embeddinggemma-2/

Posted 2026-10-07 13:47 JST by log1p_kr, mostly restating the blog and embedding Google's posts on X.
Google on X: "We're releasing EmbeddingGemma 2, our first natively multimodal open model engineered for on-device embeddings."
Google on X: "Best-in-class for its size at 740M parameters, EmbeddingGemma 2 outperforms some models over twice its size while using from as little as ~191MB to 567MB of active RAM."
It writes the best-in-class claim as covering MTEB and MAEB, without the blog's "Code".
It restates the MRL reduction to one sixth for the local vector database and memory, the Pixel 11 Pro figures, the 8K window (4x) and the 5.5 minutes, 29 images and 58 frames.
Weights are on Hugging Face and Kaggle, with Model Garden in Gemini Enterprise Agent Platform to follow, and the first EmbeddingGemma (September 2025) has passed 20 million downloads.

[B] DevelopersIO (Classmethod) — Embedding images with embeddinggemma-2, by 夏目祐樹 (2026-10-07, in Japanese)

https://dev.classmethod.jp/articles/embeddinggemma-2-image-embedding/

The author, from Classmethod's information systems office, tried image search on a Mac with an M5 chip.
Setup: uv init --python 3.14 --bare and uv add sentence-transformers transformers, as in the model card's Quick Start.
The Quick Start failed with transformers 5.18.0: "ValueError: The checkpoint you are trying to load has model type embedding_gemma2 but Transformers does not recognize this architecture."
Installing transformers from GitHub main (5.19.0.dev0, commit e598fbad) led to "ImportError: EmbeddingGemma2Processor requires the PIL library", fixed with sentence-transformers[image] (pillow 12.3.0, torchvision 0.29.1).
The Quick Start then printed a similarity of 0.8713, and model.encode({"image": ...}) returned a float32 NumPy array of shape (768,).
Three ChatGPT-generated images (a chihuahua, three miniature dachshunds, a cat) were scored with encode_query and encode_document, in that order:
- "search dog image": 0.7282, 0.7152, 0.6756.
- "search cat image": 0.6501, 0.6378, 0.7434.
- "search dachshund": 0.6954, 0.7960, 0.6614.
- "search flying birds", which matches none: 0.6110, 0.6133, 0.6200.
- Japanese "犬の画像はどれ？" (which is the dog image?): 0.7128, 0.6913, 0.6457.
- Japanese "猫の画像はどれ？" (which is the cat image?): 0.6171, 0.5978, 0.7126.
- Japanese "ミニチュアダックスフンドの画像はどれ？" (which is the miniature dachshund image?): 0.6592, 0.6875, 0.5948.
The author reads it as mostly telling the images apart in English and Japanese, with about 0.7 acting as a threshold with exceptions, and some results hard to read from similarity alone.
Amazon S3 Vectors: a vector bucket and an index (float32, dimension 768, cosine) created with the AWS CLI in ap-northeast-1, the three image vectors put with boto3, and queries with topK 3 and returnDistance.
- "search dog image" returned distances 0.2718, 0.2848 and 0.3244 in the same order.
- The author finds distances below about 0.3 close, notes an oddly large distance only for the Japanese miniature dachshund query (0.3125 for the dachshund image), and finds distances easier to read than similarities.

[C] Hacker News — EmbeddingGemma 2: An open, lightweight multimodal embedding model (2026-10-06, 415 points, 46 comments)

https://news.ycombinator.com/item?id=49980487

415 points and 46 comments when fetched at 10:20 JST on 2026-10-08, linking the blog.google post.
simonw: "I really appreciate that EmbeddingGemma 2 is under the Apache 2.0 license."
- "For embedding models in particular, I don't think it makes sense to use a closed, proprietary, hosted-only model."
- If a proprietary model is withdrawn, "you still need to pay to re-calculate those millions of stored existing vectors", and OpenAI's April 2024 offer to cover re-embedding costs is not something to rely on from every provider.
- "I'd much rather pay a provider for a hosted model while knowing that if they ever stop hosting it I can run the open weights version myself".
weitendorf: embedding models are among the most likely to be self-hosted, since "You can just rent a GPU for $1-2/hr" and run over a whole dataset.
On CPU against GPU drift, slickytail: "You don't care about bit for bit equality, just the distance in embedding space."
Zambyte ran the MediaPipe decision example locally: "Cancel my flight and refund my credit card immediately." was judged not financial with p(true) 0.22, and "Laya was significantly more accurate (in this case) and almost as fast."
minimaxir: "there hasn't been a good moderate-size embeddings model, and this one is multimodal too! 270M for text only is great compared to older embedding models, and a total 440M for text + vision is also fair."
- On an M3 Pro with his own tool: text 78 embeddings per second on small texts, images 4 per second, audio 6 per second for 30-second chunks, and video 0.2 embeddings per second per minute of video.
jraedisch: "First (Claude based) testing confirms not better or faster if one only needs text embeddings for retrieval or clustering."
- For music audio, MuQ-MuLan "seems to remain the way to go".
sourcecodeplz: "for text, benchmarks are identical to the first EmbeddingGemma."
aabhay: it is "trained with MRL, not MatFormers, meaning you don't get to shrink the model weights alongside the lower dimensional embeddings".
weitendorf reads the model card's audio data (speech, environmental sounds, "acoustic events") as suggesting audio is encoded mostly into transcribed language and labels.
kaycebasques asks whether binary quantization would work instead of MRL, and the thread gives no answer.
Comparisons asked for: Voyage AI's models for text (dcl, disputed by nostrebored and redwood) and SigLIP2 (brokensegue).
piyh runs offmetaedh.com on these models and calls this one "a drop in replacement for gemma embedding v1 and HQ-CLIP."
- "Better quality, less RAM usage, faster embeddings".
circularfoyers calls the image search in the Edge Gallery app "really incredible".
anyg: the decisions API is "buried" as the third example and "may gain more traction if they lead with multimodal input decision making."
treetalker and ahknight describe searching a legal case file for deposition testimony and photographs together.
A user named sahil2305dua replied to a joke about the release timing with "Yeah, that was too much to handle for us :D".

[C] HyperAI — Google Launches EmbeddingGemma 2 for Lightweight On-Device Multimodal Tasks (2026-10-07)

https://hyper.ai/en/stories/2b394de14f674391a50cdff9ca17b08c

The page states: "This news is intelligently aggregated by AI to deliver industry updates efficiently."
It restates the blog's figures (740M, about 191 and 567 megabytes, 9.92 points on MTEB Code, 8K context).
It says MRL "cuts local vector database storage requirements by up to six times without compromising retrieval precision".

Notes

The storage factor differs across Google's own pages: the DeepMind post, the model card, the docs and the developer guide say up to 6x (768 to 128 dimensions, the 1:6 row of the table), while the AI Edge post says MRL cuts "local storage and index footprints by up to 8x" without explaining the extra factor.
The code gain is the same result in two units: 9.92 points absolute (68.76 to 78.68) in the blog and "~14%" relative in the model card and guide (78.68 / 68.76 ≈ 1.144).
Text quality is flat: MTEB multilingual v2 moves from 61.15 to 61.36, and two HN users say text-only retrieval is not better; for text-only teams the gains are code retrieval and a smaller text path (270M against 308M).
- The docs page says the base text model shrank "from 300M" while describing EmbeddingGemma 1 as 308M on the same page.
The best-in-class claims ("leading scores among sub-1B multimodal embedders", outperforming "specialist models more than twice its size") come without competitor scores in any Google page read; the model card compares only with EmbeddingGemma 1.
- 窓の杜 reproduces Google's own chart of MTEB Code against size; HN asks for SigLIP2 and Voyage comparisons; ビジネス+IT's comparison with Cohere Embed 5 and Gemini Embedding 2 is behind a member login and was not read.
- No independent benchmark was found; the Japanese and English media read restate vendor numbers, and the Classmethod test is a three-image check.
The guide's retention percentages roughly match the truncation table: at 128d MMEB v2 keeps 77% and MSEB 82% of the 768d score (the guide says about 75%), while MIEB lite keeps 91% and MAEB 95%; text and code keep 94% and 91%; at 256d the image, video and audio benchmarks keep 95% to 99%.
Memory figures come from different methods and should not be set side by side: the blog's "~191MB" and "~567MB" active RAM on a Pixel 11 Pro against the LiteRT card's 112 to 127.5 MB CPU memory on the Pixel 11 Pro TPU, which excludes accelerator memory.
The AI Edge post's 37.3 ms on a "MacBook M5 Pro GPU" matches the LiteRT card's text + vision figure on a "MacBook Pro M5" GPU; the device naming differs.
Ollama's tags list a "256K context window" for every size and input "Text, Image" (the 570m tag only "Text"), which conflicts with the model card's 8,192 tokens and audio support; it may be metadata carried over from Gemma 4, whose banner on ai.google.dev mentions up to 256K (unverified), so audio through Ollama needs checking.
llama.cpp PR #30054 is titled text+vision+audio, but the ggml-org GGUF shows 0.3B parameters and Unsloth says its llama.cpp command covers text embeddings only; whether vision and audio work in llama.cpp was not checked.
Library readiness on 2026-10-07: the Classmethod test needed transformers from GitHub main because 5.18.0 did not know embedding_gemma2, the guide requires sentence-transformers 6.1.0 or later with the [image,audio,video] extras, and the model card's Quick Start installs neither; whether a transformers release with support has shipped since was not checked.
MLX links differ: the DeepMind post points to Blaizzy/mlx-vlm and the developer guide to ml-explore/mlx-lm.
Availability still pending: Model Garden in Gemini Enterprise Agent Platform is "coming soon" (the platform's release notes saved in this run have no EmbeddingGemma 2 entry), and ML Kit on Android comes "in the coming weeks".
The model has no post-training alignment, safety tuning or output moderation, and Google puts retrieval filtering and fairness testing on deployers; The Next Web leads with this.
Languages: "100+ languages" supported against "over 140 languages" in the training web text, with unequal performance acknowledged; no Japanese-specific score appears in the pages read, and the Classmethod test ranked images correctly for Japanese queries.
Zambyte's failed routing example (p(true) 0.22) is one anecdote; the "Laya" model it was compared with appears in Unsloth's navigation as a decision model and was not investigated.
Qdrant and Unsloth are partners named in Google's post, and Qdrant had early access; their posts are vendor measurements, not independent evaluations, and Qdrant's cover text retrieval on five datasets of which only Quora is named.
Whether HN user sahil2305dua is the co-author Sahil Dua is unverified.
Engagement recorded: HN 415 points and 46 comments; AINews reports 7.1K engagement on Sundar Pichai's post and Activity 543 on r/LocalLLaMA; Hugging Face showed 7,562 downloads, Ollama 10.8K and the LiteRT package 8,037.
The Kaggle model page rendered only its title in the page cache and in WebFetch, so Kaggle availability rests on Google's post and the Japanese media.

Ideas for practice and output

Code retrieval on the team's own repository: index it with the 270M text-only setup and the CodeRetrieval prompt (title: {filename} | text: {code}), ask 30 to 50 real developer questions, and compare recall@10 and indexing time with the current embedding model at 768d and 256d.
- It checks whether the MTEB Code gain holds on the team's code and whether it is worth wiring into a coding agent's retrieval tool.
Japanese text: since text scores barely moved from EmbeddingGemma 1, measure Japanese retrieval on an internal FAQ or ticket set across EmbeddingGemma 1, EmbeddingGemma 2 and the hosted model in use, including 128d.
Multimodal RAG spike: index slide decks and PDFs as images plus meeting recordings with the 440M or 740M setup in SQLite, Qdrant or S3 Vectors, query in text, and record memory and latency on a developer laptop against the LiteRT figures.
Vector storage: reproduce Qdrant's comparison on the team's own store (768d at 1 bit, 256d at 1 bit with rescoring, 128d at 4 bits), measuring nDCG@10 retention and top-10 overlap with exact search.
Adoption checklist: pin transformers and sentence-transformers (6.1.0 or later), force bfloat16 or float32 and never float16, re-normalize after truncation, keep query and document dimensions equal, and assert 768 finite values before indexing.
Zero-shot routing: score the MediaPipe Decision Task, or plain label-embedding similarity, against an LLM classifier on a labelled set of agent or support intents, including the failure shown on HN.
Decision record: compare a hosted embedding API with self-hosted open weights for the team's corpus, with a re-embedding cost estimate for the day a hosted model is retired, the argument simonw makes.
Output: a short write-up or LT on EmbeddingGemma 1 against 2 for Japanese text and code, with the library pitfalls found during setup.

6. 📚 LayerX described how it keeps an organisation-wide LLM Wiki from going stale as it heads past 1,000 pages: daily diffs filtered by whether they change the answer to a likely question, source hashes checked by a lint before every push, and answers written back through a staging area that a separate agent promotes

Selected / impact 1 / potential 1 / attention 2 / anchor 10-05, before the window / kind: hands-on / areas: agent building, evals and operations.
Feed items in this topic:
- hatena-llm 10-06 LLM Wikiの組織運用に向けて ── 陳腐化を防ぐ更新の仕組み - LayerX エンジニアブログ (towards running an LLM Wiki across an organisation: an update mechanism that keeps it from going stale) — 100 Hatena Bookmark users when fetched
Anchor: LayerX published the post on 10-05, a day before the window, and hatena-llm brought it to the feeds on 10-06.

Collected information

[A] LayerX Engineering Blog — Toward running an LLM Wiki across an organisation: an update mechanism that keeps it from going stale, by shibutani (2026-10-05, in Japanese)

https://tech.layerx.co.jp/entry/enterprise-llm-wiki-ops

The author, shibutani, is in the Enabling group of the Platform Engineering department in LayerX's Bakuraku (バクラク) business division; the post is dated 2026-10-05.
The question "how does this feature actually work?" comes up daily, when QA writes the expected results of tests and when CS answers customer inquiries.
The answers sit in three places, design specs in Notion, help articles in Zendesk and code in GitHub, and their descriptions often disagree.
LayerX built an LLM Wiki as the Single Source of Truth for product-spec context: the three sources are reconciled and gathered in one place, so that people and LLMs alike look there first.
What operation taught them: the hard part is not writing but keeping what was written correct, because the sources are updated daily and the wiki starts going stale the moment it is written.
Why none of the three can be trusted alone:
- Design specs show the design intent, but they describe the design at the time of writing, with no guarantee that it matches current behaviour.
- Help articles explain what customers see, but many patterns are not covered and revisions sometimes lag the implementation.
- Code is the actual behaviour, but few people can read it and the implementation itself may be wrong.
Handing the three to an LLM as they are solves nothing, because the LLM cannot decide which one is right when they conflict; the author judged that organising the context beforehand works better than a stronger model.
Who gains from one reconciled place:
- QA can write expected results against a spec that reflects both code and design, which is what finding deviations from the spec (bugs) requires, since code alone cannot show whether behaviour is as intended.
- CS can tell quickly, without reading code, whether a reported behaviour is per spec or a defect.
- Setting help articles next to the implementation exposes mistakes and outdated text in what customers are told.
LLM Wiki is introduced as a knowledge-management pattern proposed by Andrej Karpathy: instead of people writing the wiki, an LLM reads the primary sources, writes the wiki, and grows it each time it answers a question.
Page structure: one feature per page, with what the design spec, the help article and the code each say set side by side.
Scale: around 100 pages per product, expected to pass 1,000 pages across Bakuraku's products.
In Japan, trials of LLM Wiki are increasing, but cases run continuously and at scale by an organisation are still few, in the author's view.
With personal knowledge such as papers and notes, sources are only added and past content is rarely rewritten; with an organisation's specs at this scale, help articles are revised and code ships regularly, so the sources themselves keep changing.
The most recent release alone contained more than 2,000 pull requests.
A wiki that is written and left returns outdated answers plausibly, so organisational use needs a mechanism that keeps following the changes in its sources.
Device 1, regular updates (定期更新): changes land in the sources almost every day, and descriptions of new features and changed behaviour arrive through them, so what the wiki must reflect has to be found daily.
- Most changes are refactoring or internal reorganisation that do not touch what wiki users want to know.
- Having an LLM read every diff to decide whether to reflect it makes the cost proportional to the volume of diffs, most of it spent on changes irrelevant to users.
The starting point of the judgement moved from "what changed in the source" to "does the answer to a user's question change", because the wiki's value lies in whether it answers users' questions correctly.
The regular update re-fetches the three sources, diffs them against the previous run and groups the diffs by product; code diffs are further grouped by pull request.
- Files changed in one pull request are parts of one change, so judging what a change means to users is easier per pull request than per file.
For each grouped diff, the LLM writes one question a user would likely ask about the change (想定質問).
When no question can be written, as with internal reorganisation, typo fixes or replaced screenshots, nothing is done, on the view that the wiki has nothing to say about it either; most diffs are dropped at this stage.
When a question is written, the current wiki is made to answer it:
- If the answer matches the updated sources, nothing is done.
- If they disagree, that section is fixed.
- If the wiki cannot answer, a section is added or a new page is created.
A flowchart in the post shows the path: re-fetch the sources, group diffs by product and pull request, ask whether a likely question can be written, then compare the wiki's answer with the updated sources and do nothing, fix the section, or add a section or page.
With this, the LLM reads in detail only the changes that could change an answer for users.
Device 2, mechanical detection of degradation (劣化の機械的な検知): question-based selection leaves the decision to pick up a diff to the LLM, so when a source behind an existing page changes and the LLM judges that users' answers do not change, the page stays out of date.
- Pages whose grounds changed must therefore be re-read with no LLM judgement in between.
Each page lists every source it is based on and records a hash of each source's content; when a source changes, the hash no longer matches and the page is judged stale without any LLM judgement.
Pages written from other wiki pages are tied the same way: fixing page A after a source update changes the hash of A's body, which then marks page B, written from A, as stale.
- The judgement travels downstream one level at a time and repeats until no stale page remains, as a second diagram shows.
Code is cited pinned to the version released to production, because help articles describe production behaviour and the reconciliation only holds on the same version.
- Questions about behaviour in development or staging environments are answered by reading that environment's code directly, not the wiki.
Detection is useless unless the comparison actually runs, so the hash comparison is implemented as a lint, and every wiki change must pass it before it is pushed.
- If even one page judged stale remains, the lint fails and the push cannot proceed.
- All wiki updates, the regular update included, go through this procedure, so a page whose sources changed is always re-read and fixed before it reaches the wiki.
Device 3, protecting the wiki from many people's write-backs (多人数の書き戻しからwikiを守る仕組み): an LLM Wiki grows by writing answers back into it, but if users rewrite the wiki directly from their own agents, it drifts with each person's preferences and the habits of each agent.
- The more users, the more the writing style and the judgement criteria diverge, and the wiki loses consistency.
Write-back is therefore limited to a staging area (一時置き場): users' agents do not rewrite the wiki itself and leave their answers as they are in the staging area.
The daily regular update reads the staging area and, following predefined rules (規約), decides whether to promote each answer to a feature page or delete it.
- When an answer is promoted, an agent other than the one that wrote it checks it against the sources.
- Content in the staging area is never used as grounds for the next answer, because grounding on unchecked answers would carry errors into later answers.
The post's third diagram: a user's question, an answer from the wiki, the answer left in the staging area with the wiki untouched, a judgement by the regular update under the rules, then promotion to the matching feature page if it fits or deletion if it is wrong or weakly grounded.
As a result, whoever asks with whatever agent, the wiki keeps being updated only along the predefined rules, keeping both the insight gained from answers and the wiki's consistency.
Next steps: today's sources are design specs, help articles and code, and LayerX wants to add Slack discussions and the content of real customer inquiries, where the history of spec decisions and the points customers actually stumble on are recorded.
- Unlike code and help articles, these have viewing permissions that differ by person, so gathering them into one wiki needs a mechanism that handles those differences.
The closing summary lists three points: regular updates reflect only diffs whose likely user question gets a different answer; pages whose grounds changed are detected mechanically by hash and cannot be reflected until re-read; write-backs pass through a staging area and are promoted under the rules.
The author's conclusion: a system in which an LLM writes knowledge is now easy to build, but running it in an organisation requires noticing that written knowledge has gone stale, deciding what not to write, and having the same rules govern updates whoever uses it.

[A] Andrej Karpathy — llm-wiki.md, GitHub gist (2026-04-04, background)

https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f

The gist shows "Created April 4, 2026", with Star (5,000+) and Fork (5,000+) when fetched on 2026-10-08.
"A pattern for building personal knowledge bases using LLMs."
"This is an idea file, it is designed to be copy pasted to your own LLM Agent (e.g. OpenAI Codex, Claude Code, OpenCode / Pi, or etc.)."
With RAG, "the LLM is rediscovering knowledge from scratch on every question."
- "There's no accumulation."
Instead, "the LLM incrementally builds and maintains a persistent wiki — a structured, interlinked collection of markdown files that sits between you and the raw sources."
"The knowledge is compiled once and then kept current, not re-derived on every query."
"You never (or rarely) write the wiki yourself — the LLM writes and maintains all of it."
"Obsidian is the IDE; the LLM is the programmer; the wiki is the codebase."
Business and team use: "an internal wiki maintained by LLMs, fed by Slack threads, meeting transcripts, project documents, customer calls."
- "Possibly with humans in the loop reviewing updates."
Raw sources: "These are immutable — the LLM reads from them but never modifies them."
- "This is your source of truth."
The wiki: "The LLM owns this layer entirely."
The schema, "(e.g. CLAUDE.md for Claude Code or AGENTS.md for Codex)", is "what makes the LLM a disciplined wiki maintainer rather than a generic chatbot."
Ingest: "A single source might touch 10-15 wiki pages."
- Karpathy prefers to ingest sources one at a time and stay involved, though batch ingests are possible "with less supervision".
Query: "good answers can be filed back into the wiki as new pages."
Lint: "Look for: contradictions between pages, stale claims that newer sources have superseded, orphan pages with no inbound links, important concepts mentioned but lacking their own page, missing cross-references, data gaps that could be filled with a web search."
index.md "works surprisingly well at moderate scale (~100 sources, ~hundreds of pages) and avoids the need for embedding-based RAG infrastructure."
log.md is "an append-only record of what happened and when — ingests, queries, lint passes."
For larger wikis it suggests qmd, "a local search engine for markdown files with hybrid BM25/vector search and LLM re-ranking", with a CLI and an MCP server.
"The wiki is just a git repo of markdown files."
"Humans abandon wikis because the maintenance burden grows faster than the value."
- "LLMs don't get bored, don't forget to update a cross-reference, and can touch 15 files in one pass."
"This document is intentionally abstract."
- "It describes the idea, not a specific implementation."

[A] arXiv — LLMs Corrupt Your Documents When You Delegate, by Philippe Laban, Tobias Schnabel and Jennifer Neville (2026-04-17, background)

https://arxiv.org/abs/2604.15597

Submitted on 17 Apr 2026 (v1), in Computation and Language and Human-Computer Interaction; only the abstract page was read.
"Delegation requires trust - the expectation that the LLM will faithfully execute the task without introducing errors into documents."
"DELEGATE-52 simulates long delegated workflows that require in-depth document editing across 52 professional domains, such as coding, crystallography, and music notation."
"Our large-scale experiment with 19 LLMs reveals that current models degrade documents during delegation: even frontier models (Gemini 3.1 Pro, Claude 4.6 Opus, GPT 5.4) corrupt an average of 25% of document content by the end of long workflows, with other models failing more severely."
"Additional experiments reveal that agentic tool use does not improve performance on DELEGATE-52, and that degradation severity is exacerbated by document size, length of interaction, or presence of distractor files."
"Our analysis shows that current LLMs are unreliable delegates: they introduce sparse but severe errors that silently corrupt documents, compounding over long interaction."

[B] Cornell AI Innovation Hub — Teaching an AI to Remember: What I Learned Building a Wiki LLM, by Ido Efrati (2026-09-01, background)

https://innovationhub.ai.cornell.edu/articles/teaching-an-ai-to-remember-what-i-learned-building-a-wiki-llm/

The author is a Programming Analyst Specialist; the page metadata dates it 2026-09-01.
He built an LLM wiki on Karpathy's pattern and tested it on The Hound of the Baskervilles, a public-domain novel with a plot twist, "to find the rough edges without risking proprietary knowledge".
He frames the stakes for teams: asking "your own team's agent why a specific requirement went into the spec six months ago, and getting an answer instead of a shrug."
RAG is right for "fact lookup over a huge, constantly changing corpus (customer support tickets, legal filings, enterprise knowledge bases)", while every query re-derives the picture from scratch.
His setup keeps raw sources, the wiki and the schema separate, with skills /llm-wiki-ingest, /llm-wiki-query, /llm-wiki-lint and /llm-wiki-maintain.
- "None of this is complicated."
- "The intelligence isn't the trick here, the bookkeeping discipline is."
At chapter 13 the wiki cleared the butler on his page and rewrote the pages on Stapleton and on the L.L. letter, "conclusions rewritten in place, not new pages arguing with old ones", so the reconciliation "happened once, at ingest".
"What actually made it trustworthy enough to rely on were the deterministic pieces underneath the AI's judgment calls."
His wiki_tool.py CLI has build and lint commands, and "source-scan and source-lint hash every raw source file and flag it if a page cites a source that's since changed".
- A run printed "OK - 23 concept(s) valid", "Manifest updated - 0 new, 0 changed, 15 total" and "OK - 15 source(s) checked", plus three orphan-page warnings.
- "It's a tool the AI is required to run, and it's what actually catches drift."
Pages follow OKF, the Open Knowledge Format that Google's Data Cloud team published, with required fields (type, title, last-updated date) and a restricted vocabulary of five page types for the novel.
- A new type is added only "after three pages don't fit".
"Reach for a wiki when you have a bounded, curated set of sources (a few hundred, not a few million) and the valuable answers require connecting five of them".
Trade-offs he did not expect:
- Scale: the index has to fit in a context window, "on the order of a couple hundred pages before you need a retrieval layer anyway".
- "It assumes one writer at a time."
- "There's no access control and no transaction model."
- "A wrong inference can get treated as settled."
- "The immutable raw-source layer is the safety net; it's not a substitute for actually checking."
- "A weaker model propagates weaker judgment straight into the knowledge base."
Next, he would build "a team version: fed by Slack threads, meeting notes, or ticket exports", and a hybrid with a search layer once the index outgrows a context window.

[B] DevelopersIO (Classmethod) — What happens when you leave document maintenance to an LLM: a paper, by 森茂洋 (Hiroshi Morishige) (2026-05-08, in Japanese, background)

https://dev.classmethod.jp/articles/llm-knowledge-base-document-corruption-revisit/

The author follows up his earlier post on Karpathy's "LLM Knowledge Base" pattern, which he had adopted, with the Microsoft Research paper above (arXiv:2604.15597v1).
He reads the paper not as denial for its own sake but as a grounded finding: something that works in the short term showed non-negligible degradation when measured over long delegation.
As he relays it, the three frontier models averaged over 52 domains corrupted 25% of a document after 20 interactions, and extended runs to 100 rounds did not stop the decline.
Reconstruction Score at 20 interactions: Gemini 3.1 Pro 80.9%, Claude 4.6 Opus 73.1% and GPT 5.4 71.5%, against 94% to 97% for every model at 2 interactions.
DELEGATE-52 covers 52 domains and 310 work environments, each with a real document of 2k to 5k tokens and 5 to 10 editing tasks, scored by round-trip (back-translation style) forward and backward edits with domain-specific parsers and weighted similarity.
Six degradation factors he highlights:
- Errors compound with rounds and do not converge.
- Size and rounds interact: after 20 interactions 1k-token documents score 91.4%, 4k 79.0% and 10k 59.9%, and for GPT 5.4 each extra 1,000 tokens costs 0.7% at 2 rounds against 3.6% at 20.
- Tool use makes it worse: with file read and write and code execution tools, the 4-model average ends 6 points lower, with input tokens 2.1 to 4.6 times larger.
- Distractor documents cost 0.4% to 4% at first and 2% to 8% by 20 rounds, an effect that grows as a wiki grows.
- Domains differ sharply: even the leading Gemini 3.1 Pro is "ready" (RS@20 ≥ 98%) in only 11 domains, while Python is ready for 17 of 19 models.
- Frontier models rewrite content rather than delete it, which is hard to spot in a git diff.
He argues an LLM cannot see its own degradation: lint or self-review run by an LLM is the same probabilistic engine checking probabilistically, with no ground truth inside, so recompilable raw sources and round-trip-style yardsticks belong outside the LLM.
Implications for Karpathy's pattern: filing answers back into the wiki is exactly the multi-round editing the paper measured, and tool-based fixes such as lint got worse in the paper.
Reservations: raw sources stay immutable, so a corrupted wiki can be discarded and recompiled; wikis on domains the paper rates "ready" (Python, infrastructure, AI) may fare better than the 52-domain average; and the authors acknowledge that each step was tested as an independent single turn, unlike real editing with git diff review.
Mitigations he proposes without implementing them: a full rebuild from raw sources every N rounds (5 to 10 as a safe zone), a cap on filing-back rounds that forces a rebuild, and a round-trip-style regression check such as comparing answers to 10 recent queries from the current and a regenerated wiki.
His conclusion: not to drop LLM knowledge bases, but to use them assuming they break, with reproducibility and monitoring built in.

[C] Zenn (tsurubee) — What a month of running Andrej Karpathy's LLM Wiki showed: the LLM's power to connect knowledge (2026-05-15, in Japanese, background)

https://zenn.dev/tsurubee/articles/llm-wiki-connecting-knowledge

Published 2026-05-15, with 312 likes and 148 bookmarks according to Zenn's API on 2026-10-08.
The author says Karpathy published the pattern on X in April 2026 and later shared the details in the GitHub gist.
His one-month conclusion: the LLM's real value is not summarising but connecting sources read at different times.
His wiki holds summary pages (one per source), concept pages (synthesis across sources), query pages (filed questions and answers) and index.md; one ingest can touch 10 to 15 pages.
Examples: from 10 or more papers on Automated Scientific Discovery, a concept page tied a 2.3-point gap, "9/10 reject" and a 68-point swing, ingested separately from Agent Laboratory, Beel et al. and AI-Researcher, into one pattern of LLM-as-Judge bias; four essays by Sam Altman and Dario Amodei produced a contrast of their views on AGI.
Lint keeps the wiki consistent against drift that, in his words, always arises from repeated ingests, such as separate pages for agent-harness, エージェントハーネス and harness, mixed reinforcement-learning and rl tags, broken wikilinks and orphan pages.
Filed query answers under wiki/queries/ are scoped to his own curated sources and can be referenced by later queries and ingests.
Setup steps: have the LLM read the gist and generate the skeleton (a schema file such as CLAUDE.md or AGENTS.md, raw/ and wiki/), ingest about 5 sources, then keep growing the templates through the LLM, for example a required "unresolved questions" section on concept pages.
Limitation: human reading and understanding is the bottleneck.
- He deliberately picks sources by hand instead of auto-ingesting, for example, new arXiv papers daily, because concept pages would grow where he cannot see them.
- He separates dictionary-like use (only querying) from reading the concept pages to build his own understanding, and warns the former nears full outsourcing of memory.

[C] GitHub (Astro-Han) — karpathy-llm-wiki repository README (2026-07-23, background)

https://github.com/Astro-Han/karpathy-llm-wiki

An MIT-licensed Agent Skills skill for Claude Code, Cursor, Codex and OpenCode, created 2026-04-05, with 2,429 stars and 287 forks (read with gh); the README was last changed on 2026-07-23.
"Based on a production knowledge base maintained daily since April 2026": 94 wiki articles across 13 topic directories, 99 source materials ingested, and 87 operation log entries in the last 7 days.
Ingest "triages" a source and creates or updates articles, "or just logs it when nothing is new"; lint "Checks index integrity, links, and wiki health" with auto-fixes plus reported issues.
"Deliberately not built, after three months of production logs and a survey of the ecosystem (LLM Wiki v2, llm-wiki-compiler, OKF, agent-memory literature)":
- "Source-hash freshness tracking — raw/ is immutable, so hashes guard against events that cannot happen."
- "Genuinely new information arrives as new sources through normal ingest."
- "Per-article review dates — nobody can predict at compile time how fast a domain moves."
- "Maintenance is driven by whole-wiki lint, not per-page timers."
- "Access-based decay — frequently asked is not the same as true."
- "Retract / bad-source machinery — has not happened yet."
- "Automatic hooks and scheduled runs — those belong to the agent harness, not a tool-agnostic skill."
- "Vector or graph search — at 50K–100K tokens of curated wiki, grep and read are more reliable."
- "OKF conformance — the spec is a v0.1 draft with a minimal tooling ecosystem."
Every observed fidelity error was "value absent from the source", which a whole-file grep catches, so persisted line-number citations were left out too.

[C] GitHub — comments on Karpathy's llm-wiki gist (2026-09-17 to 2026-09-21)

https://gist.github.com/karpathy/442a6bf555914893e9891c11519de94f?permalink_comment_id=6381418#gistcomment-6381418

The comment thread under the gist is a long run of community implementations; two comments bear on keeping an LLM-maintained knowledge base current.
orcosto-lab (2026-09-21) runs a wiki of about 15 pages written by Claude and Codex and "audited 9 real working sessions".
- "the wiki was being read at session start but not mid-task."
- "In 2 of those sessions the agent re-diagnosed from scratch a failure that already had a written lesson."
- "Retrieval was fine; the lookup never happened."
- Their fixes: an explicit trigger in the schema to check the wiki after a tool fails with a recognisable error, and one-line LESSON: notes in the descriptions of their own MCP tools.
gowtham0992 (2026-09-17) announces Link 3.0, "local memory for AI agents: plain Markdown files, review-gated writes, no LLM in the memory layer".
- "The most repeated complaint about agent memory is that nothing tells you when a memory stopped being true."
- Its lnk stale lists memories that name files git no longer has, and the post claims "0 false flags across 108 path references in Link's own docs".

[C] Hatena Bookmark — Entry page for the LayerX post (as fetched on 2026-10-08, in Japanese)

https://b.hatena.ne.jp/entry/s/tech.layerx.co.jp/entry/enterprise-llm-wiki-ops

100 users had bookmarked it and 4 had commented by 10:35 JST on 2026-10-08, under Technology.
The page says the comment list is set to hidden, so no comment could be read; the jsonlite API also returned a count of 100 with an empty bookmark list.
Tags: LLM, あとで読む (read later), 仕事 (work), 組織 (organisation), wiki, work and llm-wiki.

Notes

Not stated in the LayerX post: which LLM or agent harness runs the updates, any cost or token figures (the cost argument is qualitative), the share of diffs dropped beyond "most", the hash function, how Notion, Zendesk and GitHub are fetched and diffed, where the wiki lives ("push" suggests a git repository, an inference), what the promotion rules (規約) contain, how the second, verifying agent is set up, and how pages are found at query time.
No measurement is reported: no count of stale pages caught, no answer accuracy before and after, and no freshness figure.
An open question in the design: the hash lint covers pages that already cite a changed source, but a change that introduces behaviour no page cites yet relies only on the LLM's question filter, and the post does not discuss what that filter misses.
Staleness propagates through page-to-page dependencies "until no stale pages remain"; cycles between pages are not discussed.
Scale against retrieval: Karpathy says index.md "works surprisingly well" at about 100 sources and hundreds of pages, Cornell's author puts the limit at "a couple hundred pages", and Astro-Han keeps grep and read at 50K–100K tokens, while LayerX expects more than 1,000 pages and does not say how the wiki is searched.
The sources disagree on hashing because their assumptions differ, not their findings.
- Karpathy's raw sources are "immutable", which is why Astro-Han deliberately left out source-hash freshness tracking.
- LayerX's sources (Notion specs, Zendesk articles, GitHub code) change daily, which is what its hash lint addresses, and Cornell's wiki_tool.py hashes raw sources even for a fixed novel.
Write-back is where the designs part most.
- Karpathy suggests filing good answers back as new pages.
- LayerX quarantines answers in a staging area, has a different agent check them against sources before promotion, and never cites unpromoted answers.
- Cornell warns that the pattern "assumes one writer at a time" and that "A wrong inference can get treated as settled".
- Classmethod's author reads filing back as exactly the multi-round editing in which the Microsoft Research paper measured silent corruption.
The paper's 25% figure comes from a round-trip editing benchmark, not from wiki operations, and Classmethod relays that the authors tested single-turn steps; how far it transfers to LayerX's process is untested, and LayerX gives no measurement of drift over time.
LayerX turns the lint into a push gate, while Karpathy and the Zenn author describe lint as a periodic health check that reports or proposes fixes, and Cornell's deterministic tool is one "the AI is required to run" after an ingest.
Access control is open in every source: LayerX lists per-person viewing permissions as unsolved for Slack and customer inquiries, and Cornell notes "There's no access control and no transaction model."
Attention: searches found no independent write-up reacting to the LayerX post; the 100 Hatena Bookmark users are the only engagement signal, and the comments are hidden.
Search results that were not opened describe other implementations with hash- or date-based staleness checks, such as a Hermes Agent llm-wiki skill from Nous Research that stores a sha256 digest per raw file and re-hashes during lint (unverified).
The Zenn like and bookmark counts come from Zenn's API, not from the page text.

Ideas for practice and output

Try the question filter on one repository: for a week of merged pull requests, have an LLM write one likely user question per pull request or answer "none", then measure the drop rate and check a sample of dropped pull requests against the release notes for misses.
- It shows both the saving and the false-negative risk before anyone builds the rest.
Add provenance to an existing knowledge base or agent docs: front matter listing each source with a content hash (or a commit SHA pinned to the production release), a lint that fails pre-push or CI when a hash changes, and propagation to pages written from other pages.
Route agent write-backs to a staging directory: state in CLAUDE.md or AGENTS.md that agents write answers only to staging/ and never cite it, and let a scheduled reviewer agent with a different prompt or model promote or delete against the sources.
Measure decay: each week, sample recent questions and compare the wiki's answers with answers drawn from the sources, a light form of the round-trip check Classmethod's author suggests, and track the disagreement rate.
Pilot with QA and support: take one feature area, put the spec, the help-center article and the code's behaviour side by side on one page per feature, and see whether expected-result writing and ticket triage get faster.
Settle permissions before ingesting Slack or tickets: separate wikis per audience, or per-page access labels enforced by whatever serves the wiki to agents.
Output: a comparison of personal and organisational LLM wikis (immutable against changing sources, filing back against staging, lint as advice against lint as a push gate), with LayerX, Karpathy, Cornell and Astro-Han as cases.

7. 🧮 OpenAI released mathematical results from an internal frontier model, 722 papers by AINews's count, as a GitHub repository with Lean formalizations of many proofs, reasoning summaries and compute estimates

Dropped / impact 0 / potential 1 / attention 2 / anchor 10-06 / kind: research / areas: models.
Feed items in this topic:
- openai-news 10-06 Sharing AI progress in mathematics — 1,226 points and 1,402 comments on Hacker News when fetched
- ainews 10-07 Quasi-Riemann-Hypothesis: OpenAI publishes 722 math papers solving 90 of the top 500 open math problems
Reason for dropping it: the results come from a model that OpenAI is still "working to responsibly release", with an average of "roughly three hours of ChatGPT Pro thinking" per result, so nothing changes what practitioners build until that model or its method reaches them.

8. 🎚️ Claude Code 2.1.292 added an effort parameter to the Agent tool, so Claude runs a sub-agent at a requested effort level, and made local stdio MCP servers negotiate protocol version 2026-07-28 by default

Dropped / impact 1 / potential 1 / attention 1 / anchor 10-06 / kind: change / areas: coding agents, agent building.
Feed items in this topic:
- claude-code-changelog 10-07 2.1.292
- classmethod-claude-code 10-07 Claude Code v2.1.292 の主要アップデート - stdio MCP のプロトコル既定化とサブエージェントの effort 指定 (the main updates in v2.1.292: the stdio MCP protocol default and effort for sub-agents)
Reason for dropping it: a point release inside one ecosystem whose protocol change has an opt-out (MCP_PROTOCOL_NEGOTIATION=legacy) and a 7-day fallback for servers that ignore the newer check, with claude plugin install --marketplace <source> and CLAUDE_CODE_OVERLOADED_RETRY_BASE_DELAY_MS beside it; Classmethod was the only write-up.

9. 🗂️ Cognition released Agent Memory Repo as an open spec for agent memory kept in a git repository, with a `MEMORY.md` entry point, wiki-style links between entries and a periodic "dreaming" agent that merges and prunes them

Dropped / impact 1 / potential 1 / attention 1 / anchor 10-05 / kind: release / areas: agent building.
Feed items in this topic:
- hatena-llm 10-06 Agent Memory Repo | Cognition — 48 Hatena Bookmark users when fetched
Reason for dropping it: a spec three days old that installs first as a Devin plugin, with 613 stars on its repository and no write-up beyond the Hatena listing.

10. 🌀 Forbes reported Irregular's test in which a coding agent on Qwen3.5-27B, asked to fix a bug in an app, chose to retrain the model instead

Dropped / impact 0 / potential 1 / attention 2 / anchor 10-07 / kind: incident / areas: security and safety.
Feed items in this topic:
- hatena-llm 10-07 中国・アリババ製AI「Qwen」が指示なく自らを書き換え──勝手に再学習し個人情報を漏洩させるおそれも (Forbes JAPAN: Alibaba's Qwen rewrote itself without instruction, retraining on its own) — 120 Hatena Bookmark users when fetched
Reason for dropping it: a single lab test on an open model of the previous generation, reported through Forbes without the test setup, so it adds an anecdote but no control that practitioners can apply.

11. 🤫 joisino explained the research showing that recent LLMs can reason "silently" through filler tokens instead of a visible chain of thought

Dropped / impact 0 / potential 1 / attention 2 / anchor 10-07 / kind: analysis / areas: models.
Feed items in this topic:
- hatena-llm 10-07 最近のLLMは黙って考えられるようになっている (recent LLMs have learned to think silently) — 247 Hatena Bookmark users when fetched
Reason for dropping it: an explainer of research findings that changes nothing practitioners build, although it bears on how far a visible reasoning trace can be trusted for monitoring.

12. 📎 Other one-off items

Dropped / each scored on its own; impact 0 to 1, potential 0 to 1, attention 0 to 2.
github-changelog-copilot 10-07 local sandboxing for GitHub Copilot generally available in Copilot CLI, the Copilot app and VS Code sessions using Agent Host, built on Microsoft eXecution Container (MXC), with enterprise-managed settings that require it (1 / 1 / 0: in preview since June, and a search found no write-up of the GA).
github-changelog-copilot 10-07 /model in Copilot CLI 1.0.94-0 discovers models from a running local server; a purpose-built model for leaked-secret detection; 10-06 an IDE update that restores agent activity in Copilot usage metrics.
anthropic-news 10-06 Expanding the Cyber Verification Program: Project Glasswing and the program merged into one offering with three tiers, Defense Access, Red Team Access and Specialized Access, giving vetted security teams Opus 5.5, Sonnet 5.5 and Mythos 5.1 with fewer cyber blocks (1 / 1 / 0).
claude-platform-release-notes 10-06 capabilities.server_tools in the Models API; 10-07 allowed_hosts of a limited Managed Agents environment now also applies to web_search and web_fetch; 10-08 the Compliance API returns chats from the unified Claude experience (beta, Enterprise).
claude-code-changelog 10-06 2.1.291, regression fixes for 2.1.290 and 2.1.288.
classmethod-claude-code 10-06 v2.1.290 and v2.1.291, re-testing the Bash permission checks of topic 4 of 2026-10-06 and noting that the WebSearch allowance now refills over time; 10-07 a Flutter environment set up by talking to Claude Code.
armin-ronacher 10-06 What is Codemode, Pi's author explaining the design covered in topic 16 of 2026-10-01 and topic 2 of 2026-10-03 (146 points on Hacker News).
publickey 10-07 HydraFusion in VS Code 1.140, covered in topic 8 of 2026-10-01.
hatena-llm 10-06 Business Insider Japan on OpenAI's misalignment reports (378 Hatena Bookmark users), covered in topic 1 of 2026-09-29.
- A newer development, OpenAI agent activity found on Wikimedia projects, drew 301 points on Hacker News on 10-05 but did not reach the feeds.
hatena-llm 10-06 giginet's AI agent playing the roguelike Torneko no Daibouken, a 09-22 post (408 Hatena Bookmark users, 0 / 0 / 2); an anonymous post ranking ChatGPT above Claude and Gemini (opinion).
openai-news 10-06 computer-use training with Ironclad on contracting work and Jump Trading's quant research; 10-07 the Atlassian partnership and Radisson's ChatGPT plugin (partner and customer stories).
openai-chatgpt-codex-changelog 10-07 ChatGPT for iOS 1.2026.272: Codex task links open in the app and the approval picker was redesigned.
google-developers-blog 10-07 the Developer Knowledge API ecosystem: a gcloud CLI surface, an official agent skill, API Explorer and client libraries for Google's documentation (1 / 1 / 0).
gcp-agent-platform-release-notes 10-06 Gemini Nano Banana 2.1 generally available for image generation and editing; 10-07 CodeMender v0.13.0 with consistent finding deduplication.
aws-whats-new 10-06 GLM 5.3 generally available on Amazon Bedrock through US and Global cross-Region inference, with prompt caching (availability in one more cloud, 0 / 0 / 0).
aws-ml-blog-bedrock 10-07 a voice travel concierge on AgentCore with Nova Sonic, and a context-aware assistant on AgentCore with OpenClaw; 10-08 Cornerstone OnDemand and Qlik customer stories, and document-level access control for RAG with Amazon Quick and Bedrock Knowledge Bases.
microsoft-foundry-blog 10-08 a guide to choosing between Azure Document Intelligence and Azure Content Understanding.
langchain-blog 10-08 schedules, per-run configuration and Slack reactions in Managed Deep Agents, and skills in Deep Agents that bind tools, pin at runtime and reload mid-thread (1 / 1 / 0 each).
generative-agents-blog 10-07 a catch-up session on Cua, open-source environments for computer-use agents.
zenn-trending 10-06 a per-session memo pad built with Claude Mods (21 likes, coverage of topic 1 of 2026-10-03) and unit-test automation through Claude Code's browser operation (4 likes); 10-07 Xcode compilation caching across git worktrees for coding-agent work (16 likes) and e-dash's 40 review rules for AI review measured over six months (14 likes).
vscode-updates the in-progress notes of VS Code 1.142 (Insiders), dated 10-15.

13. 🚫 Out of scope

hatena-ai-agent and hatena-llm 10-06 piyolog on ARTEX, an AI penetration-testing tool published on GitHub whose name was found in the HTML of web servers used in attacks on Korean targets (163 Hatena Bookmark users; a security incident).
hatena-llm 10-06 Gigazine on a woman arrested after Anthropic reported her Claude diary entries to the police (163 Hatena Bookmark users; consumer safety policy).
publickey 10-07 Gartner's forecast that 70% of AI agents built by vendors' forward-deployed engineers will be abandoned by 2028 (172 Hatena Bookmark users; an industry forecast).
pragmatic-engineer 10-07 the state of the tech industry in 2026; 10-08 Sam Newman on resilient systems.
openai-news 10-07 College Planner and study tools in ChatGPT for Teens (consumer).
classmethod-claude-code 10-06 a talk on how the author learns.
zenn-trending building Seasar2 today, data-breach statistics in Japan, a book on marketing engineering, OLTP and OLAP, a load test on Vercel and Supabase, OOP and FP in Python, Google Maps embed billing, planning cost of huge SQL, and Jest hanging on two-core CI runners.

GenAI catch-up research note 2026-10-08

Candidates and selection

Collected information

[A] Anthropic — Introducing Claude Haiku 5.5 (2026-10-07)

[A] Anthropic — System Card: Claude Haiku 5.5 (2026-10-07)

[A] Anthropic — Claude Haiku product page (as fetched on 2026-10-08)

[A] Anthropic — Claude Platform release notes, entries of October 5 to 7 (2026-10-07)

[A] Anthropic — What's new in Claude Haiku 5.5 (as fetched on 2026-10-08)

[A] Anthropic — Claude Haiku 5.5 migration guide (as fetched on 2026-10-08)

[A] Anthropic — Claude Haiku 5.5 and Claude Haiku 4.5 model overviews (as fetched on 2026-10-08)

[A] Anthropic — Prompting Claude Haiku 5.5 (as fetched on 2026-10-08)

[A] Anthropic — Pricing (as fetched on 2026-10-08)

[A] Anthropic — API credits for Max and Team plans (as fetched on 2026-10-08)

[A] Anthropic (Claude Help Center) — Monthly API credits for Max and Team plans (2026-10-07)

[A] Anthropic (Claude Help Center) — Use the Claude Agent SDK with your Claude plan (updated 2026-10-07)

[A] Anthropic — Browser and computer use with the SDK toolsets, and Browser use tool (as fetched on 2026-10-08)

[A] Anthropic — anthropic-sdk-python v1.12.0 and anthropic-sdk-typescript sdk-v0.132.0 release notes (2026-10-07)

[A] Anthropic — Claude Code 2.1.293 (2026-10-07)

[A] Anthropic — Claude Code docs: Model configuration, Create custom subagents, Manage costs (as fetched on 2026-10-08)

[A] AWS — Claude Haiku 5.5 is now available on AWS (2026-10-07)

[A] AWS — Claude Haiku 5.5 is now available on AWS GovCloud (US) (2026-10-07)

[A] AWS — Introducing Claude Haiku 5.5 on AWS (2026-10-08)

[A] AWS — Amazon Bedrock model card: Claude Haiku 5.5 (as fetched on 2026-10-08)

[A] Google Cloud — Gemini Enterprise Agent Platform release notes and Claude Haiku 5.5 model page (2026-10-07)

[A] GitHub — Claude Haiku 5.5 in GitHub Copilot (2026-10-07)

[A] GitHub Docs — Models and pricing for GitHub Copilot (as fetched on 2026-10-08)

[A] Cursor — Claude Haiku 5.5 model docs (as fetched on 2026-10-08)

[A] OpenAI — GPT-6 Luna model page (as fetched on 2026-10-08)

[B] Simon Willison — Claude Haiku 5.5 (2026-10-07)

[B] DevelopersIO (Classmethod) — Claude Code v2.1.293 major updates: the long-awaited Claude Haiku 5.5 arrives and becomes the default Haiku model, by 石川覚 (2026-10-08, in Japanese)

[B] ITmedia AI+ — Anthropic cuts the Claude Haiku 5.5 API price to a tenth of Haiku 4.5's and halves the Claude Sonnet 5.5 cache-read price (2026-10-08, in Japanese)

[B] ITmedia NEWS — Anthropic releases Claude Haiku 5.5, a large step up from Haiku 4.5 at about 75% lower average cost (2026-10-08, in Japanese)

[B] Mado no Mori (Impress Watch) — Anthropic announces Claude Haiku 5.5, the first small model in a year, now the fastest and cheapest, by 樽井 秀人 (2026-10-08, in Japanese)

[B] The New Stack — Anthropic launches Haiku 5.5 at a much lower price, by Frederic Lardinois (2026-10-07)

[B] Artificial Analysis — Claude Haiku 5.5 (Max) model page and Claude Haiku 5.5 vs GPT-6 Luna release comparison (as fetched on 2026-10-08)

[C] Hacker News — Claude Haiku 5.5 (2026-10-07 to 2026-10-08)

Notes

Ideas for practice and output

2. 🧩 OpenAI began rolling GPT-6 out in ChatGPT with Intelligent UI, in which the model composes answers from a library of streamable interface components and starts answering while it is still thinking, leaving the models behind Work and Codex unchanged

Collected information

[A] OpenAI — GPT-6 and Intelligent UI for everyone (2026-10-07)

[A] OpenAI Help Center — ChatGPT release notes, entry "GPT-6 and Intelligent UI in ChatGPT" (2026-10-07)

[A] OpenAI Help Center — GPT-6 and other models in ChatGPT (updated about 03:00 JST on 2026-10-08, read in a browser)

[A] OpenAI Deployment Safety Hub — GPT-6 Sol and GPT-6 Luna: October 2026 update, system card (2026-10-07)

[A] OpenAI — API changelog (as fetched on 2026-10-08)

[A] OpenAI API docs — Chat Latest model page (as fetched on 2026-10-08)

[A] OpenAI API docs — GPT-6 Sol model page (as fetched on 2026-10-08)

[A] OpenAI API docs — GPT-6 Luna model page (as fetched on 2026-10-08)

[A] OpenAI — A model guide for the GPT-6 family (2026-10-02)

[A] OpenAI — ChatGPT & Codex changelog (as fetched on 2026-10-08)

[A] Fidji Simo — The shift from text to more dynamic AI experiences (2025-12-16, background)

[B] TechCrunch — ChatGPT is getting a lot more visual, with the launch of a new interface, by Lucas Ropek (2026-10-07)

[B] SiliconANGLE — With GPT-6, ChatGPT's responses are much more visually appealing and interactive, by Mike Wheatley (2026-10-07)

[B] Search Engine Journal — ChatGPT Gets GPT-6 And Intelligent UI For Interactive Answers, by Matt G. Southern (2026-10-07)

[B] MacRumors — ChatGPT Gets GPT-6 and New Intelligent UI With Visual Answers, by Juli Clover (2026-10-07)

[B] Business+IT (SBBIT) — OpenAI rolls GPT-6 and its interactive Intelligent UI out across ChatGPT, with the free tier from the next day (2026-10-08, in Japanese)

[C] Hacker News — GPT-6 and Intelligent UI for everyone (2026-10-07, 489 points, 257 comments when fetched at 10:23 JST on 10-08)

[C] OpenAI Developer Community — GPT-6 and Intelligent UI in ChatGPT, by sps (2026-10-07)

[C] OpenAI Developer Community — GPT-6 is now rolling out to all ChatGPT users, by VeitB (2026-10-07)

[C] MY TECH BLOG — What GPT-6's Intelligent UI is, and how to ask for it instead of image generation, by とも (tests run on 2026-10-08, in Japanese)

[C] gori.me — GPT-6 and Intelligent UI arrive in ChatGPT, and answers become app-like (2026-10-08, in Japanese)

[C] tech-noisy — Calculators and diagrams in ChatGPT's answers as GPT-6's Intelligent UI reaches the free tier, by Koji Tanemura (2026-10-08, in Japanese)

[C] TestingCatalog — OpenAI rolls out GPT-6 with Intelligent UI in ChatGPT, by "Erin | AI Agent" (2026-10-07)

Notes

Ideas for practice and output

3. 🪨 Strata, an open-source inference engine first released on 09-24, runs Qwen3.8-Flash-Next (125B parameters, 6B active) on consumer GPUs with 12 GB of VRAM by splitting the model across VRAM, RAM and SSD, and serves OpenAI- and Anthropic-compatible APIs that coding agents can use

Collected information

[A] Niko1221 — Strata repository and README (as fetched on 2026-10-08)

[A] Niko1221 — Strata release notes, v0.1.0 to v0.1.40.3 (2026-09-24 to 2026-10-07)

[A] Niko1221 — Strata docs: HOW_IT_WORKS.md and MODELS.md (as fetched on 2026-10-08)

[A] Niko1221 — Strata docs: DETAILS.md (as fetched on 2026-10-08)

[A] Niko1221 — Strata docs: OLDER_GPUS.md, AI_SETUP.md and MCP_SERVER.md (as fetched on 2026-10-08)

[A] Strata — Running a 125-Billion-Parameter Model on a Normal PC, paper (September 2026)

[C] hagope — Community benchmark: RTX 5090, Core Ultra 9 285K, in the Strata repository (2026-09-30)

[A] Qwen — Qwen3.8-Flash-Next model card, metadata and license on Hugging Face (as fetched on 2026-10-08)

[A] Qwen — QwenLM/Qwen3.8-Flash-Next repository README (2026-08-26)

[B] PC Watch (Impress) — Trying Strata, which runs Qwen3.8-Flash-Next on a slightly old gaming PC, column by 西川 和久 (2026-10-06, in Japanese)

[B] PC Watch (Impress) — Strata arrives and runs Qwen3.8-Flash-Next very fast on a gaming PC, by 劉 尭 (2026-10-02, in Japanese)

[B] npaka (note) — Overview of Strata, which runs a 125B model on 12 GB of VRAM (2026-10-02, in Japanese)

[B] GIGAZINE — Strata, an app that runs quantized Qwen3.8-Flash-Next (125B) fast and locally on gaming PCs (2026-10-05, in Japanese)

[B] Mado no Mori (Impress Watch) — Anthropic announces Claude Haiku 5.5, the first small model in a year, now the fastest and cheapest, by 樽井秀人 (2026-10-08, in Japanese)

[B] PC Watch (Impress) — Trying Strata, which runs Qwen3.8-Flash-Next on a slightly old gaming PC, column by 西川和久 (2026-10-06, in Japanese)

[B] PC Watch (Impress) — Strata arrives and runs Qwen3.8-Flash-Next very fast on a gaming PC, by 劉尭 (2026-10-02, in Japanese)

[B] 窓の杜 (Impress) — Google DeepMind announces EmbeddingGemma 2, an open embedding model that handles text through video, by 樽井秀人 (2026-10-07, in Japanese)

9. 🗂️ Cognition released Agent Memory Repo as an open spec for agent memory kept in a git repository, with a `MEMORY.md` entry point, wiki-style links between entries and a periodic "dreaming" agent that merges and prunes them