Stop letting AI agents burn context on shell syntax

What it does

FastCtx is a local Rust runtime that exposes repository operations—file reads, content search, glob, replace, and Bash execution—as structured MCP tools. Instead of having models assemble, escape, and parse ad-hoc shell commands, the agent passes parameters like paths and patterns to a persistent Rust process that handles traversal, encoding, and pagination. The goal is fewer tool calls and less context wasted on command mechanics.

The interesting bit

The architecture is deliberately split: each fastctx serve process is a thin stdio proxy, while a shared per-user control center manages search execution, resource limits, and background jobs. This lets multiple agent sessions share a single search pool and job history without stepping on each other’s working directories. If the control center fails to start, the proxy quietly falls back to a standalone server rather than leaving the agent stranded.

Key highlights

• Nine built-in MCP tools covering file inspection, grep, glob, batch replace, and foreground/background Bash execution
• Persistent control center shared across proxies for the same user, with per-session isolation for working directories and cancellation state
• Background job support: start, stream output, list, and kill full process trees across sessions
• First-class setup flows for ChatGPT App and Codex CLI; any MCP client can register fastctx serve directly
• Shipped through npm as a wrapped Rust binary, with atomic GitHub Release updates and offline-aware caching

Caveats

• Bash execution tools are disabled by default and must be explicitly enabled in the control terminal
• Fresh releases can trigger 404s on npm mirror registries until they sync from the official registry
• Large batch replacements can hit out-of-memory errors if the file size limit is configured too aggressively

Verdict

Worth a look if your AI agent is drowning in shell syntax and context overhead during repository work. Probably overkill if you only need occasional file reads and your MCP host already exposes a simple filesystem tool.