For people
A searchable place to learn the codebase, save context, and understand why files are organized the way they are.
Product workflow
One afternoon of setup, then Moxie works on your repo's schedule: every pull request checked, every merge re-indexed, every Friday cleaned up.
The cadence
Connect, start the trial, run the first index.
PR checks, drift detection, re-index.
One reviewable docs-only PR.
Phase 1 · Once
Install the GitHub App on the repos you choose. Read-only by default, scoped per repository.
Read-only access · scoped to the repos you pick
Add payment details to unlock indexing. 14 days, no charge today, cancel anytime.
Moxie reads source, tests, docs, and history — and writes architecture pages, conventions, gap reports, and MCP context.
reading source · tests · docs · history
Phase 2 · Every merge
Each PR description is rewritten against your template and conventions. The diff is never touched.
before
added search tool, misc fixes
after
Adds the search_docs MCP tool. Queries hit the doc index and return cited matches. Why: agents needed scoped search…
Stale or missing docs are called out on the PR — before merge, while fixing is cheap.
Flagged on the PR — fix now or let Friday Cleanup catch it
When code lands, the affected docs are re-checked and regenerated, cited back to source.
- Search runs against raw file chunks.
+ Search queries the doc index via the search_docs MCP tool.
Re-indexed 4m after merge · cited to source
Phase 3 · Every Friday
Moxie recaps the week's merges and opens a single reviewable PR for anything documentation missed. You review, you merge — nothing lands on its own.
moxie/friday-cleanup · docs-only · awaiting your review
Merge it, edit it, or close it — your call.
Human and AI use
A searchable place to learn the codebase, save context, and understand why files are organized the way they are.
A compact context layer with conventions, commands, boundaries, and citations before AI tools edit the repo.
Connect a repo and the first index runs in minutes.