pilion-browser

# pilion-browser Before any browser task, locate the command and read its installed guide: ```bash command -v pilion # If missing, try the app-installed command before asking for setup: test -x "$HOME/.local/bin/pilion" export PATH="$HOME/.local/bin:$PATH" pilion skill ``` and follow its output. It prints the usage guide that matches the installed Pilion version. Run it again after Pilion updates, or when any output says to. The guide ends with a line starting `[pilion:skill] end of guide`. If that line is missing, the output was truncated: save it to a unique temporary file and read it in parts, for example `PILION_GUIDE_FILE=$(mktemp); pilion skill > "$PILION_GUIDE_FILE"`. Do not continue from an incomplete guide. Check `pilion status --json` before the first browser operation. Follow the guide for one recorded Space per conversation, explicit `--space` and tab IDs, exact refs, approvals and outcome verification. An explicitly exported `PILION_SPACE` is an alternative within that shell; do not inherit another task's Space, and do not assume exports persist across tool calls. When a shell returns a running-command handle, poll that command; do not start a duplicate effect. Report a timeout as an uncertain outcome until you verify the page. For review or sign-in, ask the person to view the task Space in Pilion's sidebar; `activate` does not switch their view in an Agent Space. At task completion, close only this conversation's recorded Space. `space list` can include other conversations; never stop their work to free capacity. On `SPACE_ENDED` or user takeover, report the interruption and wait for the person's agreement before creating a replacement; never silently retry, switch Spaces or recreate one. Follow the guide for idle/restart resumption. ## References - [Install Pilion and connect it to agents](references/install.md) — read when `pilion` is not found, when `pilion skill` reports an unknown command, or when `pilion status` reports a problem.