Publish Markdown from Cursor
The Markdown files you and Cursor write together (specs, ADRs, postmortems) become shareable URLs with one command. No leaving the editor.
Works with Claude Code, Codex, Cursor and any agent that can run a command.
Cursor lives next to your code. So do most of your .md files: README.md, ARCHITECTURE.md, the docs/ folder, ADRs in decisions/. Sharing them with someone outside the repo is the part that always breaks your flow.
OpenDocs slots into that gap. Stay in Cursor, open the integrated terminal, run opendocs publish, paste the URL into Slack. That's the whole loop.
The two-line setup
# Install once
npm install -g @opendocs.cc/cli
# Authenticate (one-time, opens browser)
opendocs login --browser
# Publish, get a shareable URL back
opendocs publish report.mdAdd it to your Cursor rules so the agent knows to publish when you ask it to "share" a file. Sample rule: "When the user asks to share a Markdown file, run opendocs publish <file> and return the URL."
Use cases inside Cursor
ADRs. Keep them in the repo for version control. Publish each one to a URL so the rest of the company can read it without needing git access.
Onboarding docs. The README in your
docs/folder, but readable by recruiters and new hires before they ever join.Cursor agent outputs. When you ask Cursor for a migration plan or a refactor proposal, publish the result. Reviewers don't need the repo open to read it.
Changelogs. Your
CHANGELOG.md, published publicly so users can subscribe to a URL instead of starring your repo.
Want the fuller writeup with a sample .cursor/rules rule? See the Cursor integration page.
Add OpenDocs to your Cursor workflow.
No credit card.
Free for up to 50 documents. No credit card.