joakimp
6625d66f3a
Discoverability follow-up to baking agent-browser into the base: agents won't reach for a browser they don't know they have (the exact gap that made this capability easy to miss). Add a short pointer section to the pi-devbox managed block — capability, the preset AGENT_BROWSER_EXECUTABLE_PATH, and `agent-browser skills get core --full` for the command set. Pointer only; depth stays in the skill. rootfs change → folds into the same base-<hash> rebuild. CHANGELOG note updated.
2.5 KiB
Running inside pi-devbox
If the directory /usr/local/lib/pi-devbox/ exists (or your shell prompt is
prefixed [devbox], or ~/.ssh-local/config is present), you are in a
pi-devbox container — a Docker environment whose persistence, networking,
DNS, host/LAN reachability, tmux, and Python/REPL behaviour differ from a normal
workstation. Before any task that touches reaching the host or its LAN, SSH,
DNS/name resolution, what survives container recreate, running Python/REPLs,
tmux, or pi-studio, read ~/.agents/skills/pi-devbox-environment/SKILL.md.
Key reflex from that skill: the deployment specifics are not universal — the
host OS, hostnames, internal domains, and nameservers vary per instance and must
be discovered at runtime, never assumed. And interactive shell aliases
(dssh, dscp, cat→bat) do not exist in your non-interactive bash
tool, so spell out the underlying command (e.g.
ssh -F "$HOME/.ssh-local/config" mac …).
Browser automation is available (agent-browser)
This image bakes the agent-browser CLI plus a headless Chromium, so you can
drive a real browser — open pages, click/fill/eval, snapshot the DOM, take
screenshots — to verify front-end work (live DOM, WebGL, layout, popup
positioning) instead of guessing. Reach for it whenever a task involves a web UI
or checking how a page actually renders. AGENT_BROWSER_EXECUTABLE_PATH is
preset to the baked browser, so agent-browser open <url> works out of the box
(headless). Run agent-browser skills get core --full for the command set and
workflow patterns (always version-matched to the CLI); the agent-browser skill
under ~/.agents/skills/ mirrors it when the skillset is mounted.
Session start: load the mempalace skill
If MemPalace MCP tools (e.g. mempalace_search, mempalace_diary_write) are in
your tool list, read ~/.agents/skills/mempalace/SKILL.md before doing
non-trivial work and follow its protocol: search the palace before answering
about past work, and write a diary entry before the session ends. This is
especially load-bearing here — a pi-devbox container is frequently recreated, so
the palace is your only memory across recreates. Without the habit it is just
storage, not memory. (The skill is the consumer side; feeding the palace is the
separate opencode-mempalace-bridge skill, if present.)