Invite a teammate
v11Invite links expire after 7 days.
Acceptance criteria
- Only workspace admins can send invites.
A home for yourknowledge base, live PRD, shared notepad, or agent context.
Write together, keep it current, and make it yours.
Write the brief
Saving…Human in browser Agent in CLI
Scroll to see the workflow
Your documents. Your way.
Make room for what matters.
Keep a knowledge base. Shape a live PRD. Share a notepad. Give an agent context. Start with Markdown and choose how you use it.
An idea in a Markdown file.
A living document in your own space.
One example: a live PRD.
From the first brief to the next decision.
01Define
Give your agent a shared starting point.
Write the requirements in a team document. Your agent reads the same Markdown through the CLI, so the brief stays connected to the project.
Human writes the brief. Agent reads the source.
release-brief.mdv11
Invite a teammate
Invite links expire after 7 days.
Only workspace admins can send invites.
Acceptance criteria
Define the expired-link behavior.
Illustrated with sample content.
release-brief.mdv11
Invite a teammate
Invite links expire after 7 days.
Only workspace admins can send invites.
Acceptance criteria
Define the expired-link behavior.
Illustrated with sample content.
Bring your tools, too
Your Markdown, from the terminal.
Use the CLI yourself or connect a coding agent to read documents, edit Markdown, and follow discussions.
01
Read documents
See the space's documents and unresolved messages for agents, then read the Markdown you need.
ourdoc context
ourdoc docs read DOCUMENT_ID02
Update documents
Save against the version you read. If someone changed the document, a conflict asks you to read and reconcile first.
ourdoc docs update DOCUMENT_ID \
--file brief.md --expected-version 1203
Read team discussions
Fetch messages marked for agents and reply on the same document. Decisions stay with their context.
ourdoc discuss list DOCUMENT_ID --relay-agentsNewer work deserves to stay.
Version-aware CLI writes protect changes made while an agent was working. A stale update returns a conflict so the agent can read the latest document and reconcile its changes.
expected-version → 409 Conflict → re-readStart with a document
Set up in three steps.
Create a space and write your first document in the browser. Invite collaborators when you need them. Connect the CLI if it fits your workflow.
Read the setup guide- 01
Create a space
Choose a personal or team space and add your first Markdown document.
- 02
Make it your own
Organize your documents and invite the people who need access to a team space.
- 03
Connect your tools, if you want
Use init to connect a project. Then read and update the same documents through the CLI.
ourdoc init
The whole workspace around your document
Collaboration tools, included.
Write together in real time
People share live edits and cursors in the browser. Saved document updates stay connected to the same workspace.
Discuss where the decision belongs
Keep questions and replies on the document, with messages your agent can fetch as part of its context.
Review and restore earlier work
See document history and restore a saved version when a decision needs to change.
Access that follows the team
Shared spaces use team roles. Agent access is scoped to the approved space. Your personal notes remain private.
Keep Markdown as the source
Write in the visual editor or Markdown source. People and agents access the same saved content.
Understand more with Friendly AI
Get a plain-language explanation of a saved document without changing its source.
A few things worth knowing
How the shared space works.
What can I use ourdoc for?
ourdoc hosts Markdown documents. Use a space as a knowledge base, a live PRD, a shared notepad, or context for your tools. You choose the structure and the workflow.
What happens in real time?
People can write together with live cursors and shared edits. Saved agent updates appear in the workspace. Agents read and publish through CLI requests; they do not stream live typing into the editor.
Does marking a message start my agent?
No. It makes the message available for your agent to fetch. Your coding agent runs in its own environment and chooses when to read or respond.
What if a person and an agent edit at the same time?
Browser collaborators share live edits. CLI updates include the version they were based on. If that version is stale, the update returns a conflict instead of silently replacing newer work.
Who can access the documents?
Your personal space is private. Shared team spaces follow team membership and editor or viewer roles. Connecting an agent requires approval for that space; a document link does not grant access.
For whatever you want to write together.