Codex CLI backgrounds itself by default, HN sours on agents, and open models go vertical.
Top Signal
Codex CLI ships a persistent self-updating daemon by default
platform change
HN Front Page
An openai/codex issue (#48195) reporting that Codex CLI installs a persistent, self-updating background daemon without opt-in hit 414 points on HN today. The builder consequence is not the daemon itself but the trust model: an agent CLI that keeps a resident process and updates itself out-of-band executes code on your machine that you never reviewed, on a schedule you don't control. That breaks version pinning, defeats reproducible dev images, and widens the supply-chain surface on the one box that holds your prod credentials. Today: check for stray launchd/systemd units and listening ports after installing any agent CLI, pin the CLI version in your toolchain lockfile or Dockerfile, disable auto-update if the flag exists, and read the issue thread before upgrading. Longer term, treat agent CLIs as privileged software with the same install review you'd give a browser extension — the category is normalizing background residency fast.
Read more →
Fast Signals
QwenGyre: RL framework for long-horizon agent training
new tool
r/LocalLLaMA
Qwen released QwenGyre, an RL framework aimed specifically at training agents on extremely long, complex tasks — the regime where most open RLHF tooling falls over on credit assignment and rollout cost. If you've been hand-rolling reward shaping for multi-hour agent trajectories, read the design before building more scaffolding. Bookmark even if you don't train models: the rollout/eval harness shape is reusable.
Link →
Decision 3.0 lands open decision models from 0.6B to 27B
research to practice
r/LocalLLaMA
An open, multimodal decision-model family spanning 0.6B to 27B claims #1 on both Jev Decision Index boards. The 0.6B end is the interesting part: a routing/triage model small enough to run inline in a request path instead of calling a frontier API. Decision models have now appeared in our feed on five of the last six days — this is the week's most durable signal.
Link →
GLM-Legal continues the vertical open-weight model run
emerging signal
HN Front Page
Z.ai shipped GLM-Legal, a domain-specialized model in the GLM line, to 391 points on HN. Paired with openmed 3.0 (clinical, Apache-2.0) and the aescode/Mellum code models from the last five days, the pattern is clear: vertical open weights are arriving faster than general ones. If you ship into a regulated domain, the build-vs-prompt math just changed — a specialized open model you can host beats a general API you must send documents to.
Link →
MiniCPM-V 4.7 ships in 35B-A3B and 1B sizes
new tool
r/LocalLLaMA
OpenBMB dropped two vision-language models the same day: a 35B MoE with ~3B active params and a 1B. The A3B config is the one to test — 35B-class capability at roughly 3B-param inference cost makes document and screenshot pipelines viable on a single consumer GPU. Benchmark the 1B for on-device OCR/classification before paying per-image API rates.
Link →
262k context plus vision on 16GB VRAM at 80 tok/s
workflow
r/LocalLLaMA
A reproducible config: unsloth/Qwen3.8-27B-UD-IQ4_XS with 262k context at q4_0 KV cache and vision enabled, on 16GB VRAM, hitting 80 tok/s generation and ~1500 tok/s prefill. The q4_0 KV quantization is what buys the context length — copy the flags directly. This is the clearest evidence yet that long-context agent loops don't require a datacenter card.
Link →
Intel Crescent Island becomes D-series with 480GB LPDDR5X
platform change
r/LocalLLaMA
Intel's inference GPU got its product name and a headline spec: up to 480GB of LPDDR5X. Capacity-over-bandwidth is a deliberate bet on serving large MoE models where most weights sit idle — exactly the workload where VRAM, not FLOPS, is the wall. Watch the software stack, not the spec sheet: without working llama.cpp/vLLM paths this stays a slide.
Link →
Python 3.15 lands and 3.10 going EOL raises your floor
platform change
Simon Willison
Willison's take on the release is the actionable part for library authors: with 3.10 out of support, you can finally set requires-python to >=3.11 and use tomllib, exception groups, and asyncio TaskGroups unguarded. 3.15 is already in actions/python-versions, so add it to your CI matrix now and drop the 3.10 row. Do both in one PR while the dependency floor is moving anyway.
Link →
Meta research ships Muse Wonder to the top of HN
emerging signal
HN Front Page
Meta's research blog post on Muse Wonder was the day's highest-voted item at 493 points with 266 comments. We're flagging the signal, not summarizing it — the post is the source and the comment thread is where the capability claims get stress-tested. Read it directly before the newsletter cycle reframes it.
Link →
Radar
Boole-1.7B: 1-bit Qwen3-1.7B beating Bonsai-1.7B
A 1-bit quantization of Qwen3-1.7B that claims to outperform a comparable small model, continuing the ultra-low-bit thread from littlebit last week. Worth watching because 1-bit at this size is where edge deployment stops needing a GPU at all.
Link →
Leaderboard that filters to models your machine can run
An open-source leaderboard that takes your hardware and shows only the models you can actually serve — inverting the usual benchmark table that ignores VRAM. Solves a real daily problem for anyone running local inference, from an individual dev rather than a lab.
Link →
PS2 games statically recompiled to WebAssembly
Static recompilation of PS2 binaries into WebAssembly rather than emulation, meaning native-ish speed in a browser tab. The technique generalizes well beyond games if you ever need to lift legacy binaries into a sandboxed runtime.
Link →
WiFi 7 router repurposed as a 320Msps SDR receiver
A WiFi 7 router's radio exposed as a 320 Msps software-defined radio front end — commodity hardware delivering capability that cost thousands. The pattern to notice is firmware-level repurposing of consumer silicon, the same move driving this month's salvage-GPU builds.
Link →
Convergence Watch
decision models
TRENDING
1 mentions across r/LocalLLaMA
Fifth appearance in six days, previously across Simon Willison, HN Front Page, and r/LocalLLaMA simultaneously. OpenAI's Decisions API, Microsoft's and H2O's entries, and now an open 0.6B-to-27B family means the category is consolidating into a real primitive. If you route or triage with a frontier model today, a small decision model is about to be the cheaper default.
local hardware capex
TRENDING
3 mentions across r/LocalLLaMA
Five of the last seven days. Today: Intel's 480GB D-series, an RTX 5080 24GB rumored for Q1 2027, and CUDA-moat laptops selling out. Single-source so far, but the direction is consistent — VRAM capacity is the scarce resource and vendors are finally pricing for it. Delay discretionary GPU buys; the 24GB-plus consumer tier is about to get crowded.
qwen3.8
TRENDING
2 mentions across r/LocalLLaMA
Fifth day in seven, now shifting from release chatter to deployment recipes — 262k context with vision on 16GB VRAM, plus head-to-head frontier comparisons. That transition from 'announced' to 'tuned configs posted' is the reliable sign a model has become a default. Treat Qwen3.8-27B as the local baseline to beat.
domain-specific open-weight models
TRENDING
1 mentions across HN Front Page
GLM-Legal today, openmed 3.0 clinical models and Microsoft's aescode yesterday, Mellum 2.1 four days ago. Four verticals in five days from four independent labs. The strategic read: labs are competing on domain depth now that general open weights are commoditized, which makes self-hosting viable for exactly the regulated use cases that couldn't use APIs.