fix(agents): add validated managed runtime recovery (#2580)

This commit is contained in:
Carlos Florêncio
2026-08-13 12:14:01 +01:00
committed by GitHub
parent 5dff29d61e
commit 45c9ba5554
72 changed files with 4258 additions and 474 deletions
+14 -7
View File
@@ -37,17 +37,24 @@ The update icon is available on managed Claude, Codex, OpenCode, Copilot, and
Gemini agent cards. It updates the runtime on the Kandev host.
1. Select the update icon.
2. Review the current version, target version, and command.
3. Select **Approve update**. If the update fails, select **Retry update**.
4. Wait for the capability refresh to finish.
2. Review the current version, active version, available stable versions, and command.
3. Keep the latest version selected for a normal update, or select an older stable version to roll back.
4. Select **Update runtime**, **Roll back runtime**, or **Repair runtime**.
5. Wait for the exact version to prepare and pass its ACP capability probe.
Kandev disables approval when the versions already match or the version check
is incomplete. A successful refresh updates the advertised models, modes,
Kandev enables the action only after the backend validates the selected version
against the trusted package catalogue. It does not accept package names, npm
tags, prereleases, registry URLs, or command text. When the active version,
observed version, and target version match, the action is disabled as **Up to
date**. A successful activation updates the advertised models, modes,
configuration options, commands, and runtime version without a page reload.
- Active sessions keep running; later probes and launches use the refreshed runtime.
- The active exact version survives Kandev and browser restarts.
- Later host-local probes, utility calls, and standalone sessions use the active exact version.
- Active sessions keep running. They are not restarted or hot-swapped.
- Passthrough agents, authentication helpers, remote executors, and running containers are unchanged.
- If the update or refresh fails, Kandev keeps the previous capability catalogue and shows the error. Authenticate the host agent, then retry.
- If preparation, ACP validation, authentication, or persistence fails, Kandev keeps the previous active version and capability catalogue. Select another stable version or retry the same target.
- Kandev may prepare the exact version again if npm removes its cache entry. Kandev does not own an offline package inventory, and global npm cache cleanup is not required.
<details>
<summary>Add a custom terminal agent</summary>