Make your computer a home for your AI partner. Avibe is the local-first Agent OS: Vibey, its built-in AI partner, works out of the box, and Claude Code, Codex & OpenCode run unchanged beside it — reach them from your browser, phone, or any chat app.
Python agentagent-osaiai-agentsai-partnerchatopsclaudeclaude-codecodexdevtoolsdiscord-botlark-botllmlocal-firstlong-term-memoryopencodeslack-botvibe-codingvibeywechat
docs(regression): keep the shared master target for merged code and respect holds before updates (#3051)
Call White9502be76a8ec
diff --git a/AGENTS.md b/AGENTS.mdindex 460fdbef4..5f664732f 100644--- a/AGENTS.md+++ b/AGENTS.md@@ -120,16 +120,19 @@ Hard rules:for remote ops- use the runner, not raw Incus commands; it owns naming, source sync, statepreparation, readiness checks, Show Runtime setup, metadata, and cleanup-- `master` is the long-running unified four-platform environment; keep it online,- preserve product state, sync source, and restart the service in place+- `master` is the long-running unified four-platform environment other Sessions+ test on: deploy only the merged default branch to it, keep it online, preserve+ product state, sync source, and restart the service in place; verify an+ unmerged branch on a `worktree` target- `worktree` targets are temporary isolated environments; delete each oneexplicitly with`python3 scripts/incus_regression.py delete --target worktree --slug <slug> --yes`when merged, abandoned, or stale-- before proposing or performing deletion of any regression environment, check- its hold with `status` or `reconcile`; if held, tell the user who holds it and- why, and do not offer a one-click delete. Long-running work must hold its- environment for as long as it runs.+- before updating, restarting, or deleting any regression environment, check its+ hold with `status` or `reconcile`, since holds do not stop `up` or `down`; if+ held, tell the user who holds it and why, and do not proceed or offer a+ one-click delete. Long-running work must hold its environment for as long as+ it runs.- `reconcile` reports every worktree environment held by Incus, includingenvironments created outside the runner, and only forgets metadata forenvironments that are no longer present. It never deletes an environment.diff --git a/docs/regression/README.md b/docs/regression/README.mdindex d9aa272f1..77ad2e4e8 100644--- a/docs/regression/README.md+++ b/docs/regression/README.md@@ -241,12 +241,14 @@ config and state to rerun the wizard while keeping CLI logins made in it. Themaster environment is always seeded.Delete worktree environments promptly after the worktree is merged, abandoned,-or removed. Before proposing or performing deletion of any regression+or removed. Before updating, restarting, or deleting any regressionenvironment, check its hold with `status` or `reconcile`; if held, tell the user-who holds it and why, and do not offer a one-click delete. Long-running work-must hold its environment for as long as it runs. The persistent `master`-environment should stay running and preserve its product state across normal-source updates.+who holds it and why, and do not proceed or offer a one-click delete.+Long-running work must hold its environment for as long as it runs, including+on `master` (`hold --target master`). The persistent `master` environment+should stay running and preserve its product state across normal source+updates. Other Sessions run long checks on it, so deploy only the merged+default branch there and verify an unmerged branch on a `worktree` target.`reconcile` answers "what is actually still here?". It enumerates worktreeenvironments from Incus rather than from the runner's metadata, so an