Local LLMs, Claude Code, and Agent Efficiency: Real Tools for Real Builders

Today's findings

1. #1 RAGless: Local FAQ system with no cloud dependency at query timerepo

   Semantic FAQ system that uses LLMs only during ingestion, not at query time, running fully offline with Ollama.

   RAG vs RAGless

   Why RAGless wins for closed-domain FAQs

   vs

   Traditional RAG

   RAGless

   LLM at query

   Generation

   Retrieval only

   Latency

   High

   Low

   Cost

   Per-query API

   Zero at query

   Hallucination

   Possible

   None

   Offline

   Cloud needed

   Fully offline

   Traditional RAG wins the row RAGless wins the row

   RAGless moves LLM generation to ingestion, eliminating latency, cost, and hallucination at query time.

   Why it matters: For closed-domain use cases, generation at query time adds latency, cost and hallucination risk without adding value. RAGless removes it.

   How to apply: Use for internal knowledge bases, customer support tools, or documentation systems where answers are predefined. Supports PDF, TXT and Markdown. Works fully offline with Ollama.

   raglocalollamaagents

   Read more: RAGless – what if you skip the generation step entirely? · RAGless – local FAQ system, no cloud dependency at query time · RAGless: Q-Q retrieval with score aggregation for closed-domain FAQ [P] · RAGless – FAQ retrieval without an LLM at runtime

2. #2 browser-search: Three tools, zero cost, and your AI agent learns to search and browse the webrepo

   Three open source tools orchestrated by a skill, fully self-hosted, to give AI agents web search and browsing capabilities.

   browser-search

   Three zero-cost tools for web-capable AI agents

   SearXNG Metasearch engine

   Camofox REST API browsing

   CloakBrowser Cloudflare bypass

   Tool

   Orchestrate with a skill for full web autonomy.

   Why it matters: AI agents like Claude Code and Cursor struggle with web search due to Cloudflare blocks, JavaScript-heavy sites, and API costs. browser-search solves this with zero-cost tools.

   How to apply: Use SearXNG for metasearch, Camofox for REST API browsing, and CloakBrowser for Cloudflare bypass. Orchestrate with a skill for full web autonomy.

   agentsmcptoolsweb

   Read more: browser-search — three tools, zero cost, and your AI agent learns to search and browse the web

3. #3 Terminal Pilot: A lightweight terminal-first AI CLI built in Pythonrepo

   A terminal-first AI CLI that brings AI capabilities directly to your command line.

   Tool Release

   Terminal Pilot: A lightweight terminal-first AI CLI built in Python

   Terminal Pilot

   tool Python CLI

   Built in Python2025

   GitHub

   runpip install terminal-pilot

   Bring AI capabilities directly to your terminal.

   Why it matters: For developers who live in the terminal, having AI capabilities directly accessible via CLI can significantly streamline workflows without context switching.

   How to apply: Install Terminal Pilot and use it to run AI commands directly from your terminal. Useful for quick tasks, scripting, and automation without leaving your command line environment.

   clitoolsterminalagents

   Read more: Terminal Pilot – A lightweight terminal-first AI CLI built in Python

4. #4 Dynamic MCP Router: Real-time tool routing to prevent agent bloattechnique

   Routes tool queries in real-time instead of dumping all JSON schemas into the system prompt, preventing context window bloat and semantic confusion.

   MCP tool routing

   Dump every schema vs route on demand

   Prompt-stuffing

   • All tool JSON in system prompt
   • Context window bloat
   • Semantic confusion, retrieval decay

   vs

   Dynamic router

   • Search index over tools
   • Routes queries in real time
   • Lean prompt, sharper recall

   Gateway fetches the right tool instead of front-loading them all

   Cuts agent bloat that degrades local LLM tool retrieval

   Why it matters: Local LLMs suffer from retrieval degradation when system prompts contain too many tool descriptions. Dynamic routing solves this.

   How to apply: Implement a lightweight, dynamic tool gateway that connects to downstream servers over HTTP/SSE, compiles a search index, and routes queries in real-time.

   mcpagentslocaltools

   Read more: Dynamic mcp router · Stop shoving 50 tools into your local Llama context. It’s making your agent slow and stupid.

5. #5 Built a self-improving coding agent with early exit logicrepo

   Saves 40% tokens by knowing when to quit, using Ollama + LangGraph, fully local.

   Early-exit agent

   Knowing when to quit cuts token spend

   40%

   fewer tokens per run

   same output quality

   Local

   runs on Ollama, no API

   LangGraph

   early-exit conditions in the graph

   Stop signal

   halts on goal met / diminishing returns

   Self-improving coding agent halts once further work stops paying off.

   Why it matters: AI agents often burn tokens on unnecessary work. Early exit logic cuts costs while maintaining quality.

   How to apply: Implement early exit conditions in your agent workflows to stop processing when goals are met or further work yields diminishing returns.

   agentsollamalanggraphlocal

   Read more: Built a self-improving coding agent with early exit — saves 40% tokens by knowing when to quit [Ollama + LangGraph, fully local]

6. #6 vault-engine: PII scrubber on top of Ollamarepo

   De-identify text before it goes to a cloud model using a local model to detect identities and swap them for stable tokens.

   vault-engine · privacy

   Scrub PII locally before it reaches the cloud

   1

   Local scan

   Ollama detects identities

   2

   Tokenize

   swap to stable tokens

   Reversible token swap keeps identities local

   3

   Cloud model

   sees only redacted text

   4

   Restore

   deterministic swap-back

   Deterministic and reversible: cloud never sees raw PII

   Why it matters: Sending sensitive data to cloud models poses privacy risks. vault-engine allows safe preprocessing with local models.

   How to apply: Run `vault-engine scrub notes.txt` or `vault-engine clip` to scrub clipboard content before sending to cloud models. Reversible and deterministic.

   privacyollamalocaltools

   Read more: uilt a PII scrubber on top of Ollama — de-identify text before it goes to a cloud model

7. #7 Google's Agentic Peer-Reviewer Handled ~10K Papers at ICML/STOCpaper

   Agentic AI peer-reviewer reviewed ~10,000 papers with 30-minute turnaround, catching 34% more mathematical errors than zero-shot prompting.

   Why it matters: This is the first formal research paper documenting AI-automated scientific review at conference scale, setting a precedent for future peer review.

   How to apply: Use agentic architectures for large-scale review tasks where consistency and error detection are critical. Consider for internal code reviews or documentation auditing.

   agentspaperreviewresearch

   Read more: Google's Agentic Peer-Reviewer Handled ~10K Papers at ICML/STOC — Formal Research Paper Now Out [R]

8. #8 Complete working guide for AniSora V3.2 GGUF on ComfyUIrepo

   RTX 5090 fix included: PyTorch cu130 required, two-pass setup with UnetLoaderGGUF, avoid WanVideoSampler.

   Why it matters: Getting anime video generation working locally on ComfyUI requires specific fixes and workflows. This guide saves days of debugging.

   How to apply: Use Native ComfyUI nodes + UnetLoaderGGUF in a two-pass setup. Avoid WanVideoWrapper/WanVideoSampler which break temporal coherence.

   comfyuivideolocalgguf

   Read more: Complete working guide for AniSora V3.2 GGUF on ComfyUI — RTX 5090 fix included (two days of debugging so you don't have to)

9. #9 How prompt caching works in Claude Code (and how to stop wasting tokens)tip

   Claude Code caches prompts as you go, but cached prompts expire after 5 mins by default, so long sessions cost full price every turn.

   Why it matters: Understanding prompt caching can save significant costs in Claude Code workflows, especially for long sessions.

   How to apply: Keep Claude Code sessions under 5 minutes to benefit from 10% cached prompt pricing. For longer tasks, structure work into shorter sessions.

   claudecostcachingtokens

   Read more: How prompt caching works in Claude Code (and how to stop wasting tokens)

10. #10 Built a 135M looped transformer from scratch with custom Muon+AdamW optimizer routingrepo

    135M parameter looped transformer trained from scratch on FineWeb (4.6B tokens), with custom optimizer routing and truncated BPTT.

    Why it matters: Shows how to implement advanced training techniques like looped transformers, custom optimizers, and truncated BPTT from scratch.

    How to apply: Use looped transformer architecture for efficient sequence modeling. Implement custom optimizer routing for better gradient flow. Use truncated BPTT for long sequence training.

    trainingtransformeroptimizerlocal

    Read more: I trained a 135M looped transformer from scratch for $51, tried to reproduce Parcae's stability tricks across 5 ablations, and every single "fix" made things worse. Shipping the honest results anyway. r/MachineLearning · I used Claude to build a 135M looped LLM from scratch — it debugged Parcae paper implementations, caught optimizer routing bugs, wrote Modal training infra, and helped ship to HuggingFace. Here's the full story. · Built a 135M looped transformer with custom Muon+AdamW optimizer routing, per-sequence Poisson depth sampling, and truncated BPTT. Here's what the training code looks like.