Reviso FAQ
Everything from connecting your agent to reviewing, versioning, and deciding what ships.
Connecting an agent
- How do I connect my agent?: One command. Run `mcp add reviso` in any MCP-capable agent and it can publish drafts straight into your workspace as reviewable documents. On a single machine you can log in with the CLI instead. No keys to paste in the cloud. Connection runs over OAuth. Command: mcp add reviso # or, on a single machine: python3 -m reviso.cli login
- What is the difference between Cloud and Local?: Cloud connects over OAuth in the browser, so there is no key to paste and it works the same locally and in the cloud. Local mints a token you place in the agent environment for CLI or stdio MCP access on a specific machine.
- Which tools are supported?: Any MCP-capable client such as Claude, Codex, Cursor, and others, plus the Reviso CLI. Cloud uses a single MCP URL over OAuth; local uses the CLI or a stdio MCP command with a token.
- What document formats does Reviso work with?: Agents publish Markdown or HTML. Reviso renders it as a live document your team can read, comment on, and edit, and keeps every saved version so you can diff and roll back.
What agents can do
- How does an agent publish and invite reviewers?: Point the CLI or MCP client at your workspace, publish a draft, and invite a teammate by email with an access level such as comment. Command: python3 -m reviso.cli publish draft.md --workspace-id "$REVISO_WORKSPACE_ID" --title "Launch Plan" --description "Initial agent draft" python3 -m reviso.cli invite create "$DOCUMENT_ID" --email teammate@example.com --access comment
- How does an agent read feedback and update?: The agent pulls the review packet with comments and content-addressed fields, applies changes, and saves a direct revision, keeping the human decision loop intact. Command: python3 -m reviso.cli packet "$DOCUMENT_ID" --format json > packet.json python3 -m reviso.cli update "$DOCUMENT_ID" revised.md --description "Agent revision"
Getting started
- What is Reviso?: Reviso is the content collaboration system for teams and AI agents. Agents write and revise Markdown or HTML through MCP or the CLI; your team reviews, comments, edits, diffs, and rolls back in the browser — every change versioned, auditable, and shipped by a human decision.
- How is Reviso different from Google Docs or Notion?: Those are general-purpose editors. Reviso is content collaboration between agents and teams: agents write and revise, people review and edit, and every change is versioned with one-click rollback and a full audit trail. Nothing ships until a human decides.
- Who is Reviso for?: Teams that want AI agents to draft and revise documents while keeping people accountable for what ships. Writers, reviewers, and owners collaborate in one place with a full audit trail.
The review flow
- How does a review work?: An agent writes a Markdown or HTML draft and opens it for review. Your team comments inline, suggests or makes edits, and compares versions. The agent reads the feedback and saves a revision.
- Can people comment and edit inline?: Yes. Reviewers can leave threaded comments anchored to a selection, edit the document directly, and mention teammates. Comments and mentions notify account members; guest and share links stay comment-scoped.
- How do I know when an agent publishes or updates a draft?: Published reviews appear in your workspace, and comments and mentions notify account members. Guest and share-link activity stays comment-scoped, so outside reviewers never trigger account-only notifications.
- Can I compare versions and roll back?: Yes. Every save is a version. Compare any two versions side by side or unified, and roll back to an earlier one at any time; the rollback itself becomes a new version.
Permissions and sharing
- Do connected agents get extra permissions?: No. A connected agent acts within the workspace permissions of the account that created the connection, checked at runtime on every action. Connecting an agent never grants publish authority. Humans still review, revise, and decide what ships.
- Where is my data stored, and who can see it?: Documents live in your workspace, and access follows workspace membership. Agents connect over OAuth with no keys to paste in the cloud, and guests or share-link visitors are limited to viewing and commenting, and can never publish.
- Can I share with people outside my team?: Yes. You can share a review with people outside your team through invite or share links with a scoped access level. Guests and share-link visitors can view and comment without an account, but cannot publish.
Workspaces and versions
- What is the difference between a personal and a team workspace?: A personal workspace is your own space; a team workspace is shared with invited members whose roles decide who can review, revise, or publish. Both share one workspace model, and access follows each workspace membership.
- Is document history preserved?: Yes. Every saved version is retained. You can compare any two versions side by side or unified, and restore an earlier one. Restoring creates a new current version while earlier versions stay available.