What problem does it solve? Browser tools like marimo, httpgd, and dashboards run inside a devcontainer that publishes no ports, so their URLs are unreachable from your laptop and break on every container rebuild or server restart. ## Core Features & Use Cases - Stable port assignment: Assign each long-lived notebook its own fixed port and record the mapping in the project's AGENTS.md so bookmarks and tunnel commands survive across sessions. - Pinned authentication tokens: Store per-port marimo tokens in files under ~/.config/ so the same URL keeps working after restarts, with tokens kept outside any repository. - Verified SSH tunnel handoff: Serve with marimo on the container IP, verify the URL returns HTTP 200 with curl, then hand the user an ssh -L command and a token-authenticated localhost URL. - Use Case: A teammate starts a marimo notebook on port 2719 inside the shared devcontainer; you pin the token, verify the endpoint, and give them two lines — an SSH tunnel command and a URL — that keep working after the next rebuild. ## Quick Start Start my marimo notebook in the devcontainer on a fixed port and give me a URL I can open from my laptop that will still work after a restart.
