What a workspace is actually for.
Markbase is one primitive — a Markdown workspace your agents share over MCP. These are the jobs teams reach for it to do, and the shape each one takes in practice.
- Decisions & precedent An agent that can't see why you chose Postgres over Redis will cheerfully propose Redis again. A decision log it can query turns settled questions into constraints.
- Session handoff Context windows end; the work doesn't. Write a handoff into the workspace and resume it in a fresh session — on another machine, or with another agent.
- Agents from different vendors Different models are genuinely better at different jobs. The one thing they have in common is MCP — so make the memory the thing they share.
- Parallel agent fleets Fan a job out across a fleet and they all reach for the same file. Every write says which version it's changing, so the loser of a race is told, not silently overwritten.
- Onboarding an agent The first thing a fresh agent does is read the workspace — what the system is, what's settled, how to work here — instead of asking you or guessing.
- Background & scheduled agents A nightly run has nowhere to put what it found. Give it a folder and the report is waiting in the morning — for you, and for the next run.
- Research & deliverables Agents produce spreadsheets, PDFs and rendered charts. Keeping them at the same paths as the notes that cite them is what makes the analysis reproducible later.
One primitive
These aren't seven features.
Every page above describes the same small set of things: Markdown
documents at paths, folders that carry their own conventions in an
_markbase.md, typed collections where a shape keeps
recurring, files stored beside the notes that cite them, and writes
that assert the version they're changing.
What differs is the folder layout and who reads it. A decision log and a nightly report queue are the same collection primitive pointed at different problems. That's the point — you don't adopt a feature, you give your agents a place to put things and then shape it.
None of this requires Markbase to run your agents. It doesn't schedule them, orchestrate them, or sit in their loop. Your harness keeps doing that. Markbase is the workspace they all reach.
Free plan, no card
Pick the one that sounds like your week.
If one of these is a problem you've been solving with a synced folder and a lot of copy-paste, you can have the real thing set up before lunch. Starting costs nothing, and we'd genuinely like to hear which of these you reached for first.