From 88e633c6c48bd6d62d56a25555aa0fb4acda8833 Mon Sep 17 00:00:00 2001 From: Thales Maciel Date: Sun, 29 Mar 2026 17:52:42 -0300 Subject: [PATCH] Document vm run tooling bootstrap and attach fallback 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. --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 9868e27..c7e0809 100644 --- a/README.md +++ b/README.md @@ -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 ``` -`vm run` resolves the enclosing git repository, creates a VM, copies a git checkout plus current tracked and untracked non-ignored files into `/root/`, 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/`, 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