automation: Agent Canvas documentation image requests — 2026-08-29

[DevinVinson]

This issue was created by an AI agent (OpenHands) on behalf of the user.

Audit record

Source SHAs

• OpenHands/OpenHands: f26d734a848297d8dcf460b0bb739174e76511f0
• OpenHands/docs: 5a75b32c7f1e93811e8ccf440ad577307cc35bd6

Pages reviewed

All 36 pages currently listed in the Agent Canvas tab of docs.json: overview, architecture, installation, automations and their prebuilt guides, conversations, profiles, ACP agents, plugins, extensions, Critic, settings, backend connection and deployment guides, development, troubleshooting, mobile access, and release notes.

Reviewed in-scope prose and image references; relevant openhands/static/img assets and their history; current Agent Canvas source; mock-LLM E2E journeys; all open and closed OpenHands/docs issues; and open/draft PRs. A final duplicate check found the active general image queue issue #752 and its implementation PR #753, which cover the conversation overview panel but not Canvas Extensions.

Safety and scope

Agent Canvas is read-only; OpenHands/docs is the sole write target. Capture data must be synthetic. No secrets, personal data, real local paths, private URLs, or real conversation content may be captured. Use the OpenHands-Neutral theme.

Requested image

1. Add — Canvas Extension installation form
   • Target page / exact prose anchor / change: openhands/usage/agent-canvas/canvas-extensions.mdx, ## Install an Extension, immediately after “Open Customize > Extensions, then select Add extension.” Add.
   • Intended filename / descriptive alt text: agent-canvas-add-extension.png; “Agent Canvas Add extension dialog with synthetic source, ref, and repository path fields.”
   • Material reader benefit: The documented Git Repository procedure requires readers to locate and distinguish three meaningful fields—source, optional revision, and optional repository subdirectory—before submitting. A focused capture materially clarifies the control locations and avoids confusing extension source configuration with plugin or backend setup.
   • Exact UI state: On Customize > Extensions, display the Add extension dialog before submission. Populate the source, ref, and repository-path fields; leave the primary Add extension action enabled. Do not show an installed extension, trust confirmation, browser chrome, terminal, or external UI.
   • Synthetic records / data: Source github:demo-org/demo-canvas-extension; ref v0.1.0-demo; repository path extensions/demo-page. These are illustrati - Synthetic records / data: Source github:demo-org/demo-canvas-extension; ref v0.1.0-demo; repository path extensions/demo-page. These are illustrati - **Synthetic mo - Synthetic records / data: Source github:demo-org/demo-canvas-extension; ref v0.1.0-demo; repository path extensions/demo-page. These are illustrati - Synthetic records / data: Source github:demo-org/demo-canvas-extension; ref v0.1.0-demo; repository path extensions/demo-page. These are illustrati - **Synthetic mo - **Synthetic records xtension-modal, add-canvas-extension-source-input, add-canvas-extension-ref-input, add-canvas-extension-repo-path-input, and add-canvas-extension-submit`. Use the E2E API route only to provide the extension feature surface; stop before its installation mutation.
   • Crop / context guidance: Include the complete dialog, its field labels, optional/required indicators, populated synthetic values, and enabled primary action. Retain only enough dimmed Canvas surface to establish it is an Agent Canvas modal. Exclude browser chrome, sidebars, diagnostics, developer tools, the full underlying extension inventory, and all environment-specific text.
   • Theme requirement: OpenHands-Neutral.
   • Safety / privacy checks: Confirm all three populated values match the synthetic data above; the action is not submitted; no secrets, masked credential fields, personal data, real local paths, private URLs, real repository content, or conversation content are visible. Do not capture an external or third-party surface.
   • Acceptance criteria: At documentation width, the image clearly shows Add extension, the required Source field, optional Ref and Repo path fields, each stated synthetic value, and the enabled add action. It accurately matches the current modal, visibly supports the three-field Git Repository procedure, and contains only the OpenHands-Neutral synthetic Canvas state.
   • Priority / confidence: P2 / High.

Rejected or deferred candidates

• Conversation overview panel: deferred as actively covered by issue automation: Agent Canvas documentation image requests — 2026-08-24 #752 and open PR docs: add Agent Canvas visuals from image request #752 #753.
• Backend connection form and saved LLM profile manager: rejected because accurate dedicated assets already exist following the earlier image queue.
• First-time setup, automation import preview, and Critic settings/results: rejected because each material state already has an accurate screenshot.
• Extension enablement, trust confirmation, and sidebar page: deferred: the installation form is the more compact and independently actionable capture for the three-field procedure; avoid overlapping requests in this run.
• Conversation branching, archive/filter controls, and plugin attachment: deferred because the audited mock-LLM suite lacks a dedicated capture-ready journey for these states without adding capture-only setup.
• Prebuilt GitHub and Slack automation flows: rejected because representative states require credentials or third-party UI.
• Architecture, installation, self-hosting, and troubleshooting: rejected because diagrams, code, or terminal output communicate the information better than an Agent Canvas screenshot.

[DevinVinson]

Draft PR: #769

This comment was created by an AI agent (OpenHands) on behalf of the user.