Repository navigation
vibe 0.1.201
Assist the user when docker sbx auth token expires: detect need to login & guide the user there (#18)
When sbx is signed out of Docker, vibe now says so and offers to fix it, instead of waiting out a 3-minute start and reporting "didn't start within 3m0s" (and vibe -l printing sbx's raw error).
Changes
- Waking a sandbox reads sbx's output as it comes. With no terminal,
sbx execfails at once pointing tosbx login; on a terminal it starts a device-login flow and waits. Both are recognised (by thesbx logincommand it names and the docker.comuser_codeaddress, not by sbx's wording) and reported at once. - Page: a start that can't happen says sbx is signed out and points to the Admin tab. A failed prompt, and the page being brought back into view, show the Conversation banner, whose button opens the Sign-in card. Any other failure to start shows sbx's own (shortened) words and where the log is.
vibe --list/--infooffersbx loginon the terminal when sbx is signed out, and run again once it is signed in.- Waiting loops (session start, memory restore) give up at once when signed out. Failed wakes are noted in
~/.vibe/sbx-wake.log(the first and last of a run). - Last resort: a failure nothing recognises asks
sbx login(at most once in two minutes). Its message says it was used and asks for a report of what sbx said. The agent can cause it to run; that is documented.
Security
What a wake prints is the output of a command run in the sandbox, which the agent controls. So it is never shown as a sign-in link (a sandbox could start its own Docker device login), is read a line at a time and capped at 64 KB, and is shown short and without control characters.
Also fixed
sbxrun.Process: a process stopped while printing without end was never reaped, because its output pipe blocked. Output is now drained once nobody wants it.
Verified
go test ./...passes; each new test was seen to fail first.- By hand on a real sbx:
vibe -loffered the login and completed it; a prompt while signed out gave the error and the banner; the Admin card signed in; the wake log shows the new wording. - Two reviews on the Review tab, with their findings fixed.
Not verified
- The new tests on macOS and Windows CI (the stand-in scripts need
yes,headandtr; they skip on Windows). - The last-resort path against a real unrecognised failure.
- The banner on bringing the page back into view, on a real sbx (page tests pin it).
Host-side only: no sandbox rebuild (vibe -C) is needed.
To install:
- Linux/macOS:
curl -fsSL https://raw.githubusercontent.com/fluffynuts/vibe/master/install.sh | sh - Windows:
irm https://raw.githubusercontent.com/fluffynuts/vibe/master/install.ps1 | iex - Manual: download the zip for your platform (below), unzip it anywhere, and run
vibe --installfrom the folder it makes.
To upgrade, run the same command again, or vibe --upgrade once vibe is installed.
| Platform | Zip |
|---|---|
| Linux (x86-64) | vibe-linux-amd64.zip |
| Linux (ARM) | vibe-linux-arm64.zip |
| macOS (Apple Silicon) | vibe-macos-arm64.zip |
| macOS (Intel) | vibe-macos-amd64.zip |
| Windows (x86-64) | vibe-windows-amd64.zip |
| Windows (ARM) | vibe-windows-arm64.zip |
SHA256SUMS holds each zip's checksum. The install scripts and vibe --upgrade check it.
macOS: the binary isn't signed, so if it's blocked after downloading in a browser, run
xattr -dr com.apple.quarantine <folder> once.
What's Changed
- Assist the user when docker sbx auth token expires: detect need to login & guide the user there by @fluffynuts in #18
Full Changelog: v0.1.198...v0.1.201