control-browser
Browser Control
Stop: local_shell is not a reliable path to user-local files
local_shell runs on the user's machine only if they have the
starchild agent-shell daemon installed, running, and authorized — most users
do not, so the tool is usually unavailable or denied. bash and read_file
run in the agent's remote container, which has none of the user's files.
Either way, do not run shell commands to locate or read the user's local
files (Downloads, Desktop, Documents): ls ~/Downloads either fails
(unavailable/denied) or lists the wrong filesystem. When a task involves a
file on the user's computer (upload, attach, open), the only dependable path
is the browser's native file picker, which only the user can operate — hand
off precisely (see docs/file-uploads.md). Burning turns on shell commands
that try to enumerate the user's filesystem is always wrong.