# Launch Post

Hi all. My team has been building Markbase for the past few months and it’s now OPEN SOURCE and free to use.

**The problem**

My team writes with agents all day, but not with the same one. One person uses Claude Code, another Codex, another Cursor or Gemini. Three things kept going wrong:

- **Context lives in too many places.** Each agent has its own context: a [CLAUDE.md](http://CLAUDE.md) here, an [AGENTS.md](http://AGENTS.md) there, a spec pasted into a chat. The team’s knowledge needs one home that every agent can read and write, with access control on who sees what.
- **Not everyone reads markdown.** Markdown is what agents read and write best, but PMs, designers and ops people don’t want to edit raw `##` and `- [ ]`. They need a normal editor for the same files.
- **Clients are left out.** An agent can write a plan in minutes, but there’s no easy way to share that plan, or the progress on it, with an external client without exporting it to some other tool.

**What Markbase does**

- **A vault is a folder that syncs.** Mount it anywhere on your disk. Your agents read and write plain `.md` files there, with no integration and no API key handed to the agent. The same documents are available in the browser and the desktop app, and edits from people and agents merge instead of overwriting each other.
- **A WYSIWYG markdown editor** so non-technical teammates can write and edit the same files without seeing markdown syntax.
- **Version history and comments.** Every change is attributed to the person or agent who made it, so you always know what an agent changed and can undo it. Comments are anchored to the exact line.
- **Publish and share.** Share a document with teammates as viewer, commenter or editor, or send a link to someone who has no account.

**How we use it**

- **On-call.** The incident is a document. The agent reads the logs and writes down what it sees, quoting the lines. People check the findings with comments on the exact line. The agent proposes the fix in the document, and a person approves it before it’s applied. The postmortem timeline writes itself from the history.
- **Docs next to your code.** Put the vault in your repo (`docs/` or the root). Engineers and their agents edit the files in the working tree. PMs and designers edit the same specs in the browser. Everyone, human or agent, works from one version.
- **Keep clients in the loop.** Send a client a link to the plan, with no account needed. They see the current version every time they open it and can comment on the exact line they have a question about. When your agent updates the plan, the client sees it.

**Try it**

- Open source: <https://github.com/Markbase-Team/Markbase>
- Free to use at <https://markbase.so>, or self-host it (Supabase plus Vercel or Docker; there’s a guide in the docs)
- Docs: <https://markbase.so/docs>
