Skip to content

Troubleshooting

The walkthrough does not print SUSHI_CUSTOMER_DEMO_PASSED

Cause: the form submission or the independent readback did not match the three expected records.

Fix: keep the result directory. Rerun readback against that directory with /opt/browser-use/readback.py. Start a new attempt in a new output directory. Do not delete a failed run to hide the error.

Chromium does not start

Cause: the sandbox failed to initialize. The public guide points at AppArmor and kernel logs.

Fix: read journalctl for sushi-browser-use-firstboot.service and the kernel log from an administrative session. Leave the sandbox enabled.

Provider setup refuses to write

Cause: ~/.config/sushi/browser-use/provider.json already exists. Setup does not overwrite it.

Fix: edit the existing file locally, or move it aside only after you have stored the key somewhere else. Keep mode 0600.

A provider-backed demo calls the model and still fails

Cause: the model did not satisfy the JSON schema, did not select the DOM tool, or the form readback failed. The run allows four agent steps and does not retry the provider.

Fix: confirm the model supports JSON schema structured output. Keep the failed directory. Use a new output directory for the next run. Provider charges for the attempts that were sent are separate from the software fee.

Last updated November 11, 2026 · Suggest an improvement