Revisions

Each save writes a new revision. update_comment_draft and PATCH /api/v1/apps/:id save the draft and do not publish. name is optional and falls back to the current app name. publish_comment_app and POST /api/v1/apps/:id with { "action": "publish" } publish the current draft.

Active clients read the published revision. Test preview may read the draft with GET /api/v1/config/:appId?preview=draft and must not write production rows. A test key is required for that preview. If there is no draft, the response is validation_error: This Comments app has no draft to preview. A missing published revision on a normal fetch is Comments app not found.

Removing mentionsEnabled or resolveEnabled hides the affordance. Historical comments stay. Comments MCP does not expose Onboard's list_revisions or restore_revision. Revisions still exist on the app. The dashboard and secret REST publish them.

create_comment_app returns nextSteps that tell the agent to update the draft, publish, call ensure_comment_test_publishable, then get_comment_install_snippet. Publish returns the last two of those steps. The same strings are in AGENTS.md.

Related: Configuration · Environments · API overview