Keep codebase docs in sync with every pull request

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, and Vue, with deepest structured convention analysis for TypeScript/JavaScript, Python, Go, Rust, and Ruby.

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.

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.

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.

We're back on Product Hunt with the new Public Knowledgebase Beta.

Turn your reviewed docs into a public help center - generated from your repo, approved page-by-page by your team, and live on your own subdomain in minutes. If you're checking us out from Product Hunt, take a look at a live site and let us know what you think.

Support us on Product HuntSee a live knowledgebase

Keep codebase docs in sync with every pull request

• Living dev docs & public help centers
• MCP context feeds AI agents
• Nothing merges without review

Connect GitHub repoSee workflow

14-day trial, no charge today · Docs-only PRs · Nothing auto-merges

Watch the walkthrough (9 min)

Works with the agents your team already uses

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

• Claude
• Cursor
• Gemini
• GitHub Copilot
• VS Code
• Codex
• Antigravity
• Windsurf
• Cline
• Zed
• JetBrains
• Neovim
• Warp
• Claude
• Cursor
• Gemini
• GitHub Copilot
• VS Code
• Codex
• Antigravity
• Windsurf
• Cline
• Zed
• JetBrains
• Neovim
• Warp

1. Connect a repo 01 Install the scoped GitHub App and pick the repo to start with. 2. Docs generate in minutes 02 The first index writes architecture, convention, and walkthrough pages into your workspace. 3. PRs keep them current 03 Each merge is checked for drift - fixes arrive as docs-only PRs your team reviews and merges.

//The drift tax

AI writes the code. Docs fall behind.

Code ships faster than anyone can document. Every merge widens the gap between the system and the wiki.

• 75%
of Google's new code is AI-generated (up from \~25% in 2024). Google Cloud Next, 2026
• 58%
of developer time goes to understanding existing code. Xia et al., IEEE TSE
• 0
of that AI-written code updates your docs by itself. Every team, every repo

Agents write code faster. Moxie keeps the docs - and the next agent - honest.

How Moxie catches drift

//Living documentation

Documentation that notices when it's wrong.

Architecture, conventions, and walkthroughs from your code - re-checked on every merge and rewritten when they go stale.

• From source. Architecture, conventions, walkthroughs - cited to code.
• Checked on merge. Each merge is compared to the docs it touches.
• Fixed, not abandoned. Stale pages regenerate with a reviewable diff.

Connect GitHub repoSee how it works

Billing webhook behavior

docs/billing.md

Drift · code changed in PR 491 Regenerated

@@ Retry handling @@

\- Failed webhooks retry up to 3 times.

\+ 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

//New · Public Knowledgebase Beta

A public help center, straight from your repo.

Turn the same reviewed docs into a hosted help center for the people using your product — end users, developers, or both.

• End users or developers. Pick the audience — plain-language help articles, API docs, or both from one repo.
• You approve every page. Drafts stay private until a human publishes them.
• Live in minutes. your-team.moxiedocs.app with your logo and accent color. Custom domains coming soon on Pro.

Explore KnowledgebasesSee a live site

docs.mycompany.com

public kb

Getting Started GuideActive

API AuthenticationActive

//Friday Cleanup

A week of drift, fixed in one PR.

Every Friday: one docs-only PR for what documentation missed. You review. You merge.

• Docs-only. Never your application code.
• One PR a week. Small enough to review on Friday.
• You merge. Nothing auto-merges. Ever.

Connect a repoHow PR checks work

Friday Cleanup

Week of Jun 1 · 9 PRs merged

Docs: catch up on this week's merges

moxie/friday-cleanup · docs-only · awaiting your review

• docs/billing.md+12 −4
• docs/architecture/webhooks.md+6 −1

Docs-onlySource-citedAwaiting review

Merge it, edit it, or close it. Your call.

//Token economics

Calculate your AI token waste

LLM agents waste massive context re-reading your codebase on every prompt. See how much you save with Moxie's dense MCP context layer.

Your Team & Codebase

Active AI Developers5 developers

Developers using Cursor, Claude Code, or Copilot daily.

Daily Prompts per Dev30 prompts / day

Average requests sent to coding assistants per developer daily.

Codebase Size500 source files

Number of files in your active repositories.

Estimated Monthly Savings

$149API bill reduction

75 hrsDeveloper time saved

Avoids wasting 49.5M input tokens per month by ending redundant whole-codebase scans.

Reduces agent latency by serving targeted, pre-indexed codebase conventions on the first try.

Rough estimate · Sonnet input pricing

Stop wasting tokens →

//Ready to try it

Connect a repo. The first index runs in minutes.

Living docs, drift detection, and MCP - on as soon as the first index lands. 14-day trial, no charge today.

Connect GitHub repoSee workflow

14-day trial · No charge today · Pick one repo to start

Or, get a one-time $5 pass

//Solutions for your team

Built for how you lead, build, and scale.

Same living documentation system — framed for your role and company setup.

• Engineering leadersCut onboarding time and see what shipped each week.See how it helps →
• Staff & platform engineersTurn tribal knowledge into docs agents and teammates follow.See how it helps →
• CTOs & foundersScale velocity without losing the thread on your system.See how it helps →
• Teams using AI agentsGive Cursor, Claude & Codex real repo context over MCP.See how it helps →
• Startups & early-stageShip fast without losing codebase context or burning founder hours.See how it helps →
• Scale-ups & growing orgsKill documentation drift and knowledge silos as your team doubles.See how it helps →
• Multi-repo & microservicesSynchronize architecture and MCP context across all your repositories.See how it helps →
• Agencies & consultanciesRamp on client codebases fast and hand off self-updating documentation.See how it helps →
• Enterprise & security-firstPR-gated documentation governance with predictable repo-based pricing.See how it helps →

//Also in the box

The rest of the toolkit.

Explore all features

• Changelog
this week

1. Add per-repo billing+212PR 491 2. Cache dashboard claims+64PR 488 3. Emit cancellation events+38PR 485

Changelog

Auto-generate developer changelogs on every merge. Sync descriptions to Slack or publish a public feed.
• Ask this codebase
8 sources how does auth work? Session tokens & rotationguide lib/auth/session.tssource

Searchable workspace

A terminal-first workspace for your team's Markdown files, codebase annotations, and API specs.
• docs.mycompany.com
public kb Getting Started GuideActive API AuthenticationActive

Public Knowledgebases

Beta Host a fast public help center for your product. Let AI draft pages from code, and publish with human approval. Knowledgebases
• eng-updates
Slack M Moxieapp Friday Recap - 12 PRs merged this week, docs updated for 4 of them. 🎉 4✅ 6

Slack

Deliver weekly Friday Recaps, drift alerts, and pending documentation PR approvals directly to your Slack channels. Slack integration
• Model Context Protocol
mcp-server Claude Code · session active $ moxie-docs --context Loaded 42 rules & 8 schema definitions “Using session auth in lib/auth/session.ts”

Model Context Protocol

Feed verified codebase rules, API schemas, and architectural guidelines to Cursor, Claude Code, and Windsurf.
• Coding conventions
3 rules VITESTTests must use vitest + RTL NAMINGReact components use PascalCase IMPORTSRelative path imports prohibited

Coding conventions

Detect folder structures, naming rules, and import patterns. Raise PR alerts when changes breach codebase standards.

//The trust zone

Security by design, not by promise.

Moxie connects through a scoped GitHub App and keeps your code server-side. Here's exactly what that means.

• Repository access
you choose

* acme/web-appshared * acme/apishared * acme/payrollprivate

Scoped access

GitHub App on only the repos you pick. Nothing else on the account.
• Indexing
auto-skip

* src/server.tsindexed * .env.productionskipped * id\_rsaskipped

Code & secret privacy

Encrypted tokens. Secrets, env files, and dependency folders skipped.
• docs: update auth guide
draft

1. Opened as draft 2. Awaiting your review 3. You merge - never us Ready for review

Human-in-the-loop

Docs arrive as draft PRs. Your team reviews and merges.

Read the full security model

//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.

Z

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.

G

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.

M

MakerStack

Product review · MakerStack



//Free developer tools

Try Moxie before you connect a repo.

No account required. Useful on their own - and a fast on-ramp when you are ready for living docs grounded in your codebase.

View all free tools

• ### Mermaid Diagram Editor
Private in-browser editor with instant preview, shareable URLs, and SVG export. Open tool
• ### SQL to ER Diagram
Paste CREATE TABLE SQL for a live Mermaid ER diagram, SVG/PNG export, and optional AI data-model docs. Open tool
• ### README Generator
Structured README builder with live Markdown preview and shareable export. Open tool

Also free: llms.txt Generator, AGENTS.md Generator, ADR Generator, llms.txt Validator, .cursorrules Generator, CLAUDE.md Generator, .windsurfrules Generator.

Need docs that stay true on every merge? Connect a repository to get living docs, MCP context, and reviewable Cleanup PRs.

Connect GitHub

//FAQ

The questions every team asks first.

Short version: Moxie reads your code, writes the docs, and keeps them current on every merge.

See all FAQ

What is Moxie Docs?+

What happens after I connect a repo?+

Will Moxie change my code automatically?+

How does MCP cut agent cost?+

Can I publish a public help center for my users?+

How much does it cost?+

//Pricing

Try it on a real repo before the first charge.

14-day trial. No charge today. Cancel anytime.

Open-source maintainer? Request free access

//Team & enterprise

Pilot Moxie across a fleet of services.

Team includes priority indexing, unlimited seats, and up to 50 repositories. We will help you scope a rollout on real repos, walk through security, and align on cadence.

Book a callSend a message

//Start the trial

Connect a repo. The first index runs in minutes.

First index in minutes. 14-day trial, no charge today. Cancel anytime if it isn't a fit.

Connect GitHub repoTrial details

Pick one repository. First index in minutes. You review every docs PR.

• Docs generated, then kept current on every merge
• MCP context ready for Claude, Cursor, and Codex
• Friday Cleanup PRs that wait for your review