Skip to main content

Living docs for GitHub repos

Docs that stay true to your code.

Moxie connects to GitHub, writes docs from source, checks every pull request for drift, and opens a docs-only PR when something is wrong. Your team reviews. Nothing auto-merges.

Connect GitHub freeSee how it works

Free on 1 repoNo card, everDocs-only PRs you review

moxiedocs.com/dashboardIn sync

Repository

acme/payments-api

1 PR awaiting review
  • Billing webhooksdocs/architecture/webhooks.mdPatched
  • Payments APIdocs/api/payments.mdCurrent
  • Session handlingdocs/auth/sessions.mdCurrent
  • Agent guidanceAGENTS.mdCurrent
Docs current4/4
Conventions12
Cleanup PRs1 open

Activity · this merge

main
  1. PR #491 merged into mainfeat(billing): idempotency keys on webhook retries
  2. Drift detected · docs/architecture/webhooks.mdRetry limit changed 3 → 5 · doc still says 3
  3. Doc patched with source citationssrc/billing/webhooks.ts:42-61
  4. Cursor asked get_conventions()12 rules returned · each cited · 18ms
  5. Friday Cleanup PR #493 opened2 files · docs-only · waiting for your review

Serves context to the editors and agents your team already uses

Works with Claude, Cursor, Gemini, GitHub Copilot, VS Code, Codex, Antigravity, Windsurf, Cline, Zed, JetBrains, Neovim, Warp.

Common questions about Moxie Docs

Does Moxie Docs work with private GitHub repositories?
Yes. Built for private repos. The GitHub App is scoped to only the repos you choose, tokens are encrypted server-side, and code is used only to generate documentation and MCP context for your workspace.
What programming languages does Moxie Docs support?
Documentation and search work with any GitHub repository. Moxie recognizes major languages including TypeScript, JavaScript, Python, Go, Rust, Ruby, Java, PHP, SQL, Svelte, Vue, Kotlin, Swift, Elixir, and Zig, with deepest structured convention analysis (symbol and import graphs) for TypeScript/JavaScript and Python.
How do I keep documentation in sync with my code?
Connect a GitHub repo. Moxie re-indexes on every merge, flags pages affected by code changes, regenerates stale documentation with cited diffs, and on Pro and Team plans runs Friday Cleanup to open weekly docs-only pull requests for review.
How much does automated codebase documentation cost?
Starter is $29/month, Pro is $79/month, and Team is $199/month, each with a 14-day free trial. Annual billing saves about two months versus monthly. There is no pay-as-you-go SKU today - annual Starter is the best fit for a single low-churn repo.
What is the best tool for automated GitHub codebase documentation?
Moxie Docs indexes the repositories you select through a scoped GitHub App, generates architecture and convention docs grounded in source code, detects documentation drift on every merge, and opens weekly Friday Cleanup PRs so docs stay current without manual rewrites. It also exposes an MCP server so Cursor, Claude Code, and Codex pull verified conventions instead of re-crawling the repo.
What is documentation drift and how does Moxie Docs detect it?
Documentation drift is when written docs no longer match the code they describe. Moxie Docs checks each merged pull request against the documentation it touches, compares generated docs to the current source, surfaces gaps in the workspace, and regenerates impacted pages so teams see what changed and why.
What is Friday Cleanup in Moxie Docs?
Friday Cleanup is a weekly docs-only automation on Pro and Team plans. Moxie batches small documentation fixes - stale pages, gaps, and drift - into a single pull request your team can review with Friday coffee. Nothing auto-merges; you hold the merge button.
How do AI coding agents get codebase context from Moxie Docs?
Every Moxie Docs plan includes an MCP (Model Context Protocol) server. Compatible agents and editors query it for current documentation, conventions, verified commands, and open gaps instead of guessing from partial file reads, which cuts token waste and wrong API assumptions.
What is an MCP server for codebases?
An MCP server for codebases exposes repository documentation and conventions to AI agents through the Model Context Protocol. Moxie Docs publishes one at /api/mcp with OAuth and bearer-token access so agents pull live, cited context about how your project actually works.
What happens when an agent hits undocumented code via MCP?
MCP tools return structured gaps and impact, not invented APIs. Agents can call moxie.get_doc_gaps, moxie.get_doc_impact, and moxie.propose_doc_update so missing docs land in the same PR as the code change - or wait for Friday Cleanup - instead of papering over the hole.
What if the docs are right and the code is wrong?
Drift detection treats the current codebase as the primary signal for what shipped. Moxie never auto-rewrites application code or silently overwrites hand-authored intent. Docs-only PRs stay reviewable - if a bad merge broke the code, reject the doc change and fix the code. Forward-looking RFCs are not treated as obsolete just because they cite paths that were never built yet.
How does Moxie handle RFCs and design docs ahead of the code?
Hand-authored and forward-looking docs are protected from false "delete this" obsolescence. Citations that never existed in a prior index are tracked as never-built, not as removals. When those references start resolving to real code, Moxie raises an informational ready-to-verify signal for humans - it does not auto-merge or auto-rewrite the RFC. Stale but still-valid hand docs can be refreshed via reviewable PRs.
Can internal notes leak into the public knowledgebase?
No page goes public without a human publish step. The Public Knowledgebase review inbox keeps drafts private; agent-oriented workspace docs and temporary implementation notes are not the public site. Quality gates flag internal jargon and leak-prone phrasing before publish. You choose audience (users, developers, or both) at setup.
How does indexing work on large monorepos with frequent commits?
The first index is a full baseline and takes longer on large trees. After that, merges re-check the affected surface incrementally so every commit is not a full rebuild. Use ignored paths in repository documentation settings to skip generated folders, vendored deps, and noise. Team plans get priority indexing for larger fleets.
How do I make Moxie Docs PR checks required before merge?
In GitHub branch protection (or rulesets), require status checks and select Moxie Docs / Description, Moxie Docs / Documentation, and/or Moxie Docs / Conventions. Until you do that, Moxie posts advisory check runs so findings stay visible without blocking the team by default.
How does Moxie Docs help onboard new engineers?
Moxie generates searchable architecture overviews, module walkthroughs, and convention guides cited to source files, then keeps them current on every merge. New engineers search one workspace instead of spelunking the repo, and AI agents they use inherit the same grounded context over MCP.
Can Moxie Docs generate architecture documentation from source code?
Yes. Moxie indexes your repository, builds an outline of modules and dependencies, and generates architecture pages, references, and convention summaries with citations back to the files they came from. Pages regenerate incrementally when the underlying code changes.
What is a hosted knowledgebase?
A hosted knowledgebase is a searchable help site grounded in your codebase — written for your product's end users, for developers integrating your API, or both, depending on the audience you pick during setup. Moxie Docs publishes it on a moxiedocs.app subdomain (custom domains are coming soon on Pro and Team plans) with human review before anything goes public, built-in article search, and content that stays in your git repo as Markdown.
Can Moxie Docs host an end-user help center?
Yes. Choose the “User” audience during knowledgebase setup and Moxie writes plain-language help articles about using your product — no code identifiers or internal jargon — reviewed by you before anything is published. Pick “Both” to serve end users and developers from the same site.
Will Moxie Docs change my application code automatically?
No. Moxie only proposes documentation changes as reviewable pull requests. Description alignment may update a pull request description on GitHub, but your source code, branch protection, and merge controls stay with your team.
500+
repositories connected
13k+
source files documented
88%
of reviewed doc PRs merged
Moxie Docs rating on PeerPushMoxie Docs reviews on SourceForge

Production figures, verified September 2026

The drift problem

Every merge is a chance for the docs to lie.

Code changes in a pull request. The doc that described it does not. A week later an engineer, or an AI agent, reads the old rule and ships against it.

  1. 01A pull request mergesRetry limit goes from 3 to 5. Idempotency keys are added.
  2. 02Moxie checks the docs it affectsAn advisory GitHub check names the page and the exact lines.
  3. 03The doc is patched, cited to sourceA docs-only diff, ready for review. Nothing merges on its own.
How drift detection works
src/billing/webhooks.tsPR 491
export async function retryWebhook(event: StripeEvent) {
− const MAX_RETRIES = 3;
+ const MAX_RETRIES = 5;
+ const key = `idemp:${event.id}`;
+ await redis.set(key, 1, { ex: 86_400 });
return withBackoff(MAX_RETRIES, () => deliver(event));
Patched · cited to webhooks.ts:42
docs/architecture/webhooks.mdCurrent
## Retry handling
−Failed webhooks retry up to 3 times.
+Failed webhooks retry 5 times with exponential backoff.
+Idempotency keys (24h TTL) prevent double-charges on retry.

How it works

One loop, four jobs. It runs on every merge.

Connect once. From then on the docs, the PR checks, and the agent context follow the code without anyone babysitting a wiki.

  1. github.com/apps/moxie-docs/installations/new

    Install Moxie Docs

    Only select repositories

    • acme/payments-apiTypeScript · 1,248 files
    • acme/webTypeScript · 3,901 files
    • acme/infraHCL · 212 files
    Permissions requestedContents · readPull requests · read & writeMetadata · read
    See the full workflow
  2. moxiedocs.com/dashboard/knowledgebaseIndexed 1,248 files
    • Billing webhooksArchitecture
    • Request lifecycleArchitecture
    • PaymentsAPI
    • Validation & errorsConventions
    • Deploy & rollbackOperate

    Billing webhooks

    Stripe delivers events to /api/webhooks/stripe. Each event is verified against the signing secret, deduped by event id, then dispatched to a typed handler. Failed handlers retry with exponential backoff.

    • src/billing/webhooks.ts:12-61
    • src/lib/backoff.ts:4-28
    How indexing works
  3. github.com/acme/payments-api/pull/491/checksAdvisory

    feat(billing): idempotency keys on webhook retries

    #491 · 3 checks · merge not blocked

    • Moxie Docs / DescriptionPR body matches the diff
    • Moxie Docs / Documentation1 page drifted · patch staged
    • Moxie Docs / Conventions12 of 12 rules followed

    Require these checks in branch protection to turn a warning into a gate.

    Drift detection guide
  4. github.com/acme/payments-api/pull/493Open

    docs: Friday Cleanup for billing & agents

    moxie/friday-cleanup → main · opened by moxie-docs[bot]

    Three pages drifted this week. Each change is cited to the source that caused it. No application code is touched.

    • docs/architecture/webhooks.md+12 −4
    • docs/billing.md+6 −1
    • AGENTS.md+3 −0
    Your review · your mergeReview changes
    Friday Cleanup details

Agent context over MCP

Your agents read the same docs.

Every plan includes an MCP server. Cursor, Claude Code, Codex, and friends pull conventions, docs, verified commands, and open gaps instead of re-crawling the repo on every prompt.

  • One scoped lookup replaces dozens of file reads. Fewer tokens, fewer wrong guesses.
  • Undocumented code comes back as a gap, not an invented API. Agents can propose the doc in the same PR.
  • Moxie keeps AGENTS.md current too, so tools without MCP still get the rules.
ClaudeCursorGitHub CopilotCodexWindsurfCline
Set up MCP in your editor
Claude Code · session
moxie-docs mcp · connected

  1. ›moxie.get_conventions()

    12 rules · "Webhooks are idempotent on event.id" · cited src/billing/webhooks.ts

  2. ›moxie.search_docs("retry backoff")

    Architecture · Billing webhooks → docs/architecture/webhooks.md#retry-handling

  3. ›moxie.get_doc_impact(["src/billing/webhooks.ts"])

    2 docs affected · 1 undocumented export · update in this PR

10 tools · OAuth 2.1 or bearer tokencontext stays current on merge

Built by the team behind Moxie Docs

Meet Jackalope, a desktop workspace for parallel coding agents

Run Claude Code, Codex, and Grok side by side. Each agent works in its own Git worktree, so nothing collides, and you review every change before it lands. Launching for macOS, Windows, and Linux. Early access is going out in waves.

Join the waitlist
acme.moxiedocs.app/webhooksBeta · all plans

Public knowledgebase

Publish a help center from the same source.

Turn the repo into a hosted docs site for your product, written for end users, developers, or both. Every page waits for your approval before it goes live.

  • Plain-language articles for users, cited references for developers.
  • Hosted on your-team.moxiedocs.app with search, a changelog, and llms.txt built in.
  • Internal notes and agent guidance stay private until you publish.
Knowledgebase features

Trust boundaries

Security by design, not by promise.

Moxie reads code to write docs and serve context. That is the whole job, and the boundaries around it are explicit.

Read the security model

  • Scoped to the repos you choose

    The GitHub App is installed per repository. The rest of your organization stays invisible to Moxie.

  • Secrets never leave your repo

    Environment files, keys, and vendored folders are skipped at index time. Tokens are encrypted at rest.

  • Humans hold the merge button

    Changes only ever arrive as docs-only pull requests through your normal review process. Your code is never used to train models.

What developers say

Developers get the problem instantly.

Early reactions from developers and reviewers, and where Moxie fits in.

Context quality seems to be becoming a bigger bottleneck than model quality for a lot of agent workflows.

Moxie resolves this by pre-indexing codebase context right in front of the model.

Zaid Mallik@zaidmallik · Product Hunt

Docs that travel into the coding assistant is the part that feels right here. A README sitting in GitHub is helpful, but the moment I'm in a Claude/Codex loop the question is whether the current rule is actually in the model's face.

Moxie keeps those architecture rules active and cited in every coding session.

GlyphHarbor@glyphharbor · Product Hunt

Moxie Docs tackles the real problem of stale documentation by auto-generating docs and flagging drift on merge, which is smart.

The drift detection and weekly PRs attack the root cause of stale docs.

MakerStackProduct review · MakerStack

The PR check is the part I would lead with. Docs rot because nothing in the workflow ever tells you they rotted, so a check that fails loudly on the diff is worth more than any amount of generation quality.

Paul Crinigan@paul_crinigan · Product Hunt

This feels useful because docs are starting to serve two audiences at once: humans reading the public knowledgebase, and AI agents using repo context while work is happening.

Grace Lee@grace_lee26 · Product Hunt

The Friday Cleanup idea is nicely restrained. Batching doc drift into one reviewable PR, with nothing auto-merging, feels like a much easier habit for a team to trust.

Adrian Ciaschetti@adriancia · Product Hunt

Token economics

Estimate what re-crawling the repo costs you.

Agents re-read a slice of the codebase on every prompt to rebuild context. One dense, cited MCP lookup replaces most of it.

5 developers

Anyone on Cursor, Claude Code, Codex, or Copilot most days.

30 prompts

Requests sent to a coding assistant on a normal day.

500 files

Bigger repos mean more files re-read per prompt.

Estimated per month

$149input-token spend avoided
75 hdeveloper time reclaimed

About 49.5M input tokens a month stop going to whole-repo scans. Time saved assumes 1.5 minutes less re-explaining context per prompt.

Rough estimate · $3 per 1M input tokens

Connect GitHub free

Pricing

Start free on a real repo. Upgrade when you need more.

Free is permanent for one repository, no card required. Every paid plan starts with a 14-day trial and can be cancelled anytime if Moxie Docs doesn't work for you.

Open-source maintainer? Request free access

Rolling out across a fleet?

Team covers up to 50 repositories with unlimited seats and priority indexing. We will help scope the rollout and walk through security.

Book a callSend a message

Questions

The short answers.

What Moxie reads, what it writes, what it never does, and what it costs.

See all questions

Connect a repo. The first index runs in minutes.

Free forever on one repository, no card required. Upgrade only when you need more repos, Friday Cleanup, or team seats.

Connect GitHub freeCompare plans
  • Docs generated from source and re-checked on every merge
  • MCP context for Cursor, Claude Code, Codex, and Windsurf
  • Docs-only pull requests that wait for your review