Daimonos
About
Daimonos is a single Rust binary MCP server that makes AI coding agents faster and cheaper. It replaces built-in file, search, exec, and git tools with structured equivalents that return compact JSON instead of raw terminal output.
Details
- Author
- beardfaceguy
- Downloads
- 307
- Categories
- Developer Tools, Productivity, Other, File Management
Jump to
- Native tool plugins for git, cargo, gh, and docker with structured JSON output
- Semantic output filtering — test runners return summary + failures only
- Read deduplication — re-reading an unchanged file returns {"unchanged":true}
- Batch operations – multiple tools in a single round trip
- Workspace snapshots – checkpoint before risky edits, rollback on failure
- Token analytics with cross-session history
Download a pre-built binary for your platform and configure it as an MCP server with any compatible tool (Cursor, GitHub Copilot, Claude Code, Windsurf, Cline, Gemini CLI, Zed, etc.). No additional dependencies are required.
An agent-optimized OS layer that makes AI coding agents faster and cheaper.
Daimonos replaces the built-in file, search, exec, and git tools in your AI coding agent with structured equivalents that return compact JSON instead of raw terminal output. The result: fewer tokens consumed, fewer round-trips, and lower API costs — with zero changes to your workflow.
Platforms:Linux (x86_64, aarch64) and macOS (Apple Silicon, Intel). Windows support isplanned.
For repository agent/operator conventions, seeAGENTS.md(especiallyDaimonos tool usage policy).
The name comes from Greekdaimon(agent/spirit), the etymological root of "daemon."
When an AI agent runscargo test, it gets back hundreds of lines of terminal output — progress bars, compile messages, passing test names — when all it needs is "47 passed, 0 failed." The agent pays for every token of that noise: reading it, reasoning about it, and carrying it in context for the rest of the session.
The same waste happens withgit status,docker ps,ls -la, and every other shell command. Agents spend 30-50% of their token budget on verbose, unstructured tool output.
The single binary also provides ACP, one-shot agent, interactive chat, and socket-daemon runtimes — a full coding-agent harness in its own right; seeAgent harness featuresbelow andRuntime modesfor the explicit subcommands and compatibility aliases.
Agent: exec("cargo test") Without Daimonos (raw terminal output): Compiling inventory v0.1.0 (/workspace) Finished test profile [unoptimized + debuginfo] target(s) in 2.31s Running unittests src/main.rs (target/debug/deps/inventory-abc123) running 47 tests test config::tests::test_default ... ok test config::tests::test_load ... ok ... (200+ more lines) test result: ok. 47 passed; 0 failed; 0 ignored With Daimonos (structured JSON): {"ok":true,"tests":47,"passed":47,"failed":0,"failures":[]}
-
Native tool plugins—git,cargo,gh, anddockerare exposed as first-class MCP tools with structured JSON output. When agents callexec("cargo test"), Daimonos intercepts it and routes through the native plugin instead.
Semantic output filters— For commands without native plugins (pytest, make, pip install, eslint, etc.), Daimonos applies semantic compression: test runners return summary + failures only, build commands return "ok" or just the errors, install commands return success/failure.
Protocol-level efficiency— Read deduplication (re-reading an unchanged file returns{"unchanged":true}instead of the full content), compact field names, lazy tool exposure, batch operations, and a terse output directive that cuts LLM prose by ~30%.
Tested with Claude Opus 4.6 on identical coding tasks (read files, search code, edit, run tests, git operations):
Remote benchmarks on AWS (same hardware, same model, same tasks) showed20.3% cost reductionand14.0% fastertask completion.
Use this script for README readers, release notes, and social posts:
# 1) Install daimonos cargo build --release sudo cp target/release/daimonos /usr/local/bin/ # 2) Configure your MCP client (example: Cursor) # .cursor/mcp.json -> command: daimonos, args: ["--mcp", "-w", "/path/to/project"] # 3) Ask your agent to run: # "Run cargo test and summarize failures only." # "Show git status as structured output."
- same workflows, less tool-output noise
- structured responses instead of raw terminal spam
- fewer tokens and fewer round-trips for common coding tasks
# Linux x86_64 curl -L https://github.com/beardfaceguy/daimonos/releases/latest/download/daimonos-x86_64-linux.tar.gz | tar xz sudo mv daimonos /usr/local/bin/ # macOS Apple Silicon curl -L https://github.com/beardfaceguy/daimonos/releases/latest/download/daimonos-aarch64-macos.tar.gz | tar xz sudo mv daimonos /usr/local/bin/
git clone https://github.com/beardfaceguy/daimonos.git cd daimonos cargo build --release sudo cp target/release/daimonos /usr/local/bin/
Seedocs/install.mdfor all platforms (ARM Linux, Intel Mac, musl static builds).
For most users, start with one of these:
- Cursor:Cursor IDE setup
- Zed:Zed setup
- Claude Code:Claude Code setup
Add Daimonos as an MCP server. ForCursor, add to your project's.cursor/mcp.json:
{ "mcpServers": { "daimonos": { "command": "daimonos", "args": ["--mcp", "-w", "/path/to/your/project"] } } }
That's it. Daimonos starts when your IDE opens the project and exits when you close it. No daemon to manage, no background service.
- Cursor IDE
- GitHub Copilot(VS Code, Visual Studio, JetBrains, Xcode, Eclipse)
- Claude Code(CLI + macOS Desktop app)
- Windsurf
- Cline(VS Code extension)
- Gemini CLI
- Zed Editor
- Discord integration(bot token, allowlists, read-only tools)
- Other tools(Claude Desktop, ChatGPT, Continue.dev, BoltAI, etc.)
These appear automatically when the corresponding CLI tool is found on PATH:
- Workspace snapshots— Checkpoint before risky edits, rollback on failure
- Starlark scripting— Bundle multiple tool calls into a single script
- Token analytics— Per-tool-call tracking with cross-session history (daimonos --stats)
- Background processes— Start, poll, and kill long-running commands
- Configurable— All tunables in a single[TOML config file
Beyond the MCP server, the same binary is a complete coding-agent harness: an interactive terminal UI (daimonos agent), an ACP backend for Zed, a one-shot CLI, and a session daemon with attach/detach and remote control.
Many of its recent features come from a systematic study of 60+ open-source agent harnesses (Aider, OpenHands, SWE-agent, Goose, OpenCode, Forge, Pi, the Cline family, and others) — mining the ecosystem for proven techniques and adapting the best ones.
Provider resilience — a hiccup never kills the turn
…
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.





