reviso-cli

Command line client for Reviso, a content collaboration system where agents publish Markdown and HTML drafts and a human team reviews them.

This is the client half of Reviso. It talks to a Reviso server over HTTP and contains no server code. It has no runtime dependencies: the transport is urllib, so publishing a Markdown file does not pull a dependency graph into an agent's environment.

Install

pip install reviso-cli
# or run it without installing
uvx --from reviso-cli reviso --help

Installs the reviso command. No runtime dependencies: installing it will not pull a dependency graph into an agent's environment.

Quick start

reviso auth login --server https://reviso.work
# opens a browser for consent; use --no-browser to open the URL yourself
reviso doctor --json

reviso publish draft.md --title "Q3 launch plan" --description "Initial draft"
# prints the document URL

reviso documents --json                 # find the document id
reviso packet doc_abc123 --format json  # reviewer comments and version metadata
reviso versions doc_abc123              # read the current version id

reviso update doc_abc123 revised.md \
  --description "Address reviewer feedback" \
  --base-version-id ver_xyz

Browser login

Version 0.2 supports browser consent with a temporary loopback callback and PKCE. Keep the CLI running and open the login URL in a browser on the same computer. reviso auth status shows the selected server and login state without credentials; reviso auth logout removes that server's saved login. Revoke the connection in Settings → Integrations to end its server access.

Credentials live in an owner-only file at ~/.config/reviso/credentials.json (or under XDG_CONFIG_HOME), separately for each server, and refresh automatically. An existing REVISO_AUTOMATION_KEY or --key still supports headless use. The credential lock currently supports macOS and Linux.

The rule that matters

Always pass --base-version-id when you revise a document.

Omitting it is not a safe default. Without it the command re-bases onto whatever version is newest and lets your write win, which silently discards a human's concurrent edit. The safe shape is always two steps:

reviso versions <document_id>        # take the newest version_id
reviso update <document_id> file --description "..." --base-version-id <ver_...>

If the write is rejected as a conflict, re-read and re-apply your change on top of the human's edit. Do not retry with the flag removed.

Command groups

Deliberately not in this client

These are boundaries, not gaps to be filled later:

• No server commands. Starting a Reviso server is not part of the client.
• No share-link creation. A share link carries a bearer token in its URL, and creating one is a browser action where the person handing it out can see who it is going to. Invites by email are here instead.
• No owner or operator surfaces. Metrics, debug replay, and internal replay endpoints are not exposed.

If you need MCP tools rather than a shell, the hosted connector is the better path in most hosts. See reviso-agent for the agent skill.

Known limitations

• publish prints only the document URL. It does not return the document id, so use reviso documents --json to continue from the id.
• update and rollback accept an omitted base version and fall back to last-writer-wins. Always pass the flag. A future release should make the safe behaviour the default.

License

MIT. See LICENSE.

The Reviso product itself is not open source. This repository covers the client only; it grants no rights to the service or its server software. See VISIBILITY.md for the boundary this repository holds, and CONTRIBUTING.md before opening a pull request.

Publish a presentation with its explicit kind so the server validates and renders it as slides:

reviso publish presentation.html --workspace-id <workspace-id> --kind html_deck --deck-contract-version html-deck/1

Ordinary HTML keeps --kind document (the default); deck markup without html_deck is rejected by the server.