Codestin Search App

Macro Docs

Agent-editable, collaborative, @linked, version-controlled, mobile-friendly, markdown-native documents.

Why Macro Docs?

Every document is a CRDT with its own Durable Object in the cloud. Edits merge in order, so two people can type on the same line without overwriting each other.

Everyone can type on this line at the same time — and it never conflicts.

How it stays in sync

Edits apply locally first, then reconcile in the background.

No round-trips to a central database. The actor is the source of truth.

Offline changes replay when you reconnect.

Power in simplicity.

At the end of the day, a Macro Doc is just a markdown file. As simple as you want it to be, with advanced features when you need them. Collaborate online, smart link to other Macro entities, loop in agents, edit offline, or export for another markdown editor.

Nothing is trapped in a proprietary format.

A Macro Doc is just a markdown file.

Open source
Macro fully open source on Github. Audit it, fork it, or extend it.
Built for mobile
Blocks, properties, comments and live cursors all work on mobile.
Stable offline
CRDT-backed: keystrokes apply locally first, then replay in order on reconnect.

Mention and link
as you type.

Mention a person, a task, a date, an email, a channel, or another document.
Insert snippets of other documents with ';'

Markdown example

Hello @evan

Please take a look at Preserve filter settings between tabs

You can talk to me at https://cal.com/jacob-beckerman-b56mrn/30min

Book a slot for Tomorrow

Agenda1

Check in

Filter discussion

Before we meet

Read the investor email thread: Q4 Report

Post any updates to Engineers

Deeply integrated
with your workspace.

@mention a task, channel, document, email thread, agent, or company to share it with everyone in the doc.

Agents edit
like teammates.

As many agents as you want can join you in the doc simultaneously. They don't lock your document, you see their actions in realtime.

The outage started at 02:14 and ran for forty one minutes before the edge workers recovered without anyone intervening. Root cause was a stale connection pool that never got recycled after the config push.

Nobody is on the hook for the pool itself. It behaved exactly as configured, which is the part worth writing down before the next person reconfigures it the same way.

Impact is smaller than it felt at the time, and the retry budget is the part that actually needs fixing rather than the pool: 1,240 requests failed, and the retry budget was exhausted by 02:31, which is why the second wave never got through at all.

Owen has the customer note in draft and is waiting on numbers before it goes out, so the follow up work here is narrow enough to name: connection limits per worker, plus a retry budget that resets per minute rather than per hour.

Postmortem is on the calendar for Tuesday. Bring the graph of pool age against error rate, because the shape of it is the whole argument for recycling on every config change.

Rewrite history.

Restore any timestamp.
See who did what.
Fork it into a new doc.

Leverage links
to cross-connect your docs.

Link to literally anything that exists in Macro.
Format a link as text, a card, or an icon.
Agents can add, edit, and navigate links.

A Macro document @linking last week's notes, four tasks, an email and a channel, with teammate and agent cursors in the text.

Type @ to insert a live link to anything in your workspace
ExampleTask mentions show current status, priority, and assignee
Example@linked email threads get shared as live documents, no need to forward or BCC

Type @ to insert a live link to anything in your workspace
Task mentions show current status, priority, and assignee
@linked email threads get shared as live documents, no need to forward or BCC

How does Macro Docs stack up?

Macro

Notion

Obsidian

Google Docs

Confluence

Inline comment threads

Search workspace and connected sources

Real-time collaboration + offline editing

Properties / database experience

Markdown-native documents

Version history & fork a past version

@mention people, docs, tasks & channels

Agents with workspace context

Built-in tasks, CRM & email

Live agent cursor in the document

Open source (AGPLv3)

Full support Partial / limited Not available

How is Macro Docs different from Notion?

Macro Docs uses Markdown and supports real-time, offline-capable editing. Documents link directly to related tasks, email, and channels.

Are docs collaborative?

Yes. It uses CRDT-based real-time editing, includes inline comment threads, and shows a live agent cursor while an agent works in the document.

What are properties?

Properties add structured fields such as status, assignee, dates, and links alongside the document.

Can agents edit my docs?

Yes. Agents can draft or revise documents, and you can see their cursor move through the document in real time.

Is there version history?

Yes. Every document keeps a full version history, and you can restore or fork a past version.

Is Macro open source?

Yes. Macro is open source under the AGPLv3. The code is on GitHub.

Is our workspace data secure?

Yes. Open source means the Macro application code is available to inspect. It does not make your workspace public. Data in your Macro account, including your team’s email, documents, messages, and other workspace content, remains private and secure.

Let's get started.

It takes 30 seconds to connect your account and bring docs, tasks, email, channels, and agents into shared memory.

Get started

Book Demo Switch to Macro Jobs Partners Terms Privacy DPA

Collaborativemarkdown docs.

Why Macro Docs?

Power in simplicity.

Open source

Built for mobile

Stable offline

Mention and linkas you type.