The collaborative knowledge base for humans and agents.
Write, organize, and share knowledge in the browser. Let your terminal and AI agents read and update the same pages through the CLI and API.

One page. Every way to work.
Write in the browser, read from the terminal, or let an agent make a targeted edit. Everyone reaches the same page, so there is no second copy to sync and no wrapper to maintain.
Read about the CLI →

Work together without losing control.
Give collaborators View, Edit, or Admin access. When they are connected, everyone can edit the same page in real time and see the collaboration status. If the connection drops, Markdawn switches to read-only instead of accepting edits against stale content.
Read about sharing →
Keep the context with the content.
Link to another page with `[[Page Name]]`. Folders keep related pages together; backlinks show how a page is used elsewhere. Your notes become a path through the subject, not a collection of isolated files.
Read about pages and folders →Give agents boundaries, not a blank check.
Create a named API token and start with read access. When an assistant needs to write, the CLI can make an exact replacement on the current page. It refuses to guess when the passage is missing, repeated, or has changed—so automation does not become a silent rewrite.
Read about agent access →Keep your notes portable.
Import one md file, a folder, or an Obsidian vault. Export a page or the whole workspace from the CLI. Use Markdawn as a hosted service, or run the open-source application on infrastructure you control.
Read about self-hosting →

Before you start.
- Is Markdawn only for AI agents?
- No. Markdawn is for people first, with the CLI and API as direct ways for terminals, scripts, and AI assistants to use the same pages.
- How do people and agents share a page?
- They use the same content layer. A person can write in the browser while a terminal or assistant reads and edits that page through the CLI or API.
- Does Markdawn use md for page content?
- Yes. Page content remains md across the browser, CLI, and API. Titles and access settings are stored separately as page metadata.
- Can I bring existing notes?
- Yes. Import one md file, an md folder, or an Obsidian vault. Keep the original copy until representative titles, links, images, and folders have been verified.
- Can I self-host Markdawn?
- Yes. Markdawn is open source under GNU AGPL v3 and includes a documented deployment path for a VPS with Caddy, Podman, and PostgreSQL.
Start in the browser. Add the CLI when you want a terminal in the loop.





