What Is Dosu and How Does It Keep Documentation and Coding Agents in Sync?

Dosu is knowledge infrastructure for engineering teams and the coding agents they work with: it captures what agents and people learn, stores it as durable team knowledge, and serves it back to every agent as shared context. It fits teams already running one or more coding agents who keep paying to re-discover the same information, and who want docs, specs, and agent memory to stay current with the code. It is not a standalone wiki you maintain by hand — the value depends on connecting your repos, chat tools, and agents so Dosu can observe changes.

The core problem Dosu targets

Most agent token spend goes to context gathering, and much of that is re-discovering what another agent already figured out. Dosu's answer is a shared knowledge cache: information is explored once and reused everywhere.

The site illustrates the gap with a comparison of a typical task run:

Dosu summarizes this as 50% fewer tokens and 2x iteration speed, and claims roughly 3x more run-to-run consistency from the shared knowledge layer. Treat these as vendor-reported figures, not independently verified benchmarks — the mechanism (one agent learns, all agents know) is the part worth evaluating against your own workflow.

How Dosu works

Step 1: Connect your tools

• Install Dosu on GitHub or GitLab; it begins monitoring changes to keep docs fresh.
• Add Dosu to Slack or MS Teams so you can ask it for context or tell it to document something.
• Sync existing docs from Notion, Confluence, Coda, or your repo.

Step 2: Connect your coding agent

Add the Dosu MCP Server with a single shell command. Your agent then gets consistent, token-efficient context from all connected tools, and Dosu automatically captures knowledge from each session.

The site also shows a CLI install path:

curl -fsSL https://cli.dosu.dev/install | sh

What happens after setup

Dosu reviews your knowledge as code changes and new conversations happen, wherever that knowledge lives. It updates existing sources instead of creating conflicting copies, so humans and agents work from the same version. Captured learnings become durable, team-wide knowledge and reusable skills — the site's example artifacts include Agents.MD, Claude.MD, and a skills/auth entry.

Ownership and portability

Dosu positions itself as a layer, not another silo:

• Knowledge is human-readable and markdown-based.
• It is Open Knowledge Format (OKF) compatible.
• It syncs to GitHub, Confluence, Notion, and more.
• It works with every agent, and the knowledge stays yours — no migrations required.

That matters if you are wary of locking team knowledge into a tool that only one agent can read.

Who it is for

Dosu is aimed at engineering teams running multiple coding agents who want consistent, current context without changing their existing workflows. It is a weaker fit if you have a single agent and a small, stable codebase where context-gathering cost is negligible, or if you cannot connect repos and chat tools to a third party.

What to check before adopting

• Pricing and plan limits: the site links to a pricing page, but the supplied material does not state prices or free-tier terms — confirm directly before committing.
• Agent compatibility: verify your specific agent supports MCP and that the one-command server setup works in your environment.
• Sync coverage: confirm the sources you rely on (your Git host, chat platform, and doc tools) are all supported.
• Measurement: run a representative task before and after to compare token use and iteration time against the vendor's numbers.