Skip to content

Configuration

The launcher is a local command. Nothing in this image listens for a public task API.

Where things live

Item What it is
sushi-browser-use Configure a provider and start a demo.
~/.config/sushi/browser-use/provider.json Base URL, model id, and key. Owner ubuntu, mode 0600.
/home/ubuntu/browser-use-results/ One directory per run.
/opt/sushi/docs/demo.sh Local fixture walkthrough.
/opt/sushi/docs/README.md Request-file format and allowed-domain instructions for a custom task.
/opt/browser-use/readback.py Reread a completed directory.

A completed walkthrough includes extracted.json, submission.json, history.json, and result.json. The result file binds the saved artifacts with hashes. Failed runs are left in place.

Provider file

sushi-browser-use configure preserves an existing file and refuses to overwrite it. To change a provider, edit that file locally. Do not pass the key as a command argument. Histories, browser profiles, and raw agent logs can contain page or task content. Treat them as account data.

Custom tasks

Follow the request-file and allowed-domain instructions in /opt/sushi/docs/README.md. Review the task, the site, and the files you authorize. Domain navigation controls are not a firewall and are not an isolation boundary.

Only the ubuntu account should run the launcher.

Last updated November 11, 2026 · Suggest an improvement