thaloco/banger
1
Fork 0
Code Pull requests Releases Packages Activity Actions

Document vm run tooling bootstrap and attach fallback

Browse source 
Bring the vm run documentation back in line with the current behavior.

Explain that vm run now starts a best effort guest tooling harness,
prefers a host side opencode attach session when the local client
supports it, and falls back to guest opencode over SSH otherwise.
Also note that the harness runs asynchronously and logs inside the guest.
This commit is contained in:
Thales Maciel 2026-03-29 17:52:42 -03:00
parent 4813e844e2
commit 88e633c6c4
No known key found for this signature in database
GPG key ID: 33112E6833C34679
1 changed files with 1 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -120,7 +120,7 @@ Start a repo-backed VM session and attach `opencode` automatically:
./build/bin/banger vm run ../some-repo --branch feature/alpine --from HEAD ./build/bin/banger vm run ../some-repo --branch feature/alpine --from HEAD
``` ```
`vm run` resolves the enclosing git repository, creates a VM, copies a git checkout plus current tracked and untracked non-ignored files into `/root/<repo-name>`, and then runs `opencode attach` from the host against the guest. `vm run` resolves the enclosing git repository, creates a VM, copies a git checkout plus current tracked and untracked non-ignored files into `/root/<repo-name>`, starts a best-effort guest tooling harness that inspects the repo and installs clearly-needed tools with `mise`, and then prefers a host-side `opencode attach` session when the local client supports it. Older host opencode clients fall back to starting `opencode` inside the guest over SSH. The harness runs asynchronously and logs its output inside the guest.
## Web UI ## Web UI