01
A single MCP server + CLI (npx rea-agents setup) that hands a coding agent (Claude Code, Codex, Cursor, Copilot, Gemini CLI, OpenCode…) decompilation and tracing tools for native binaries, Electron apps, .NET assemblies, Android APKs, firmware, websites, and HAR captures. The agent decompiles, traces a feature, returns evidence with caveats — fully local, the binary never leaves your machine. #1 on GitHub Trending today; ~188.8k stars, roughly 167k of them in the last 30 days — one of the fastest-growing repos GitHub has ever seen. REA 4.1 (Oct 6) added APK analysis via JADX, firmware via Binwalk/Unblob, and IDA Pro as a backend. MIT, TypeScript.
Local-first, MCP-native, built for exactly your agent-harness world — and growing faster than almost anything in GitHub history. The 4.1 APK/firmware additions turn it from a demo into a toolbox. This is the repo to clone this week.
02
A local MCP server that intercepts tool output before it floods an agent's context — sandboxed execution returns lightweight pointers instead of raw payloads (claims up to 98% context reduction), persists session memory in SQLite FTS5, and installs lifecycle hooks plus a routing skill across 17 platforms (Claude Code, Codex, Copilot, Cursor, OpenClaw, Zed…). #3 on GitHub Trending today; ~27.7k stars and climbing steadily. TypeScript.
Context amnesia is the #1 killer of long agent sessions, and this attacks it at the plumbing level. Speaks directly to your trajectory-logging and calibration work — the underconfidence canary is, at heart, a context-cost measurement.
03
A layer-sharded inference library that streams model weights one layer at a time from disk — absurd-scale models on tiny GPUs with no quantization: 70B on 4GB VRAM, Kimi K3 (2.8T) in 3.72GB, DeepSeek-V3 (671B) in ~12GB, Qwen3.8-Flash-Next (125B) in 5.95GB. A September update added training huge models on small VRAM (125B under 6GB). #7 on GitHub Trending today; ~38k stars. Python, Apache-2.0, one-line pip install.
This is the VRAM math you live for — and the layer-split philosophy you already endorsed over tensor split, running in production. The Kimi K3-on-3.72GB trick reframes your "biggest model fitting ~30GB" directive entirely. Keep one eye on this during the Glimmer 30B eval.
04
Microsoft's official framework for 1.58-bit (ternary) LLMs: hand-tuned kernels delivering 2.4–6.2× speedups and up to 82% energy savings on x86 CPUs — a 100B BitNet model runs on a single CPU at human-reading speed. Also ships the official BitNet-b1.58-2B-4T model, 1-bit embedding models (0.6B, 270M), and GPU kernels. #8 on GitHub Trending today with a steady 72h resurgence; ~41.1k stars. C++/Python, MIT.
The most radical answer to your VRAM ceiling: if models go 1-bit natively, the 29.4GB math stops being the binding constraint. A 100B model at reading speed on bare CPU is the kind of result that makes GPU shopping look quaint. Watch it for the d1-3B test's sake.