Notes from my October liked tweets and GitHub stars. Wildest engineering story this month was Anthropic having to replace standard Git on their monorepo coz coding agents were merging 30,000+ changes a day, plus a ton of practical lessons from PostHog’s AI team and new local NVMe inference engines.
Main takeaways from October
- At 30,000 agent merges/day, standard Git servers melt. Anthropic shared details on Scion, their internal source-control replacement. With Claude writing ~90% of Claude Code, monorepo merges hit 30,000+ per day and CI checkouts hit 25M/day, saturating traditional Git packfile negotiation. Scion cut source-control CPU and RAM usage by 200x.
- Hard-cap agent review-and-fix loops at 3 rounds. Anthropic’s internal code review agents lifted substantive review comments from 16% to 54%, which is great - until you hook a review agent directly to an auto-fix agent with no turn limit. They had one PR where the reviewer and fixer argued back and forth for 50+ rounds overnight burning tokens. Cap automated review/fix cycles at 2-3 rounds, then escalate to a human.
- One sandboxed SQL read tool beats 20 narrow REST tools. In PostHog’s writeup on “38 things we’ve learned about building AI products” [1], their biggest unlock was replacing dozens of specialized read endpoints with a single read-only SQL/HogQL tool. Questions that used to take 4 chained tool calls collapsed into 1 query.
- Keep a compact 8KB docs index in context instead of relying only on
SKILL.mdtriggers. When a framework ships breaking changes after model cutoff (like Next.js 16), agents often don’t know what they don’t know - in evals, agents skipped calling the docs skill 56% of the time coz they assumed their pretrained knowledge was fine [2]. Putting a compressed 8KB map of the docs directly into always-on context pushed accuracy to 100%. - Three rules for scheduled/cron agents. Also from Anthropic’s automation notes:
- Read from a persisted cursor/bookmark, never a rolling “last 24h” window (otherwise a brief outage silently drops events).
- Never let an expired OAuth token or empty API error get summarized as “nothing new today!” - fail loud on read errors.
- Re-fetch the live ticket/PR state right before posting a comment so your agent doesn’t reply to an issue a human closed 4 minutes ago.
Decoupled cloud agents & high-throughput setups
Everyone is converging on the same architecture for cloud agents: split the Brain (lightweight durable state machine), Hands (ephemeral sandbox VM), and Drives (network-mounted workspace).
pi-durableon Rivet Actors: keeps idle waiting agents at ~1.3 MB of RAM instead of paying for a paused container while waiting on human approval or slow webhooks.- OpenAI’s GPT-6 dead-code sweep: OpenAI ran background maintenance agents across their own internal repos and merged 1,400+ PRs deleting 800,000+ lines of dead code in 2 weeks.
- Solo 1,000+ PRs/week setup:
@navuudshared a wild solo operator rig running 50oh-my-piagents across a home Linux box and 4 Mac Minis with stacked diffs (pstack), Linear ticket routing, and a 24-hour production error watcher that auto-reverts suspect commits.
Generative UI & open-weight decision models
- Streamed native UIs over markdown chat: OpenAI shipped GPT-6 Intelligent UI, Thesys released OpenUI 1.0 + OUI-1 (a diffusion UI model trained with parser-as-reward), alongside Vercel’s
json-renderand Google’sA2UI. Instead of dumping a 600-word markdown table, the model streams a constrained JSON schema that renders interactive filters, charts, and forms directly in the client. - Open-weight System One models: if you want sub-50ms routing/classification on your own GPUs or CPUs without calling an external API, check out Stanford/NVIDIA’s CLM-8B (hits 32ms latency by pre-caching action embeddings separately from state [3]) and Fastino’s GLiNER2.5-Decide (a 340M parameter decision encoder that runs fast on CPU [4]).
Starred GitHub repos from October
- prabanta-dev/janas - pure C inference engine (
Janas-LLM) that streams active MoE expert weights straight from NVMe SSD viaO_DIRECT. RunsQwen3-Next-80B(48 GB on disk) on a 32 GB RAM laptop at 37 tok/s vs 2.8 tok/s whenllama.cppthrashes OS page cache. - experientiallabs/experiential - open-source LLM gateway (
exp) that captures your Claude Code / Codex OTel traces, builds a replay simulator from your real repo tasks, and trains a custom router or fine-tuned smaller model - manthanguptaa/water - clean Python agent harness framework (
water-ai) with explicit DAG flows, approval gates, circuit breakers, and trace replay - bergside/typeui - MCP server +
DESIGN.md/SKILL.mdlibrary that gives coding agents concrete typography, color tokens, and layout variations so generated frontends stop looking like default Tailwind slop - one2nc/ai_observability - super helpful comparison repo that instruments the exact same RAG + agent app five ways (vanilla OpenTelemetry, OpenLLMetry, OpenLIT, Bifrost, and Langfuse) so you can compare trace output before committing to a stack
- OrchestratorInc/agent-orchestrator - local desktop Kanban + Git worktree manager for supervising parallel Claude Code and Codex workers from spec to merge