# Synthetic Anvil · full index

> Synthetic Anvil is an independent publication covering the AI stack: models, agents, tools, hardware and the silicon under them. Sourced, checked, no hype.

## Asus ProArt P16 with Nvidia RTX Spark N1X costs $7,000 with 128 GB, per Notebookcheck
URL: https://syntheticanvil.com/sparks/asus-proart-p16-rtx-spark-n1x-7000
Type: News brief (curated by agents, checked by the desk) · Section: Silicon
Source: https://www.notebookcheck.net/Asus-ProArt-P16-RTX-Spark-review-verdict-So-expensive-but-pretty-awesome.1428207.0.html (2026-10-19)
Summary: Notebookcheck finds the $7,000, 128 GB RTX Spark ProArt P16 weighs under 1.8 kg and matches last year's RTX 5070 model on GPU performance.

Curated by agents · checked by the desk

The Asus ProArt P16 is a laptop built on Nvidia's RTX Spark N1X SoC, and Notebookcheck published its review of the machine on October 19, 2026. The configuration Notebookcheck covers pairs the chip with 128 GB of RAM and costs $7,000. The review, written by managing editor Andreas Osthoff and translated from a German original, calls the laptop "no bargain" but says its target buyers can purchase it "with virtually no reservations."

The 2026 ProArt P16 (series H7607) uses a redesigned metal chassis that weighs under 1.8 kg, which Notebookcheck says is more than 300 g lighter than Apple's MacBook Pro 16. The 16-inch display is a 4K tandem OLED panel running at 120 Hz, carried over from the previous top-end model. Per the review, it offers very high brightness, accurate colors and a higher PWM frequency than before, though the article gives no nit figure or PWM value. Fan noise reaches about 50 dB(A) under heavy load, and Notebookcheck says the system can stay quiet when the workload allows. Battery life falls short of 10 hours in the publication's Wi-Fi runtime measurement. The review also credits the keyboard, the haptic trackpad and the speakers.

On graphics, Notebookcheck reports performance on par with last year's ProArt P16 equipped with an RTX 5070. The N1X model cannot match the RTX 5090 version of the previous generation, which the review says is better suited to gaming. Notebookcheck names local AI workloads, content creation and gaming as the target uses, and lists the high price and the sub-10-hour battery life as the main drawbacks. For buyers weighing generations, that places the new model below the older RTX 5090 configuration on GPU output.

The review gives no LLM tokens-per-second figures or other exact AI throughput numbers, despite naming local AI as a core use case. It also does not detail CPU benchmark results, battery capacity, storage, ports, other configurations or software compatibility, and it does not state regional availability. Notebookcheck points readers to a separate in-depth review for full measurements. Until figures for local model inference appear, the case for the 128 GB configuration rests on memory capacity rather than measured AI output.

Source: [Notebookcheck](https://www.notebookcheck.net/Asus-ProArt-P16-RTX-Spark-review-verdict-So-expensive-but-pretty-awesome.1428207.0.html), October 19, 2026.

**Why it matters under load:** At $7,000, the N1X ProArt P16 buys 128 GB of memory for local models in a sub-1.8 kg chassis, but its GPU sits at RTX 5070 level and no published tokens-per-second figure yet shows what that memory delivers.

## Cloudflare releases Clairic, a no-reasoning extraction model, on Workers AI
URL: https://syntheticanvil.com/sparks/cloudflare-clairic-extraction-model-workers-ai
Type: News brief (curated by agents, checked by the desk) · Section: Agents
Source: https://blog.cloudflare.com/clairic-extraction-model/ (2026-10-19)
Summary: Billed on input only, Clairic cut a claims pipeline to $6,032 per million claims from $11,740 and to 19.3 s from 61.7 s, per Cloudflare.

Curated by agents · checked by the desk

Cloudflare released Clairic in preview on Workers AI on October 19, 2026, as `@cf/cloudflare/clairic`. The company calls it the first of a new "System One" class of extraction models: it reads an input and returns typed values in a single forward pass, with "no reasoning and no output tokens," and it charges only for input. In a damage-claim pipeline Cloudflare built, moving extraction to Clairic cut cost to $6,032 per million claims from $11,740 and end-to-end latency to 19.3 seconds from 61.7 seconds.

Developers call it from a Worker with `env.AI.run()` or from anywhere through the REST API. Requests declare fields by type: text (returned as a span with character offsets), number, date, time, datetime, duration, list, estimate and forecast. Estimates come back as a median with an 80% interval (p10 to p90) inside declared bounds, and forecasts return an interval per step. Outputs carry confidence scores, and the input can include up to four images. Cloudflare says the model typically responds in under a second. In the claims pipeline, Clairic extracted the customer name, order ID, amount, days since delivery, damage list and a repair-cost estimate in 0.46 s. Clef, a System One decision model, chose refund or repair in 0.22 s, and GLM-5.3 (`@cf/zai-org/glm-5.3`) wrote the reply in 18.6 s. The baseline ran GLM-5.3 for all three steps, spending 16.1 s to extract and 21.9 s to decide. Cloudflare puts the result at 69% less time and 49% lower cost. On a 21-day forecast of TSA daily passenger counts, the company reports an average error of 3.3%, with 17 of 21 actual counts inside the 80% interval.

The "System One" label comes from Kahneman's Thinking, Fast and Slow, with LLMs such as GPT, Claude, Gemini and DeepSeek cast as System Two. Cloudflare pitches Clairic against the parsing, schema validation, retries and spot checks that teams layer on top of LLM extraction, and notes that Clairic's repair estimate stayed identical across runs while GLM-5.3 returned $250, $250 and $220. The company lists preview limits: one- or two-step arithmetic is reliable, but longer calculations and aggregation across table rows are not yet, and the authors suggest letting code do the math. Estimates work best with supporting evidence in the input, calibration is "measured, not guaranteed," intervals may be too narrow on unfamiliar data, and forecasting does not replace dedicated time-series models.

Several details are absent. The post gives no per-token price for Clairic, only pipeline totals. It states no parameter count, architecture, maximum input length or supported languages. Cloudflare describes the endpoint as "an early checkpoint" and names no general-availability date or rate limits. On weights, it says only "We intend to release the model open-weights soon," with no date or license. The claim that Clairic is more accurate than LLMs for certain uses comes without a dataset or accuracy figures.

Source: [Cloudflare](https://blog.cloudflare.com/clairic-extraction-model/), October 19, 2026.

**Why it matters under load:** Input-only billing removes output-token spend from extraction steps, but without a published per-token rate or rate limits, the 49% saving cannot yet be modeled at production volume.

## fal and Black Forest Labs launch FLUX 3 Max, a 720p video model at $0.0425 per second
URL: https://syntheticanvil.com/sparks/fal-flux-3-max-720p-video-model
Type: News brief (curated by agents, checked by the desk) · Section: Studio
Source: https://fal.ai/flux-3-max (2026-10-19)
Summary: fal's post-trained FLUX 3 Max ships text-to-video and image-to-video at 720p, priced at $0.0425 per second until November 7, down from a $0.17 list price.

Curated by agents · checked by the desk

fal released FLUX 3 Max on October 19, 2026. It is a video generation model that fal Research post-trained with Black Forest Labs on the FLUX 3 foundation model, and it went live the same day on fal's inference platform. The headline number is the launch price: $0.0425 per second of 720p output, which fal describes as 75% off the $0.17-per-second list price.

There are two endpoints at launch, text-to-video and image-to-video, both at 720p and both at the same price. Billing is per second of output video with no minimums and no subscription. The promotional rate ends November 7, 2026. At those rates a 10-second clip costs $0.425 during the promotion and $1.70 at list. Developers call the model through fal's JavaScript and Python clients using endpoint IDs such as `blackforestlabs/flux-3-max/text-to-video`. fal's FAQ says content generated through its API can be used commercially, subject to fal's terms of service. The product page says its information is current as of October 18, 2026.

fal's speed figures are averages for a 10-second, 16:9 clip. FLUX 3 Max takes 12.45 seconds, against 126.44 seconds for the original FLUX 3, 277.80 for Seedance 2.5, 180.16 for Wan 3.0, 83.26 for MiniMax H3 at 768p and 47.37 for Gemini Omni Flash 1.1. For quality, fal cites preliminary results from Artificial Analysis's image-to-video arena (AA-Video-I2V v1.1): FLUX 3 Max scores 1,139 Elo, level with Seedance 2.5 at 1,139 and just behind MiniMax H3 at 768p with 1,141. fal calls that a tie for first, citing overlapping confidence intervals. The original FLUX 3 sits at 1,089 and Wan 3.0 at 1,127.

The numbers do not line up perfectly across sources. Unite.AI reports that the Artificial Analysis leaderboard itself lists FLUX 3 Max at 1,138 ±15 across 5,054 samples, ranked second behind MiniMax H3 at 1,140, and that fal's release quotes a 10.95-second generation time rather than the product page's 12.45 seconds. fal says it is still post-training the model, and Unite.AI reports the company calls this a first iteration. The product page states no maximum clip duration. It mentions draft, keyframe and extend endpoints for the base FLUX 3, but it announces none for FLUX 3 Max, although Unite.AI says the announcement references keyframes-to-video. Watch for a final Artificial Analysis rating, a stated duration limit and any new endpoints before the promotion ends on November 7.

Source: [fal](https://fal.ai/flux-3-max), October 19, 2026.

**Why it matters under load:** The per-second cost quadruples on November 7, so any pipeline sized on launch pricing needs a budget line at $0.17 per second before batch volume scales.

## GitHub retires six Copilot models, including GPT-5.5, GPT-5.4 and Grok 4.5
URL: https://syntheticanvil.com/sparks/github-copilot-retires-gpt-5-5-gpt-5-4-grok-4-5
Type: News brief (curated by agents, checked by the desk) · Section: Stack
Source: https://github.blog/changelog/2026-10-19-github-copilot-models-deprecated-on-october-19-2026 (2026-10-19)
Summary: As of October 19, 2026, six models leave most Copilot experiences, with GPT-6.1 Sol, GPT-6 Luna, Gemini 3.8 Flash and Grok 4.7 named as replacements.

Curated by agents · checked by the desk

GitHub deprecated six models across most GitHub Copilot experiences on October 19, 2026, according to a changelog post published the same day. The affected surfaces are Copilot Chat, inline edits, ask and agent modes, and code completions. The six models are Gemini 3.7 Flash, GPT-5.5, GPT-5.4, GPT-5.4 mini, GPT-5 mini and Grok 4.5. GitHub first announced the retirement on September 18, 2026, 31 days before the cutoff.

GitHub maps each retired model to a suggested replacement. GPT-5.5 and GPT-5.4 point to GPT-6.1 Sol. GPT-5.4 mini and GPT-5 mini point to GPT-6 Luna. Gemini 3.7 Flash maps to Gemini 3.8 Flash, and Grok 4.5 maps to Grok 4.7. Four OpenAI models collapse into two. The post says no action is required to remove the deprecated models, but tells users to update workflows and integrations to supported models. Enterprise administrators may need to enable the alternatives through model policies in Copilot settings. Enabled models appear in the Copilot Chat model selector in VS Code and on github.com, and admins can check individual Copilot settings to confirm a model's policy is on. GitHub directs enterprise customers with questions to their account manager.

The admin step gained an API the same day. A separate October 19 changelog post says GET and PATCH REST endpoints for Copilot model policies are now generally available at four levels: enterprise (`/enterprises/{enterprise}/copilot/model-policies`), enterprise teams (`/enterprises/{enterprise}/teams/{team_slug}/copilot/model-policies`), enterprise apps (`/enterprises/{enterprise}/copilot/apps/model-policies`) and organization (`/orgs/{org}/copilot/model-policies`). Per that post, enterprise policies can delegate model control to organizations (organization mode) or to teams and apps (enterprise teams mode). For admins running many organizations, that is a scripted path to enabling GPT-6.1 Sol or GPT-6 Luna instead of editing settings pages one by one. The API post does not list required token scopes or which plans can use the endpoints.

More retirements are scheduled. The deprecation notice links an October 15 post titled "Upcoming deprecation of selected GitHub Copilot models in mid-November" but does not summarize which models it covers. The October 19 notice says nothing about pricing or premium request multipliers for the replacement models, and it does not say when each replacement reached every Copilot client. It also does not define "most": the post does not name which Copilot experiences, if any, still offer the retired models.

Source: [GitHub](https://github.blog/changelog/2026-10-19-github-copilot-models-deprecated-on-october-19-2026), October 19, 2026.

**Why it matters under load:** Any script, extension or agent config that pins GPT-5.5, GPT-5.4 or Grok 4.5 by name now needs a new model ID, and in enterprises where admins have not enabled the replacements through model policies, those models will not appear in the selector.

## Inception ships Mercury 3, a diffusion LLM with 1M context at $0.20/$0.70 per M tokens
URL: https://syntheticanvil.com/sparks/inception-mercury-3-diffusion-llm-1m-context
Type: News brief (curated by agents, checked by the desk) · Section: Agents
Source: https://www.inceptionlabs.ai/blog/introducing-mercury-3 (2026-10-19)
Summary: Context grows from 260K to 1M tokens, Inception reports 1,068 tokens/sec on NVIDIA GPUs, and a launch discount halves the price to $0.10/$0.35.

Curated by agents · checked by the desk

Inception Labs released Mercury 3 on October 19, 2026, and calls it "the most capable diffusion-based LLM released to date." The headline figure is throughput: the company reports 1,068 tokens per second on NVIDIA GPUs and says the model runs 4 to 8x faster (the post does not name the baseline) while scoring on par with or better than GPT-6 Luna and Claude Haiku 5.5 on a range of benchmarks.

The context window rises to 1M tokens, up from 260K for Mercury 2.5. Inception says Mercury 3 is more than 40x larger than Mercury 1 in total parameters and that its standard-benchmark intelligence rose 3x from Mercury 1 (mini), but it does not publish a parameter count. List pricing is $0.20 per million input tokens and $0.70 per million output tokens. At launch the model is 50% off, at $0.10 input and $0.35 output, and the post gives no end date for that discount. Cached input tokens are 90% off the input price. Mercury 3 is available on the Inception API Platform, OpenRouter, Baseten and Vercel, and the API is OpenAI-compatible. The Inception platform offers 100 million free tokens, with no stated duration or terms. Enterprise deployments add dedicated capacity, autoscaling, compliance controls and configurable data retention.

Inception positions Mercury 3 against GPT-6 Luna and Claude Haiku 5.5. The post cites customer results, all vendor-reported. TinyFish AI ran 50 live Mind2Web browser-navigation tasks, and Mercury 3 completed 50% of them, which the company says is more than GPT-6.1-Sol managed. Octen AI reports a median generation time of 0.9 seconds and a median end-to-end response of 2.2 seconds, with its own search step taking about 80 ms. RevisionDojo says hints, marked answers and definitions return in about a second, and Lorikeet reports better latency and eval results in early use. Alongside the flagship, Inception lists Mercury Voice, tuned for time to first answer token, and Mercury Decide, a classification model. The post contains no limitations section.

Several details are missing. The aggregate benchmark scores appear only in a chart image, not in the text. The 1,068 tokens/sec figure comes without a GPU model, batch size or prompt length. The post does not say whether weights are available, does not explain how its diffusion approach generates text, and mentions no function calling, tool use or structured output support beyond OpenAI API compatibility. The post cites no third-party benchmark results.

Source: [Inception Labs](https://www.inceptionlabs.ai/blog/introducing-mercury-3), October 19, 2026.

**Why it matters under load:** For agent loops bound by output latency, 1,000+ tokens/sec at $0.35 per million output tokens could cut both wall-clock time and spend, but the discount has no end date, so budgets should be sized at the $0.70 list price.

## SonicBoom beats llama.cpp on decode with no Python in the stack
URL: https://syntheticanvil.com/sparks/sonicboom-python-free-runtime
Type: News brief (curated by agents, checked by Alessandro Moreira) · Section: Silicon
Source: https://github.com/hardenedlinux/SonicBoom (2026-10-19)
Summary: HardenedLinux's C++ and CUDA runtime posts a 12 to 18% decode lead over llama.cpp on one RTX 3050, with prefill at parity on short prompts and an MLIR planner doing the work.

Curated by agents · checked by the editor

HardenedLinux opened a community benchmark call for SonicBoom v0.0.3 on October 19, 2026. The runtime is C++ and CUDA with no Python at build or run time: one shared library, a stable C ABI, GNU Guile as the first-class language, GPL-3.0-or-later. The core is 17.7k lines. The published numbers, medians of 3 process runs on a laptop RTX 3050 8 GB with the same GGUF file and the same quantized kernels, put decode 12 to 18% ahead of llama.cpp at commit 43fe9c64281 (Gemma 4 E4B-it Q3_K_M: 53.0 against 44.8 tokens/s at 64 steps). Prefill on a 512-token prompt sits at parity, 1,990 against 1,992 tokens/s. Prefix-cache reuse is exact, and time to first token is 502.6 ms on a 4,000-token prefix, against 3,903 ms for a full recompute.

The boundaries matter. Status is v0.0.1, built and tested only for sm_86. Quant support covers Q3_K, Q4_K and Q5_K, so most downloaded Q4_K_M files do not load yet. One model is verified end to end: Gemma 4 E4B-it Q3_K_M. Build requires SonicCross, a Guile replacement for torchgen. The lead comes from the graph planner and an MLIR tier, not from the kernels. A community report on an RTX 4060 Ti showed a 0.94 ratio, which the maintainers have not reproduced, and the roadmap targets around 100 tokens/s decode on the same card.

Source: [HardenedLinux](https://github.com/hardenedlinux/SonicBoom), October 19, 2026.

**Why it matters under load:** a graph planner that fuses norm, activation and quantization passes can move decode throughput without new kernels. One GPU, two model files and an unreproduced 0.94 on a 4060 Ti mean the number is still unconfirmed outside the maintainers' laptop.

## AMD ships GAIA 0.25, retiring ChatAgent in its local agent framework for Ryzen AI
URL: https://syntheticanvil.com/sparks/amd-gaia-0-25-local-agent-framework-ryzen-ai
Type: News brief (curated by agents, checked by the desk) · Section: Silicon
Source: https://github.com/amd/gaia/releases/tag/v0.25.0 (2026-10-18)
Summary: The Windows Python environment drops from about 0.9 GB to 0.1 GB, and 16 GB PCs no longer run out of memory on the desktop app's first launch.

Curated by agents · checked by the desk

AMD published GAIA 0.25.0 on GitHub on October 18, 2026. GAIA is the company's MIT-licensed, open-source framework for building and running AI agents locally on Ryzen AI hardware, and this release covers 818 commits since v0.24.1. The `gaia chat` command now runs what the release notes call the flagship GAIA agent, and the older ChatAgent is retired. On Windows, dropping PyTorch, transformers and accelerate cuts the desktop app's Python environment from about 0.9 GB to about 0.1 GB, according to the release notes.

`gaia talk` now handles transcription and speech through AMD's Lemonade local server, using Whisper and `kokoro-v1`, and the `[audio]` extra is gone. Lemonade Server moves to v2026.40.0. Before loading a model, GAIA now checks free memory and shrinks the context window to fit, down to a floor of 32K. If the model still won't fit, it reports how much memory it needs and what to close. PCs with less than 24 GB of RAM load the model when the first message arrives. `gaia init` picks Qwen3.6-35B-A3B on a Strix Halo with 64 GB or more, or on a 32 GB GPU. Everything else gets Gemma-4-E4B, and Qwen3.8 Flash Next is opt-in on 128 GB Strix Halo machines. Document and memory indexing now run on the GPU. Long turns keep going as long as they make progress, with a default no-progress limit of 75 minutes, set by `GAIA_STREAM_TIMEOUT`. DeepSeek V4.1 Flash is the default cloud model on the AMD LLM Gateway and Fireworks. The README lists a Ryzen AI 300-series processor and 16 GB of RAM as the minimum, recommends a Ryzen AI Max+ 395 with 64 GB, and supports Windows 11 and Linux.

Several changes break existing setups. The Agent UI now runs only the GAIA agent, and the Agent Hub home, the agent picker and custom-agent export/import are gone. The nomic embedder is removed. Saved memory is re-embedded on first start, and indexed documents are re-indexed once, so the first query after upgrading rebuilds the document cache. Skills that request more than their tier allows no longer load, even ones already on disk. AMD lists one known issue: Gemini models on the AMD LLM Gateway fail with the Hub-installed GAIA agent, and a fix is in review (#5006). For Strix Halo, the changelog sizes Windows iGPUs from the driver and turns off Vulkan coopmat on drivers that crash Qwen3.6.

Phoronix, which reported the release on October 19, 2026, notes that Linux users had reported kernel OOM kills on 16 GB systems before this fix. The release notes give no throughput figures for the new default models. They do report that a first "hello" on Qwen3.6 drops from about 43 seconds to about 21 seconds, which they attribute to caching a new chat's prompt as the chat opens. The README shows a macOS download badge, but its requirements table names only Windows 11 and Linux.

Source: [AMD (GitHub)](https://github.com/amd/gaia/releases/tag/v0.25.0), October 18, 2026.

**Why it matters under load:** A memory check that shrinks the context window instead of crashing makes 16 GB Ryzen AI laptops a workable floor for local agents, but fleets that upgrade should plan for a one-time re-embed and re-index, plus skills that stop loading.

## DeepSeek charges $0.75 per 1,000 agent search and fetch calls
URL: https://syntheticanvil.com/sparks/deepseek-search-fetch-per-request-pricing
Type: News brief (curated by agents, checked by Alessandro Moreira) · Section: Agents
Source: https://api-docs.deepseek.com/guides/search/ (2026-10-18)
Summary: The Search and Fetch APIs bill per successful request at 5 QPS per account, with paid metering starting November 1, 2026.

Curated by agents · checked by the editor

DeepSeek published the pricing page for its Search and Fetch APIs, read-only endpoints for agents and RAG applications, powered by its in-house search engine. Both bill per successful request, not by tokens: $0.75 per 1,000 requests. A request is billable only on HTTP 200 with a result, a non-empty search array or a fetched page. Failed requests, empty results and timeouts are not billed, and the count parameter, up to 50 results, does not change the price.

The limits matter for production. Search and Fetch each carry a 5 QPS ceiling per account, independent quotas, plus a per-domain QPS limit on Fetch. Over-limit traffic receives HTTP 429. The error codes define the failure modes worth handling: 403 for security-policy rejection on Fetch, 404 for pages blocked by site policy or with no extractable Markdown. Server-side tool calls through DeepSeek Harness, Claude Code or Codex hit these endpoints free until 00:00 Beijing time on November 1, 2026, when per-request billing starts. An agent that performs 40 searches per task costs about $0.03 per task at list price.

Source: [DeepSeek API Docs](https://api-docs.deepseek.com/guides/search/), October 18, 2026.

**Why it matters under load:** Per-request billing with no charge on failures moves agent RAG cost from token estimates to call counts, and a 5 QPS ceiling decides whether a fleet needs retry queues.

## Modders run the official DLSS 5 model on unsupported games
URL: https://syntheticanvil.com/sparks/dlss-5-neural-renderer-on-unsupported-games
Type: News brief (curated by agents, checked by Alessandro Moreira) · Section: Silicon
Source: https://www.tomshardware.com/pc-components/gpus/modders-used-the-official-dlss-5-release-on-unsupported-games-and-are-seeing-up-to-90-percent-better-performance-than-the-leaked-dlss-5-nvidia-says-new-nr-model-uses-20-percent-less-vram-and-processes-neural-workloads-up-to-2x-faster (2026-10-18)
Summary: Modders report up to 90 percent gain over the leaked build, while Nvidia states the new model uses 20 percent less VRAM.

Curated by agents · checked by the editor

Nvidia's latest DLSS Neural Rendering model, build 310.9.16.0, shipped inside NBA 2K27 on its October update. Modder Renan Maniero extracted it and released it for unsupported games. Comparisons come from community reports on X: Gaming Optimized measured up to 90 percent better performance than the previous NR model in The Witcher 3 with native DLSS 5, and broader modder comparisons show up to 40 percent. Nvidia's own figures for the new NR model: 20 percent less VRAM at 4K, neural workloads processed up to 2x faster, and a footprint cut of 24 percent to roughly 118 million parameters.

The numbers above are the modders' and Nvidia's own, and none has been independently reproduced yet. A related project, a solo port of the full DLSS feature set to RDNA2 through RDNA4 cards, ran in the same week's coverage and is tracked separately.

Source: [Tom's Hardware](https://www.tomshardware.com/pc-components/gpus/modders-used-the-official-dlss-5-release-on-unsupported-games-and-are-seeing-up-to-90-percent-better-performance-than-the-leaked-dlss-5-nvidia-says-new-nr-model-uses-20-percent-less-vram-and-processes-neural-workloads-up-to-2x-faster), October 18, 2026.

**Why it matters under load:** DLSS gains measured on modder builds are not gains on a production machine, and the version drift between the leaked and official models changes any benchmark someone copies from X.

## Five devices over Ethernet and USB-C run one 512-expert model
URL: https://syntheticanvil.com/sparks/backburner-five-device-cluster
Type: News brief (curated by agents, checked by Alessandro Moreira) · Section: Silicon
Source: https://www.reddit.com/r/LocalLLaMA/comments/1x8ley0/2_gaming_pcs_an_m4_pro_macbook_over_ethernet_2/ (2026-10-17)
Summary: A user reports 37 to 39 tok/s on Qwen3.8 Flash Next at 60k context across two PCs, one MacBook and two iPhones.

Curated by agents · checked by the editor

On October 17, 2026, a user on r/LocalLLaMA chained five machines into one inference pipeline for Qwen3.8 Flash Next, a 48-layer mixture-of-experts model with 512 experts per layer. Two gaming PCs, an RTX 2060 Super and an RX 9060 XT, an M4 Pro MacBook, and two iPhone 17 Pro Maxes. The PCs and the Mac talk over 1 GbE Ethernet, the phones over 10 Gb/s USB-C. Measured at the server: 37 to 39 tok/s write at 60k context, 856 to 895 tok/s prompt read, about 0.5 s to start a cached follow-up turn.

The mechanism is pipelined speculation. A draft head on PC 1 guesses the next tokens, the chain verifies them in one pass, and PC 1 drafts the next batch while that pass travels. Each step lands about 2.2 tokens on average. Layers are split by device, with the Mac serving as expert cache for the phones. The 60k layout caps at 69.6k context on PC 2's 16 GB; a second layout read one prompt past 164k tokens and writes 31 to 33 tok/s at 60k. The author notes the on-screen prefill counts cached prompt tokens, so it reads high. Repo is github.com/StayLameBro/backburner, not posted yet.

Source: [r/LocalLLaMA](https://www.reddit.com/r/LocalLLaMA/comments/1x8ley0/2_gaming_pcs_an_m4_pro_macbook_over_ethernet_2/), October 17, 2026.

**Why it matters under load:** Distributed inference over hardware already on the desk changes fleet sizing decisions, but latency, not device count, sets the throughput ceiling.

## Fish Audio Drama 3 runs on a 16 GB Radeon
URL: https://syntheticanvil.com/sparks/red-curtain-fish-drama-3-on-16gb-radeon
Type: News brief (curated by agents, checked by Alessandro Moreira) · Section: Studio
Source: https://www.reddit.com/r/LocalLLaMA/comments/1x8kces/fish_audio_drama_3_says_it_needs_a_48_gb_nvidia/ (2026-10-17)
Summary: Red Curtain ports the NVIDIA-only 35B MoE to ROCm with experts cached from RAM: 11 GB VRAM, speech slower than realtime.

Curated by agents · checked by the editor

Fish Audio's Drama 3 voice model lists an NVIDIA GPU with 48 GB as its requirement. On October 17, 2026, a user on r/LocalLLaMA posted Red Curtain, a port that runs it on an RX 9070 with 16 GB. Drama 3 is a 35B mixture-of-experts with about 3B active parameters per token. The FP8 experts, about 32 GB, stay in system RAM, and only the ones a token actually uses are cached on the GPU. Everything else runs in BF16 on the card. The author's numbers: load around 17 s, 3.3 s of speech generated in about 13 s, 11.6 s of speech in about 37 s, 11 to 12 GB VRAM and 35 GB RAM.

Two facts for operators. First, the official inference script is NVIDIA-specific, the FP8 path uses NVIDIA kernels and ROCm is not supported, so a 48 GB Radeon could not run the stock release at all. This port is the first path to ROCm. Second, output is slower than realtime, usable for short takes, not for batch delivery. The repo ships a small web UI with voice cloning, multi-speaker scripts and Fish's tags. A known failure mode, a take going silent after the first line, exists in the upstream recipe too; the author reports top-k off and per-speaker reference voices as mitigations. Tested on gfx1201 only. Weights come from Hugging Face, not included.

Source: [r/LocalLLaMA](https://www.reddit.com/r/LocalLLaMA/comments/1x8kces/fish_audio_drama_3_says_it_needs_a_48_gb_nvidia/), October 17, 2026.

**Why it matters under load:** A studio pipeline that was locked to a 48 GB NVIDIA card now runs on a 16 GB AMD workstation, at the cost of realtime throughput.

## A 552B MoE runs on one RTX 4090 at 27 tokens/s
URL: https://syntheticanvil.com/sparks/xolotl-552b-on-a-single-4090
Type: News brief (curated by agents, checked by Alessandro Moreira) · Section: Silicon
Source: https://www.reddit.com/r/LocalLLaMA/comments/1x8m0jj/xolotl_strata_based_deepseekv41flash_552b_on_a/ (2026-10-17)
Summary: A community engine spreads DeepSeek-V4.1-Flash across VRAM, pinned RAM and NVMe, holding 27 tok/s decode on one 24 GB card.

Curated by agents · checked by the editor

On October 17, 2026, a user on r/LocalLLaMA published Xolotl, an inference engine based on Strata that runs the full DeepSeek-V4.1-Flash, 552B parameters, on a single gaming PC: one RTX 4090 with 24 GB, a Ryzen 7 5700X, 90 GB of DDR4 and one NVMe drive. Weights sit across VRAM, pinned RAM and NVMe, and the engine loads only the experts each token needs. The author reports 27 tok/s decode, 180 to 320 tok/s prefill, 512K context, and 21/21 HumanEval and 10/10 tool calls through the real server with thinking on. The same engine runs GLM-5.3-Flash, Qwen3.8-Flash-Next and Qwen3.8-27B.

The quant is 152 GiB. The Engram tables, about 200 GB, stay off RAM. The author says they are sensitive to random read patterns more than raw disk speed: exFAT serialized parallel reads at about 13,000 reads/s and cost roughly 10 ms per token, NTFS brought that to about 1 ms. Routed experts carry mixed 1, 2 and 3 bit quant, the dense part runs at Q8 with a Q6 experiment claiming +15% decode. Full residency needs 150 to 160 GB of RAM for the quant plus headroom. Multi-GPU is not implemented. The author's own benchmark against the API reports similar quality with three to ten times the thinking tokens per result.

Source: [r/LocalLLaMA](https://www.reddit.com/r/LocalLLaMA/comments/1x8m0jj/xolotl_strata_based_deepseekv41flash_552b_on_a/), October 17, 2026.

**Why it matters under load:** A 552B MoE answers agent traffic on one consumer card when the engine tolerates PCIe and storage latency, which moves the build decision from VRAM size to memory bandwidth and random-read IOPS.

## NVIDIA fits a 74B MoE in 24 GB with native 2-bit weights
URL: https://syntheticanvil.com/sparks/nemotron-3-5-bolt-74b-24gb
Type: News brief (curated by agents, checked by Alessandro Moreira) · Section: Silicon
Source: https://blogs.nvidia.com/blog/nemotron-3.5-super-vl (2026-10-15)
Summary: Nemotron 3.5 Bolt 74B-A9B runs locally on 24 GB via quantization-aware 2-bit training, with llama.cpp support; the model card lists a 256K context and NVIDIA's OpenMDW-1.1 license.

Curated by agents · checked by the editor

NVIDIA released the Nemotron 3.5 family on October 15, 2026: Super VL, an open 120B model for always-on agents, plus Bolt 74B-A9B 24GB, available now, and Bolt E4B 4GB, scheduled for October 23. A r/LocalLLaMA recap of four open-weights drops in 72 hours picked Bolt as the only one that fits in 24 GB, with all figures taken from the official repos and model cards. NVIDIA claims Bolt is the fastest open agentic model in its class, 5x faster than the next best on the Artificial Analysis throughput chart, and the top open model in its class on PinchBench.

The model card details matter for local builds (the blog post names the model and the 24 GB target; license and context come from the card). Architecture is a Mamba-2-Transformer hybrid LatentMoE, 74B total and 9B active, compressed from Super VL, with IQ2 2-bit quantization trained with quantization-aware distillation and some layers kept at NVFP4 or Q8_0. Context runs to 256K tokens. License is OpenMDW-1.1, NVIDIA's own permissive license, not Apache or MIT. Runtime support includes llama.cpp, Ollama, LM Studio, Unsloth and vLLM. vLLM deployment is listed for A100, H100 and Blackwell. Training data and recipes are open on Hugging Face.

Source: [NVIDIA](https://blogs.nvidia.com/blog/nemotron-3.5-super-vl), October 15, 2026.

**Why it matters under load:** it is the first vendor-sized open model that fits a 24 GB desktop without offloading, and the license is permissive enough for commercial pipelines on the same hardware.

## Latent reasoning agents cut tokens 35.5% and run 2.6x faster
URL: https://syntheticanvil.com/sparks/hybrid-reasoning-agents-token-cut
Type: News brief (curated by agents, checked by Alessandro Moreira) · Section: Agents
Source: https://arxiv.org/abs/2610.18861 (2026-10-13)
Summary: Jiaru Zou et al. report 10.4% better scores on 11 benchmarks and token cuts of 35.5% to 54.7%, with inference 1.8x to 2.6x faster.

Curated by agents · checked by the editor

Hybrid Reasoning Agents, submitted to arXiv on October 13, 2026 by Jiaru Zou et al., mix latent reasoning with text-based action inside one generation process. A lightweight HybridLink switches between text mode and latent mode, and a continuous working memory keeps hybrid context across turns. Post-training is split in two: HybridSFT stabilizes tool-integrated generation, HybridRL learns when to think in latent space and when to act through text.

Numbers from the paper, across three model scales and 11 benchmarks covering math, science, medicine, search and agentic reasoning: consistent performance gains of 10.4%, token reductions between 35.5% and 54.7%, inference 1.8x to 2.6x faster, cost savings of 2.7x to 3.7x against frontier LLM agents and frameworks. Code is published at github.com/togethercomputer/HybridAgent with a Hugging Face collection. The signal is strong in the community: the HN thread reached 283 points with 156 comments, and a top r/LocalLLaMA post picked up the same numbers from the official repos.

Source: [arXiv](https://arxiv.org/abs/2610.18861), October 13, 2026.

**Why it matters under load:** token cost per agent run is the bill. A measured 35.5% to 54.7% reduction with faster inference changes the cost curve for fleets running tool-heavy loops.

## Harness2 adds 11.5 points to agent harnesses without ground truth
URL: https://syntheticanvil.com/sparks/harness2-agent-harness-optimization
Type: News brief (curated by agents, checked by Alessandro Moreira) · Section: Agents
Source: https://github.com/google-research/harness2 (2026-10-06)
Summary: Google open sourced a framework that edits an agent's prompt, tools, memory and subagents while the agent works, with gains up to 11.5 points.

Curated by agents · checked by the editor

Google Research open sourced Harness2 under Apache-2.0 (arXiv 2610.14224, paper on October 9, 2026). The framework treats the harness as an optimizable object with eight editable components: system prompt, guardrails, memory, tool guidance, subagents, skills, scripts and plugins. Task-level recursion proposes edits, probes them on the same task, and composes a refined harness from behavioral contrasts between executions, without ground-truth feedback. A second level keeps adopted harnesses and lessons in a persistent improvement harness. A single step improves GLM-5 and Gemini 3.5 Flash over their base harnesses across four model-harness configurations: up to 11.5 points on WorkBuddy-Bench, 4.5 on JobBench, 11.8 percentage points on LAB's partial pass rate.

The limits for builders: Linux, Python 3.12 and uv. Model-backed runs need Node.js 20+, Google Cloud CLI and a Vertex AI project. WorkBuddy-Bench requires Docker, LAB requires Pandoc and Poppler. The local demo runs both recursion levels with no model credentials. OpenCode and Codex executors are supported. The README states the project is not an officially supported Google product, and the judge is a separate model configured through Vertex.

Source: [Google Research](https://github.com/google-research/harness2), October 6, 2026.

**Why it matters under load:** harness quality becomes a runtime variable. Teams can measure prompt and tool gains per task on fixed weights, paid for in extra tokens spent improving.