Use docs with an agent

Ask your Opser agent#

Ask your agent how to use Opser—for example, “How do I set up a weekly automation?” or “Where can I change approval settings?” The agent can search and read these guides directly and include links to the relevant pages. You do not need to connect an app or configure a web-search service.

The guides explain how the product works. Your agent checks your workspace separately when the answer depends on your installed apps, permissions, connections, or current settings.

The agent keeps a short-lived copy of the public guides. If the docs site is temporarily unavailable, it can use its last successfully fetched copy and tell you it may be outdated. If it has no copy yet, it reports that it cannot read the docs instead of inventing instructions.

Find the right guide#

Use Search docs, ⌘ K on macOS, or Ctrl K on Windows and Linux. Search covers the published article text and headings. Try “persistent files,” “built-in tools,” “app events,” or “credit rollover.”

Use the section filters to narrow the results. The arrow keys move through matches, Enter opens one, and Escape closes search. Section results take you directly to the relevant heading.

Copy a complete page#

Choose Copy page at the top of a guide. It copies the title, description, source link, and full article as Markdown. Links are absolute, so an agent can follow them after you paste the text into a conversation.

The copied text contains the guide itself, without navigation menus or search controls. If clipboard access is unavailable, choose Markdown and select the text there.

Read the docs without the interface#

Every article has a Markdown link. You can give that URL directly to an agent that can fetch web content; no Opser account or JavaScript is required to read it.

The footer also provides llms.txt, an index linking to every public guide, and All docs as text, the complete documentation in one text file. Start with the index when an agent should choose relevant pages. Use the complete file when you want to supply the whole handbook, allowing for the agent's context limit.

For example, ask an agent to read the documentation index, select the guides about persistent files and scripts, and explain how to reuse an analysis next week. These exports document the public product; they do not connect the agent to your workspace.

Search and reading boundaries#

Search runs against a static documentation index. It does not search private workspace records or conversations, and it does not send your question to an AI service.

JavaScript is needed for interactive search and copying. The articles, Markdown files, navigation, and table of contents remain readable without it. If search fails to load, retry or browse the relevant section.