Opentrons App

Operate the official Opentrons desktop application through the open-computer-use / ocu CLI or its MCP tools.

Core workflow

Verify Open Computer Use is available with ocu -h when its tools are not already exposed by the host.
Ask the user to open the Opentrons App if it is not already running. On Windows and Linux, do not assume Open Computer Use can launch it.
Call list_apps and use the exact matching app or process name.
Call get_app_state before acting. Use text_limit: 1000 or "max" when protocol details, warnings, or run logs are truncated.
Prefer a current element_index and semantic actions. Use window-relative coordinates only when the accessibility tree does not expose the target.
Re-read state after navigation, modal dialogs, robot reconnects, protocol import, or failed actions. Never reuse an index after a major UI change.
Verify the selected robot, robot model, protocol, pipettes, modules, labware, deck locations, and run state against the user's request.
Pause for approval before any consequential action listed below.
Inspect the refreshed state and report what the app shows after every consequential action.

For screen-oriented procedures and recovery guidance, read references/app-workflows.md.