trovex vs Aider
Aider edits your code from the terminal. trovex serves your docs to agents. Different layers — here's how they line up.
Aider is a terminal AI pair programmer: it builds a repo map of your code with tree-sitter and makes edits via git. trovex is not a coding agent — it's an MCP server that serves your repo's canonical markdown docs, one current doc per query with a freshness marker, for about 60% fewer tokens per lookup. Aider's repo map is about code structure for editing; trovex is about which doc is the source of truth. They solve different problems.
What is Aider?
Aider is a fast, zero-config, open-source pair programmer that runs in your terminal. It summarizes your codebase into a repo map so the model has the structure it needs, then applies changes to files through git commits. You pay only for the underlying model. It's great at implementing features and fixing code directly.
Where trovex is different
trovex doesn't write code — it answers "which doc is canonical?" When your project knowledge lives across many markdown files (runbooks, ADRs, READMEs), trovex returns the single current one that answers a query, marks stale and duplicate copies so they're skipped, reads at the section level, and lets agents write records back. Aider's repo map gives a coding model code structure; trovex gives any agent the authoritative documentation, cheaply.
| Capability | Aider | trovex |
|---|---|---|
| Type | Terminal coding agent | MCP context server |
| Edits your code | ✓ via git | — not its job |
| Context it builds | Repo map of code (tree-sitter) | Canonical markdown doc per query |
| Freshness signal on docs | — | ✓ canonical / stale / duplicate |
| Write-back / shared docs | — | ✓ shared write path |
| License / cost | OSS, pay for the model | OSS (AGPL core / MIT CLIs), local |
When is Aider the right choice?
When you want an LLM to actually edit your code from the terminal, Aider is excellent and purpose-built for it. Reach for trovex when the job is serving your repo's documentation to agents as one canonical, current answer — a different layer that can sit alongside whatever does the editing.
FAQ
What is the difference between trovex and Aider?
Aider is a terminal AI pair programmer — it builds a repo map of your code and edits files via git. trovex is an MCP server that serves your repo's canonical markdown docs, one current doc per query with a freshness marker. Aider's repo map is about code structure for editing; trovex is about which doc is the source of truth.
Does Aider's repo map replace trovex?
No. The repo map summarizes code structure for editing. It doesn't route a question to the one canonical doc, mark stale copies, or serve documentation with freshness — that's trovex's job.
Can I use trovex with Aider?
trovex serves canonical docs over MCP, so any MCP-capable client can read them. Aider is best at terminal code editing; if your workflow needs the repo's documentation served to an agent, trovex provides that. Check Aider's current docs for its MCP support.
Canonical docs for your agents.
trovex is in private beta — request access and serve the one current doc per query.
Open source (AGPL-3.0 core, MIT CLIs). Local-first — your docs never leave your machine.