Moxie generates architecture pages, conventions, and walkthroughs from your code, then re-checks them on every merge. When the code moves, the affected docs get flagged and rewritten instead of quietly rotting.
Generated from source. Architecture, conventions, and walkthroughs. Every line cites the code it came from.
Drift caught on merge. Each merge is checked against the docs it touches.
Updated, not abandoned. Stale pages are regenerated, with the diff to prove it.
+ Failed webhooks retry 5 times with exponential backoff.
+ Idempotency keys prevent double-charges on retry.
Cited to apps/web/src/app/api/billing · updated 4m after merge
MCP context for agents
Stop paying agents to rediscover your codebase.
Cursor, Claude Code, and Codex pull your conventions, docs, and verified commands over MCP, already formatted for agents and scoped to the task. No re-crawling the repo on every prompt.
Fewer tokens. One scoped lookup replaces dozens of exploratory file reads.
Right the first time. Agents follow your conventions instead of guessing them.
Read-only and scoped. Context only. Never billing, settings, or the merge button.
Every merge summarized, with internal and external views you can paste anywhere.
Searchable workspace
Generated docs and your Markdown in one place, so new engineers skip the scavenger hunt.
Description alignment
PR descriptions rewritten to match your template. Your code stays untouched.
Doc-impact checks
Stale or missing docs flagged on the PR before it merges.
FAQ
The questions every team asks first.
Short version: Moxie reads code, writes docs, checks PRs, and asks before changing anything.
What happens after I connect a repo?+
Moxie indexes the repository, generates searchable docs, summarizes conventions, and starts checking every new pull request for description alignment and doc impact. From then on it re-indexes on every merge.
Will Moxie change my code automatically?+
No. Description alignment edits the PR description on GitHub; doc updates arrive as reviewable docs-only PRs. Branch protection, code review, and merge control all stay with your team.
How does the MCP layer cut agent cost?+
Agents pull your conventions, docs, gaps, and verified commands directly instead of re-crawling the codebase on every prompt. Less rediscovery means fewer tokens, and fewer wrong guesses to redo.