AI agents and developers
Autodocs CLI
Autodocs has a command line: `autessa autodocs` generates, edits, publishes and converts docs, and `autessa browser-workflows` lists and runs workflows.
THE PROBLEM
Documentation should be scriptable too
Ops and engineering teams want to publish, convert and run in bulk. Autodocs and browser workflows have full command-line coverage.
Everything in Autodocs works from the Autessa CLI: list, generate, edit and publish docs, and list, read and run browser workflows from scripts.
How it works
How does autodocs cli work in Autodocs?
- 1
Install the Autessa CLI and sign in
See the developer docs for setup.
- 2
Work with docs
`autessa autodocs list`, `get`, `generate`, `save`, `publish`, `create-workflow`, `create-agent`, `delete`.
- 3
Work with workflows
`autessa browser-workflows list`, `steps`, `run`, `run-status`, `delete`.
- 4
Use it from Autobots
Autobots with a browser get the same CLI as a tool, so they can manage docs and workflows when you ask.
Options and settings
Every option, in one table
| Command | What it does |
|---|---|
| autodocs list | Docs in the Autodocs Drive, newest first, with status, steps, refresh time and changes. |
| autodocs get | One doc’s Markdown and links to its pictures. |
| autodocs generate | Writes a draft from a recorded workflow, with an optional title. |
| autodocs save | Replaces a doc’s article with edited Markdown. |
| autodocs publish | Publishes a draft into the knowledge base. |
| autodocs create-workflow | Turns a doc’s numbered steps into a browser workflow. |
| autodocs create-agent | Creates an agent that re-runs the doc’s recorded steps. |
| autodocs delete | Moves a doc to the Autodocs Drive’s trash. |
| browser-workflows run | Replays a workflow in an Autobot’s browser and waits for it to finish. |
| browser-workflows run-status | The running step and how many ran or failed. |
Who can do what
Permissions
| Who | Can |
|---|---|
| Anyone signed in to the CLI | Acts as themselves, with the same access they have in the app. |
| The person who recorded a workflow | Sees its steps, renames it, replays it and deletes it. Workflows are personal. |
AI assist
Where AI helps
AI is used where it saves you work and is always visible: it writes the guide from your recording, and it finds elements that moved during a replay, marking those steps healed. You stay in charge of what gets published.
Connects to
How it fits with the rest of Autodocs and Autessa
FAQ
Autodocs CLI: questions
Is there an API for Autodocs?
Yes. Every Autodocs action is available through the Autessa CLI and API: list, get, generate, save, publish, create-workflow, create-agent and delete.
Can I run a workflow from a script?
Yes. `autessa browser-workflows run` replays it in an Autobot’s browser and waits for the result.
Can I record from the CLI?
Recording happens in the web app’s browser, or by an Autobot in its own browser. The CLI lists, runs and manages what was recorded.
Try autodocs cli on a task you do every week.
Record it once in Autodocs. You get the guide for your team and the workflow for next time.
No extension to install · nothing is published until you publish it
100% customizable, code and all
Make Autessa Autodocs fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours