/agentbox-setup

Box layout (what you're configuring against)

Your user i vscode and you can use sudo to run commands as root.

/workspace is where the user code lives, a per-box git worktree on a fresh agentbox/<box-name> branch (or a tar-piped copy of the host workspace for non-git projects). Run agentbox checkpoint --set-default (similar to docker commit) to save any changes make to the system and workspace so that new boxes will start from a warm state. Everything is wiped on agentbox destroy.

Some special folders:

• Host main repo's .git/ — If the box bind-mounted RW at its identical absolute host path. In-box commits land on the host's branch refs (visible to git log on the host immediately); the box itself carries no SSH/git creds, so git push goes through the host relay (agentbox-ctl git push). The host's working tree is never written to — only refs/objects under .git/. GitHub PR ops (agentbox-ctl git pr create|view|list|comment|review|merge|close|reopen|checkout) flow the same way through host gh; write ops require host confirmation (deny → exit 10), merge and checkout have additional opt-in guards.
• ~/.claude — and similar home folders for coding agents are seeded from the host's ~/.claude on each create so auth, skills, and plugins persist without leaking the host's home dir.
• agentbox.yaml — read by agentbox-ctl from /workspace. Tasks and services declared here are what the supervisor will run.

Exposed ports and services:

• portless - every port with expose: setting in agentbox.yaml, will be exposed not only as a local port but also as a special domain name https://<name>.localhost (so on https) using portless cli and proxy. This will be also mapped to the host where also portless proxy is running so users can access the same service on the same looking url.
• vnc - the webVNC server exposed on 6080 will be proxies to the host on a random port.
• vscode - the vscode server is proxied to the host on a random port.