AGENTS.md
Open convention for any coding agent - build commands, style, and gotchas at the repo root.
Claude Code + Moxie Docs
MCP and CLAUDE.md context for Claude Code
Claude Code reads CLAUDE.md at session start, but that file still goes stale. Moxie Docs generates and maintains repository documentation, serves live context over MCP, and helps your AGENTS.md / CLAUDE.md instructions stay grounded in what the code actually does.
- MCP + markdown files. Use CLAUDE.md for standing instructions and MCP for live docs, gaps, and conventions.
- Shared source of truth. Import AGENTS.md into CLAUDE.md so every agent reads the same house rules.
- Friday Cleanup PRs. When docs drift, Moxie proposes updates as reviewable PRs - never silent edits.
Set up Claude Code with Moxie
- Step 1
Connect a repository
Start a trial and index the repo Claude Code will work in.
- Step 2
Run moxie-docs setup
npx moxie-docs setup configures Claude Code's MCP entry and installs the skill block.
- Step 3
Wire AGENTS.md
Point CLAUDE.md at AGENTS.md (or symlink) so Claude-specific notes sit below shared conventions.
$ npx moxie-docs setup
Sign in, configure your editor, and install the skill - one command.
Context files
CLAUDE.md
Claude Code's session memory. Import AGENTS.md, then add Claude-specific instructions below.
FAQ
Does Moxie work with Claude Code out of the box?+
Yes. Moxie exposes a standard MCP endpoint. Run npx moxie-docs setup after connecting a repository, or copy the MCP config from your dashboard once the first index finishes.
What context do agents receive?+
Conventions, generated docs, open doc gaps, verified commands, and doc-impact hints for the files an agent plans to change - all scoped to the repository you selected.
Does Claude Code read AGENTS.md automatically?+
No - Claude Code loads CLAUDE.md. The recommended pattern is a CLAUDE.md that imports or symlinks AGENTS.md so both tools share one source of truth.