Docsmith
Shared memory for your team. Runbooks, conventions and decisions in one searchable place — readable by the people who need them and by the agents working alongside them.
Try it: docsmith.app
What it is
Docsmith is a documentation platform for teams — runbooks, conventions, notes and decisions kept somewhere searchable instead of scattered across heads and Slack threads. Documents start from a type with named sections rather than a blank page, comments anchor to the exact sentence they're about, and superseded documents say so everywhere they appear, including in search results.
The problem
Most team knowledge lives in two bad places: someone's head, or a Slack thread nobody can find again. The tools meant to fix that usually assume everyone is comfortable with Git, which quietly excludes half the people who hold the context worth writing down. And when documentation does exist, the hard part isn't finding a page — it's knowing whether to trust it.
What it does
- Typed documents that open with named sections, not a blank page
- Threaded comments anchored to the exact sentence
- Supersession tracking, so stale docs announce themselves
- Full-text search ranked and matched section by section
- Access control at workspace, space and document level, with revocation that actually revokes
- An MCP server, so Claude or another agent can read, search, write and comment — strictly as you, with your permissions
Why the agent part matters
The reasoning behind a decision — why this approach, what was ruled out — increasingly lives in a prompt or a chat window, and then the session ends. The code survives; the rationale doesn't. Giving agents a first-class way to read and write the same team memory as the humans is an attempt at fixing that at the source rather than hoping someone writes it up afterwards. I wrote about the wider problem in Cognitive Debt.
The stack, and why
Next.js and React on the front end, a FastAPI backend in Python, and an MCP server exposing the same operations to agents. Keeping one permission model behind both the UI and the MCP surface is the whole point — an agent should never be able to read something its operator can't.
Status & what's next
Live at docsmith.app.