Setup Chromium

Chromium Setup Workflow

Routing

Prepare only the Appium Chromium route for Chrome, Chromium, or Edge desktop browsers. Use driver-specific official guidance for an existing runtime failure after setup passes.

Required inputs

Confirm the browser and executable when non-default, global appium mode or explicitly requested local npx appium mode, host OS, permissions, and whether a session-time browser-driver download is authorized.

Workflow

1. Load the global command profile by default or the local profile only when explicitly requested.
2. Load the Chromium profile, shared Appium setup basics, browser prerequisites, and Chromium decision, driver-validation, and smoke references.
3. Run node tools/appium/setup/scripts/check-chromium-env.mjs --format summary --report auto; add --appium-mode local only for explicitly requested local mode. Require top-level summary.requiredOk: true. Apply required fixes in technical dependency order and rerun affected checks. If the gate remains unresolved, report blocked with evidence and the next action. Load the matching example only when needed.
4. Verify appium driver doctor chromium reports 0 required fixes needed, or record not-supported and require the install, list, browser, and smoke gates instead. Use npx --no-install appium ... for the direct check in local mode.
5. Run node tools/appium/setup/scripts/smoke-appium-server.mjs --driver chromium --report auto; add --appium-mode local only in local mode. Require summary.requiredOk: true for server readiness, driver evidence, and cleanup. The smoke reference documents target-specific options. This also requires a browser session to be created and deleted successfully.

Chromium setup safety and approval constraints

• Ask before privileged package-manager commands, browser installation, or a session-time browser-driver download.
• Preserve the selected command mode and existing working browser and driver installations.

Completion criteria

• Appium succeeds in the selected command mode with major version >= 3.
• The installed driver list includes chromium.
• At least one supported Chromium browser is available.
• Doctor reports 0 required fixes needed when supported; otherwise the install, list, browser, and smoke gates pass.
• /status succeeds, logs list chromium, and the minimal browser session helper reports top-level summary.requiredOk: true.

Evidence boundary

Report Appium and driver versions, browser and executable evidence, helper and doctor summaries, /status, server driver evidence, minimal session result, and cleanup.

Self-Improvement Prompt

Before the final response, report any missing, ambiguous, outdated, or retry-causing Chromium setup instruction with its asset path and proposed wording. Leave unrelated assets unchanged.