---
{
  "id": "platform.image_editor.overview",
  "topic": "image_editor",
  "title": "Live Image Editor collaboration overview",
  "locale": "en",
  "version": "2026-07-24",
  "summary": "Image Editor actions collaborate with a user-visible browser session under an explicit, revocable Agent grant.",
  "content": "The `image_editor` family collaborates only inside an Image Editor that the user currently has open. The user's browser executes each command and applies its visible result; these are not server-side, one-shot image tools. `list_sessions` discovers eligible live sessions, `select_region` replaces the active selection, `request_edit` runs a billed edit against that selection, `undo` steps back browser canvas history, and `export` writes the current canvas as a new project revision. Read the live action schema instead of copying field shapes from this card.\n\nAuthorization has two independent gates: an explicit session-lifetime grant to this Agent and current Agent `write` permission on the image project in the database. Every call rechecks project permission. Registry `ConfirmationPolicy::None` does not remove consent; the live grant is the UserConfirm boundary. The user may revoke the grant or take over at any time, cancelling an in-flight command with `grant_revoked` or `user_takeover`. Treat either outcome as normal collaboration and do not retry around it.\n\nA `sessionId` is temporary in-memory state. Closing the editor or losing its browser connection invalidates it, so always begin with `list_sessions`; never invent an ID or reuse one from an earlier turn. Every listed session and every command result carries `projectId` context. All five Image Editor actions are unavailable on public surfaces. Current registry definitions, action results, typed errors, and project state override this card.\n",
  "aliases": [
    "image editor",
    "image edit session",
    "edit session",
    "live retouching",
    "retouch",
    "圖片編輯器",
    "修圖"
  ],
  "tags": [
    "image-editor",
    "overview",
    "live-session",
    "grant"
  ],
  "relatedActions": [
    "arinova.image_editor.list_sessions",
    "arinova.image_editor.select_region",
    "arinova.image_editor.request_edit",
    "arinova.image_editor.undo",
    "arinova.image_editor.export"
  ],
  "relatedActionPrefixes": [],
  "url": "https://docs.arinova.ai/en/kb/image_editor/overview/"
}
---

The `image_editor` family collaborates only inside an Image Editor that the user currently has open. The user's browser executes each command and applies its visible result; these are not server-side, one-shot image tools. `list_sessions` discovers eligible live sessions, `select_region` replaces the active selection, `request_edit` runs a billed edit against that selection, `undo` steps back browser canvas history, and `export` writes the current canvas as a new project revision. Read the live action schema instead of copying field shapes from this card.

Authorization has two independent gates: an explicit session-lifetime grant to this Agent and current Agent `write` permission on the image project in the database. Every call rechecks project permission. Registry `ConfirmationPolicy::None` does not remove consent; the live grant is the UserConfirm boundary. The user may revoke the grant or take over at any time, cancelling an in-flight command with `grant_revoked` or `user_takeover`. Treat either outcome as normal collaboration and do not retry around it.

A `sessionId` is temporary in-memory state. Closing the editor or losing its browser connection invalidates it, so always begin with `list_sessions`; never invent an ID or reuse one from an earlier turn. Every listed session and every command result carries `projectId` context. All five Image Editor actions are unavailable on public surfaces. Current registry definitions, action results, typed errors, and project state override this card.
