What to ask your agent
Once OpenDocs is set up, you work with it by asking your agent. There are no special phrases: say what you want the way you'd ask a colleague. These prompts show what's possible and what happens when you ask.
Your agent checks with you before anything that's hard to undo or reaches other people: making a document public, changing the export theme, sending a document for signing, deleting.
Publish and update
| Ask | What happens |
|---|---|
| "Publish the launch plan." | The Markdown becomes a link only your workspace can open. |
| "Write release notes for v2.4 and publish them." | Your agent writes the file, then publishes it. |
"Publish everything in the docs folder." | One link per file, in one batch. |
| "I edited the handbook, update it." | Same link, new version. Nobody needs a new URL. |
| "Publish this without an account." | A link anyone can open for 24 hours, plus a claim link to keep it. |
More: Publish, Sync a folder.
PDF, Word and branding
| Ask | What happens |
|---|---|
| "Send me the board report as a PDF." | A typeset PDF lands next to the Markdown file. |
| "Publish the proposal and give me a Word file too." | A link and a .docx (Pro and Team). |
| "Export everything in the Investors project as PDFs." | One PDF per document, in a folder. |
| "Use the Boardroom preset with our logo." | Every export follows it from now on. Your agent asks you first. |
| "Make our brand color navy and the font IBM Plex Sans." | Same, with your own color and font. |
More: PDF, Word and branding.
Organize
| Ask | What happens |
|---|---|
| "Put this in the Product project." | Filed under opendocs.cc/<workspace>/projects/product/... |
| "Start a project for the Northwind engagement." | A new project for that body of work. |
| "Move the old specs to Archive." | The documents move; their content doesn't change. |
| "What's in the Investors project?" | A list of its documents with their links. |
More: Projects, Find, download and remove.
Share
| Ask | What happens |
|---|---|
| "Share the onboarding handbook with dana@halvard.example." | Dana gets an email and can read that one document. |
| "Let anyone at northwind.example read the proposal." | Everyone with a verified email at that domain can open it. |
| "Make the changelog public." | Anyone with the link can read it. Your agent confirms first. |
| "Keep the salary bands private to me." | Only you can open it. |
| "Invite Sam to our workspace." | Sam gets an invitation email to accept. |
More: Who can see a document, Workspaces and teams.
Versions
| Ask | What happens |
|---|---|
| "Who changed the pricing spec, and when?" | Every version with who published it and through which agent. |
| "Show me what the spec said on Monday." | The Markdown of that version. |
| "Roll the spec back to yesterday." | The old content comes back as a new version. History is kept. |
More: Updates and versions.
Google Drive and e-signatures
These need Pro or Team and a one-time connection in the dashboard's Integrations tab.
| Ask | What happens |
|---|---|
| "Save the board minutes to the Board Minutes folder as a PDF." | The file lands in that Drive folder, and OpenDocs keeps a record. |
| "Send the consulting agreement to Ines Duarte, ines@northwind.example, for signing." | Your agent prepares a draft, shows you the signers, and sends only when you confirm. |
| "Has Northwind signed yet?" | The status of each signer. |
| "Download the signed agreement and file it in Signed Agreements." | The signed PDF and its audit certificate, saved to Drive. |
More: Google Drive, E-signatures.
Tips
- Name the project when a document belongs to a client, product or team. Your agent files it there, and the URL says where it lives.
- Say who it's for. "For the team" keeps the default. "For the client" usually means sharing with their email or exporting a PDF, not making it public.
- Ask for the link back. Your agent always gets one; asking makes it end its reply with it.