Frequently asked questions

In AI workflows you end up with a lot of .md files: architecture docs, changelogs, specs, runbooks. But sharing them is a pain. You either tell your team "open this file in Obsidian" or push to a repo and hope they find it. When you're moving fast, that friction kills momentum. OpenDocs lets you publish any Markdown file to a shareable URL in seconds, straight from the terminal or via your AI agent of choice.

Install the CLI, log in with an API key, and run opendocs publish doc.md. That's it. You get a clean, readable URL like opendocs.cc/you/doc-name that anyone can open in a browser. No git push, no deploy pipeline, no wiki to maintain. If you're using an AI agent, point it to our SKILL.md and it can publish, update, and export documents for you.

By default, documents are workspace-visible, meaning only members of your workspace can view them. This is the safe default for internal notes, specs, and drafts. If you want to share a document publicly (anyone with the link can read it), you explicitly set --visibility public. You're always in control.

Absolutely, that's what it's built for. Claude Code, Cursor, GitHub Copilot, Cline, Aider, Hermes Agent, Codex, OpenClaw, and any tool that can run terminal commands can publish to OpenDocs. The agent writes a Markdown file, runs the CLI, and hands you the link. The --json flag makes it easy for agents to parse the output programmatically.

We provide a SKILL.md file that teaches any AI agent how to use the OpenDocs CLI. Point your agent to the skill and it will know how to install the CLI, authenticate, publish, update, and manage documents on your behalf. This works with agents like OpenClaw, Hermes Agent, Claude Code, and any agent framework that supports skill files.

Free ($0) gives you 10 published documents, 1 workspace with up to 3 members, public publishing, PDF export (with a small "Made with OpenDocs" footer), API keys, and the CLI. Pro ($8/month, or $6 billed yearly) unlocks unlimited documents, 2 workspaces with up to 5 members each, Word (.docx) export, and full branding customization (colors, fonts, logo, footer). Team ($4/user/month, 3-seat minimum, or $3 billed yearly) adds unlimited workspaces and members, role-based permissions, and priority support. API access, the CLI, and public publishing are on every plan.

Yes. Run opendocs export my-doc -f pdf to get a formatted PDF, or -f docx for an editable Word document. You can also customize the output with --landscape for landscape orientation and --accent-color to match your brand. The exported files are print-ready with proper typography and formatting. AI agents that use the SKILL.md can handle exports for you too. Just ask your agent to export a doc to PDF.

Absolutely. Pass multiple slugs or IDs to the export command: opendocs export doc-1 doc-2 doc-3 -f pdf. Batch exports support up to 10 documents at once and deliver them as a zip file. Use -o ./exports to specify an output directory.

Yes. Run opendocs update doc.md --post-id <id> and the document gets a new version. The URL stays the same, so anyone who already has the link sees the latest version automatically. Previous versions are preserved in the version history. AI agents with the SKILL.md can update existing docs without you touching the terminal.

No. Public documents can be read by anyone with the link, no signup or login. Workspace-visible documents require the reader to be a member of your workspace.

Yes. Run opendocs pull <postId> to download the raw Markdown to a local file. You can also pipe it with --stdout. This makes the round-trip workflow easy: publish, share, get feedback, pull, edit, update.

Your account reverts to Free at the end of the billing period. If you have more than 10 published documents, they all stay live and readable. You just can't publish new ones until you're under the limit or upgrade again. Word exports stop being available, and new PDFs start carrying the "Made with OpenDocs" footer again. Nothing gets deleted.

The OpenDocs CLI is open source under the MIT license, so the command-line tool agents and developers run locally is inspectable and forkable. The hosted web app, API, and document-conversion service are closed source for now while we build the business. You can find the CLI on GitHub.