saltmd/salt.md

<p align="center"> <img src=".github/banner.png" alt="salt.md" width="100%"> </p> <p align="center"> <b>The open-source workspace for people and AI agents.</b><br> Docs, databases and realtime collaboration for your team. An MCP server sits in the same binary, so an agent works <i>in</i> that workspace instead of talking about it. </p> <p align="center"> <a href="https://salt.md">Website</a> · <a href="https://salt.md/wiki/">Documentation</a> · <a href="#quickstart">Quickstart</a> · <a href="#what-an-agent-can-do">Agents</a> · <a href="https://salt.md/demo/">Live demo</a> </p> <p align="center"> <img src=".github/agent-loop.gif" alt="An agent creates a page and a database; the workspace updates while a person watches." width="100%"> </p>

---

An agent asks to organise the launch notes. A page appears, a database is created, the rows fill in. A person opens the same board a second later and carries on editing. Same pages, same permissions, same history.

That is the whole idea. Everything below is how it works.

Quickstart

curl -fsSL https://raw.githubusercontent.com/saltmd/salt.md/main/install.sh | sh

No curl on the machine? A minimal server image often has wget instead, and the script itself is happy with either:

wget -qO- https://raw.githubusercontent.com/saltmd/salt.md/main/install.sh | sh

That one command downloads the binary for your platform, installs it and starts it, then prints the address to open. On a server it prints that machine's address rather than localhost, which is the thing most install scripts get wrong.

On a Linux server it installs a systemd service rather than leaving a process in your terminal: it starts on boot, restarts after a crash, and your shell is free. Running the same command later upgrades it. Everywhere else it runs in the foreground, which is right for trying it out on a laptop. There is nothing else to install. No database server, no cache, no object store, no separa