Agents broke Git at Anthropic, and the fix for prompt drift turns out to be a pre-commit hook.
Top Signal
Anthropic replaced Git internally because agents outpaced it
workflow
Simon Willison, HN Front Page
Anthropic published an engineering post on why and how it built a custom alternative to Git, driven by the dramatic increase in the rate of code changes now that agents author most of the work. The builder takeaway is not the tool — it is the diagnosis. Git's model assumes human-paced branching and review: a few long-lived branches, commits arriving at reading speed. Fleets of agents produce many concurrent, short-lived, machine-authored change sets, which moves the bottleneck from writing code to merging, reviewing, and reasoning about history. Treat this as a forecast of your own constraint. Start measuring commits and PRs per author type; keep agent-generated changes small and independently verifiable; move toward stacked diffs and server-side review tooling before your main branch becomes a queue. Pair with the Huntley item below: enforcement belongs in hooks and CI, not in prose your agent may ignore.
Read more →
Fast Signals
Huntley: enforce agent rules with pre-commit hooks, not AGENTS.md
workflow
Simon Willison
Geoffrey Huntley's point: updating AGENTS.md to tell an agent to use your diagnostics library still leaves a delta that drifts. Instead he writes a pre-commit hook that greps the git diff for direct calls bypassing his observability module, so the rule becomes a failing check rather than a suggestion. Cheapest high-leverage change you can ship today — convert your three most-ignored agent instructions into hooks or CI assertions.
Link →
Tencent open-sources an agent memory layer that runs on local SQLite
new tool
r/LocalLLaMA
Tencent released an agent memory system that runs entirely locally with SQLite as the store — no vector service, no hosted memory API. That covers the default dependency most agent stacks reach for a managed startup to solve. Worth a weekend spike if you are currently paying for hosted memory or hand-rolling a retrieval layer over conversation history.
Link →
AnythingLLM drops Ollama for Lemonade and llama.cpp
platform change
r/LocalLLaMA
AnythingLLM wrote up why it is migrating its local inference backend off Ollama to Lemonade plus llama.cpp directly. Lemonade is the under-covered name here — an inference server with broader hardware backends than Ollama exposes. If you built on Ollama as a convenience layer, read the migration rationale before your backend choice calcifies.
Link →
web-edit: edit secrets from your phone without feeding them to the LLM
new tool
Simon Willison
Simon Willison shipped web-edit (0.1a0, then 0.1a1) after hitting a real agent-workflow problem: he needed to edit a credentials file while working from his phone via Codex Remote, and did not want those credentials round-tripping through the model's context. Small tool, precise problem — bookmark it for any remote agent setup that touches config files containing keys.
Link →
Gemini 4 Argon ships with a robotics variant; llm CLI support is live
platform change
HN Front Page, Simon Willison
Google released Gemini 4 Argon alongside a dedicated Gemini 4 Argon for Robotics model, both hitting the HN front page. llm-gemini 0.35 already added support, so you can benchmark it from the CLI today rather than waiting on SDK updates. The robotics branch is the more interesting half — a flagship-tier model targeted at embodied control, not chat.
Link →
LiquidAI LFM2.5-24B-A2B: 24B total, 2B active
new tool
r/LocalLLaMA
Liquid AI released LFM2.5-24B-A2B, a sparse MoE with roughly 2B active parameters per token. That ratio is the point: near-24B-class quality at active-parameter latency, which fits consumer VRAM and CPU-offload setups that cannot run a dense 24B at usable speed. Test it if you are hunting for a local model that holds up under agent loops.
Link →
Python 3.15's sampling profiler, applied to a real codebase
workflow
Simon Willison
Willison put Python 3.15's new sampling profiler on web-edit and published the flame graphs and per-source-line heatmaps as a reproducible research repo. This is the show-don't-tell version of the 3.15 release notes — a concrete recipe for profiling a live Python service with no instrumentation overhead. Copy the workflow next time an LLM-serving endpoint mysteriously stalls.
Link →
Radar
Qwen 27B at ~20 tok/s on a jailbroken PS5 GPU
Someone got a 27B model serving at usable speed on PS5 silicon, extending the hunt for cheap VRAM beyond mining cards and workstation GPUs. Not a recommendation, but a signal of how far the consumer-hardware arbitrage is being pushed.
Link →
Dyna-2: physical agents with hour-long autonomy
Dyna Robotics walked through Dyna-2 on Latent Space with a live robot demo, pitching hour-long autonomous task horizons. Long-horizon reliability is the same wall software agents hit, so the failure modes they describe transfer even if you never touch hardware.
Link →
One HN front page, then a flood of AI crawler traffic
A developer documented their site being hammered by AI bot traffic immediately after an HN appearance. Budget for crawler load as a launch cost, and decide your robots.txt and rate-limit posture before you post, not after.
Link →
Convergence Watch
gemini 4 argon
3 mentions across HN Front Page, Simon Willison
Two HN front-page entries plus same-day llm-gemini plugin support means tooling landed with the launch. The robotics variant shipping alongside the flagship suggests Google now treats embodied control as a first-class model target, not a research spinoff.
local hardware capex
TRENDING
2 mentions across r/LocalLLaMA
Present 4 of the last 7 days, today via a PS5 GPU inference build and a thread on buying smart TVs. With 5090 supply constrained and prices spiking, builders are scavenging any silicon with usable memory bandwidth. Expect weirder deployment targets in your support matrix.
embodied agents
2 mentions across HN Front Page, Latent Space
Gemini 4 Argon for Robotics and Dyna-2's hour-long autonomy demo landed the same day from independent sources. Both bet that the hard problem is sustained multi-step execution, not perception. The long-horizon reliability techniques will leak back into software agent harnesses.
1-bit quantization
TRENDING
1 mentions across GitHub Trending
microsoft/BitNet trending again follows littlebit's latent-factorization quantization (Oct 8) and Boole-1.7B (Oct 12). Three independent low-bit efforts inside a week, with the reference inference framework re-climbing trending, points to sub-2-bit moving from paper to deployable this quarter.
SOURCE DOWN: HN Show returned 0 items