CodeSummaryCodeSummary

The context layer for engineering teams

Don’t let AI turn your codebase into a black box.

A living source of truth for your entire codebase, always complete, always current, maintaining itself as your code moves. Your team and your agents never lose the thread.

14-day free trial. No credit card. See how it works

dashboard.codesummary.io
The Code Summary dashboard managing an auto-generated documentation site

Works with the tools your team already uses

GitHubClaude CodeCursorVS CodeZedOpenAI MCP

The problem

The knowledge is already in the code. Getting it out is what costs you.

So we got it out. Automatically.

We pointed CodeSummary at OpenClaw, one of GitHub’s most-starred projects: over 350,000 stars, more than 50,000 commits, and gigabytes of TypeScript that move every day. From that one input it built a complete, cross-linked documentation site, every concept understood, every page written, not a single one touched by a human. Source code in, living docs out.

OpenClaw on GitHub
CodeSummary
CodeSummary0 human edits
openclaw.codesummary.iolive
The generated OpenClaw documentation site, live on its own domain
Published docs site

That is the actual output: a complete documentation site, generated from the source and hosted on its own domain. Browse it live, or point CodeSummary at your own repo.

How it works

From repositories to living context.

01

Pushes stream in

Install the GitHub App and every push to main rains into the workspace. Private repos stay private.

02

CodeSummary makes order

The clutter is read, organized into reviewed pages, and synthesized into separate sites, each published to its own MCP endpoint.

03

Endpoints get called

Agents call ask() and orient() against their endpoint and get cited, current answers. The same knowledge publishes as docs on your domain.

Built for agents

One source of truth for your whole stack. Agents just ask.

Every repo you link, frontend, backend, and the services between, becomes one Model Context Protocol endpoint. Instead of cloning and skimming a sibling repo to learn what it does, the agent asks CodeSummary and gets the reviewed answer in one call.

mcp / docsLiving documentation across every linked repo. Always the latest reviewed version.
mcp / style-guideYour coding standards and architecture patterns, so agents write code the way your team does.New
  • Cross-repo answers no single checkout can provide
  • Answers track main, not whoever last ran git pull
  • All your repos under one workspace, one endpoint
  • OAuth-secured · works with every major MCP client
How the MCP endpoint works

For engineering leads · New

Write the standards once. Every agent follows them.

The style guide is its own MCP endpoint your lead curates: coding standards, architecture patterns, the way your team does things. Every engineer's agent pulls it before writing code, so what lands in the PR already looks like your codebase, no matter who (or what) wrote it.

  • Architecture patterns and conventions, served to every agent
  • Update once and the whole team is aligned on the next prompt
  • Stop re-litigating standards in code review
How the style guide works
style-guide.mdcurated by @lead
§ Services communicate over events, never direct DB reads.
§ Errors return problem+json. No bare 500s.
§ React: server components by default. Client only when interactive.
Claude Code · Minaaligned
Cursor · Devaligned
Claude Code · Sashaaligned

Near real-time

Always current, even when your checkouts aren't.

Local repos drift: someone's frontend is three weeks behind main, someone never pulled the new service at all, and every agent reading those checkouts inherits the drift. CodeSummary doesn't care what's on anyone's disk. Every merge to main regenerates the docs, so every agent on the team answers from what actually shipped.

  • Answers reflect main as of the last push, not anyone's local state
  • Full and incremental regeneration on every merge
  • Your edits are never silently overwritten: changes wait in review
How generation works

Your domain, your brand

And your humans get a docs site they'll actually use.

The same reviewed knowledge your agents query ships as a polished docs site. Public product docs, internal team handbooks, or both: custom domains with automatic SSL, your logo and colors, and a private mode that keeps team knowledge behind sign-in.

  • Custom domains with automatic certificates
  • Public, unlisted, or private to your team
  • Interactive API reference when a spec is detected
Explore hosted docs

Built for serious teams

Control you can take to your security review.

Private by default

New sites start team-only. Nothing becomes public until you decide it should.

You hold the pen

Every AI change to a page you have touched goes through review. Accept, reject, or edit before anything ships.

Scoped access

OAuth grants and access tokens are scoped to a single site or repo. Revoke any of them at any time.

Full version history

Every published version is preserved. Roll back to any prior state in one click.

Pricing

Simple, flat pricing. No metering.

Pro and Team start with a 14-day free trial, no card required. Scale and Enterprise are tailored to your team.

Pro

$49/ month

For developers and small teams.

  • Unlimited hosted docs sites
  • Custom domains + SSL
  • Auto-regenerate on every push
  • Generous monthly credits
  • In-app editor + review
  • Built-in MCP endpoints
Start free trial

Team

Most popular
$299/ month

For teams shipping across many repos.

  • Everything in Pro
  • Up to 15 seats
  • Shared team workspace
  • Team roles & permissions
  • Higher monthly credits
  • Multi-repo sites
Start free trial

Scale

From$899/ mo

For larger teams.

  • Everything in Team
  • Custom seat limits
  • Custom volume pricing
  • Dedicated onboarding
  • Priority support & SLA
Contact us

Enterprise

Custom

For compliance-driven organizations.

  • Everything in Scale
  • SAML SSO & SCIM
  • Security review & SLA
  • Custom contracts & DPA
  • Onboarding & migration
Contact sales

Get every agent on the same page.

Connect your repos, set your style guide, and the whole team, humans and agents alike, starts answering from one source.