Question 1

What is Moxie Docs?

Accepted Answer

Moxie Docs is a hosted service that connects to your GitHub repositories, generates a searchable knowledge base of your codebase, keeps it in sync as code changes, and serves that context to AI coding agents over the Model Context Protocol (MCP). It documents architecture, conventions, and key modules automatically, and proposes documentation updates as pull requests your team reviews.

Question 2

Who is Moxie Docs for?

Accepted Answer

Engineering teams that want living documentation without writing it by hand: solo builders documenting private repos, growing teams onboarding new engineers, and organizations maintaining a fleet of services. It is also for teams that want their AI coding agents to have accurate, current context about their codebase.

Question 3

How do I get started?

Accepted Answer

Start a 14-day trial, connect your GitHub account through the Moxie Docs GitHub App, and select the repositories you want documented. Moxie indexes a real repository and generates docs, search, gap detection, and MCP context during the trial. No charge today, and you can cancel anytime before the trial ends.

Question 4

How does Moxie Docs generate documentation?

Accepted Answer

Moxie indexes the source files in the repositories you select, builds an outline of the codebase, and generates documentation page by page, including architecture overviews, references, and conventions, all grounded in your actual code. Documentation is regenerated incrementally as code changes, so it stays current instead of going stale.

Question 5

Is indexing one-shot or continuous?

Accepted Answer

Continuous. The first index is a full baseline. Every merge re-checks affected docs, flags drift and gaps, and keeps MCP context current. On Pro and Team plans, Friday Cleanup batches remaining fixes into one docs-only PR your team reviews - nothing auto-merges.

Question 6

Does Moxie Docs keep documentation up to date when code changes?

Accepted Answer

Yes. When pull requests merge, Moxie detects which documentation is affected, updates the impacted pages, and flags documentation drift and gaps. On Pro and Team plans it also runs a weekly Friday Cleanup that opens documentation pull requests for your team to review.

Question 7

Does Moxie Docs merge changes to my repository?

Accepted Answer

No. Moxie Docs only ever proposes documentation changes as pull requests. Your team reviews and merges every one. Moxie never merges anything itself.

Question 8

How does indexing work on large monorepos with frequent commits?

Accepted Answer

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.

Question 9

What programming languages does Moxie Docs support?

Accepted Answer

Documentation and search work with any GitHub repository, with first-class file recognition for all major languages including TypeScript, JavaScript, Python, Go, Rust, Ruby, Java, PHP, SQL, Svelte, Vue, Kotlin, Swift, Elixir, and Zig. Structured convention and dependency analysis is deepest for TypeScript/JavaScript and Python.

Question 10

Do PR checks block merge, or only warn?

Accepted Answer

By default they warn. Moxie posts GitHub check runs named Moxie Docs / Description, Moxie Docs / Documentation, and Moxie Docs / Conventions. Findings use advisory conclusions - they do not fail the check and will not block merge on their own. Docs and convention issues stay visible on the PR without becoming a hard gate unless your team chooses that.

Question 11

How do I make Moxie Docs PR checks required before merge?

Accepted Answer

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, checks stay advisory so findings are visible without blocking the team by default.

Question 12

What if the docs are right and the code is wrong?

Accepted Answer

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 instead of "syncing" docs down to a bug.

Question 13

How does Moxie handle RFCs and design docs ahead of the code?

Accepted Answer

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.

Question 14

Can internal notes leak into the public knowledgebase?

Accepted Answer

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.

Question 15

Can AI coding agents use Moxie Docs?

Accepted Answer

Yes. Every plan includes an MCP (Model Context Protocol) context endpoint, so MCP-compatible agents and editors can pull your repository's current documentation, conventions, and context while they work, keeping their output consistent with how your codebase actually works.

Question 16

What is the MCP context endpoint?

Accepted Answer

It is a Model Context Protocol server that exposes your repository's documentation and conventions to AI agents and editors that support MCP. Agents query it for up-to-date context instead of guessing, which reduces hallucinated APIs and off-convention code.

Question 17

What happens when an agent hits undocumented code via MCP?

Accepted Answer

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.

Question 18

What access does Moxie Docs need to my GitHub repositories?

Accepted Answer

Moxie Docs connects through a GitHub App scoped to only the repositories you select, and reads those repositories to generate documentation, gaps, search, and MCP context. Documentation changes are only ever proposed as pull requests. Moxie never merges anything itself.

Question 19

Does Moxie Docs work with private repositories?

Accepted Answer

Yes. Moxie Docs is built for private repositories. The GitHub App is scoped to only the repos you choose, and your code is used solely to generate documentation and context for your workspace.

Question 20

How much does Moxie Docs cost?

Accepted Answer

Moxie Docs has three plans. Starter is $29/month ($290/year), Pro is $79/month ($790/year), and Team is $199/month ($1,990/year). Every plan starts with a 14-day free trial.

Question 21

How does the 14-day trial work?

Accepted Answer

Start a trial on any plan with no charge today. Connect GitHub, index a real repository, and use the generated docs, search, gap detection, and MCP context for 14 days. Cancel anytime before the trial ends and you won't be billed.

Question 22

Can I pay annually, and is there a discount?

Accepted Answer

Yes. Every plan can be billed monthly or annually, and annual billing is two months free (about 17% off) versus paying monthly. Annually, Starter is $290/year, Pro is $790/year, and Team is $1,990/year. You can switch between monthly and annual anytime from the billing portal.

Question 23

What is the best plan for one low-churn repository?

Accepted Answer

There is no pay-as-you-go SKU today. For a single repo updated a few times a year, annual Starter ($290/year) is usually the best fit - two months free versus monthly. You can also evaluate with the 14-day free trial or the one-time $5 trial pass on the pricing page before committing.

Question 24

What is the difference between the Starter, Pro, and Team plans?

Accepted Answer

Starter fits a solo builder: up to 5 active private repositories and 1 seat. Pro fits a growing team: up to 15 repositories, 10 seats, weekly Friday Cleanup, and automated Cleanup PR drafts. Team fits an organization: up to 50 repositories, unlimited seats, priority indexing, and everything in Pro.

Question 25

Can I cancel anytime?

Accepted Answer

Yes. You can cancel or change your plan anytime from the billing portal. Cancel before your 14-day trial ends and you won't be charged.

Frequently asked questions

Getting started

How it works

PR checks & trust

AI agents & MCP

GitHub access & security

Pricing & plans

Still have a question?

Frequently asked questions

Getting started

What is Moxie Docs?+

Who is Moxie Docs for?+

How do I get started?+

How it works

How does Moxie Docs generate documentation?+

Is indexing one-shot or continuous?+

Does Moxie Docs keep documentation up to date when code changes?+

Does Moxie Docs merge changes to my repository?+

How does indexing work on large monorepos with frequent commits?+

What programming languages does Moxie Docs support?+

PR checks & trust

Do PR checks block merge, or only warn?+

How do I make Moxie Docs PR checks required before merge?+

What if the docs are right and the code is wrong?+

How does Moxie handle RFCs and design docs ahead of the code?+

Can internal notes leak into the public knowledgebase?+

AI agents & MCP

Can AI coding agents use Moxie Docs?+

What is the MCP context endpoint?+

What happens when an agent hits undocumented code via MCP?+

GitHub access & security

What access does Moxie Docs need to my GitHub repositories?+

Does Moxie Docs work with private repositories?+

Pricing & plans

How much does Moxie Docs cost?+

How does the 14-day trial work?+

Can I pay annually, and is there a discount?+

What is the best plan for one low-churn repository?+

What is the difference between the Starter, Pro, and Team plans?+

Can I cancel anytime?+

Still have a question?