Auto-update from v0.76.2 -> v0.77.0 leaves broken install (ModuleNotFoundError: keboola_agent_cli)

[MichalProchazka]

While running kbagent (v0.76.2), the CLI's built-in auto-update check kicked in and attempted to upgrade to v0.77.0. The update failed with:

Updating kbagent v0.76.2 -> v0.77.0...
Auto-update failed; continuing with current version. Recover with: uv tool install --force --reinstall "keboola-cli @ https://github.com/keboola/cli/releases/download/v0.77.0/keboola_cli-0.77.0-py3-none-any.whl"
Error in sys.excepthook:
Traceback (most recent call last):
  File "typer/main.py", line 82, in except_hook
ImportError: cannot import name 'rich_utils' from 'typer'

Despite the message saying it would "continue with current version," the local install was left in a broken, inconsistent state -- every subsequent command (kbagent flow --help, kbagent job --help, etc.) failed immediately with:

ModuleNotFoundError: No module named 'keboola_agent_cli'

so the tool was completely unusable until manually repaired.

Environment: Windows 11, installed via uv tool install.

Workaround: running the exact recovery command printed in the failed-update message fixed it:

uv tool install --force --reinstall "keboola-cli @ https://github.com/keboola/cli/releases/download/v0.77.0/keboola_cli-0.77.0-py3-none-any.whl"

After that, kbagent --version correctly reports v0.77.0 and kbagent doctor passes.

Suggested fix: if auto-update fails partway (e.g. dependency conflict, partial package removal), the CLI should roll back to the previously-working install rather than leaving a half-updated environment that can't even print --help.

[padak]

Thank you for the report — and specifically for including the full traceback. This is
the same failure as #528, and your details added evidence we did not have.

Root cause. uv tool install recreates a tool environment by removing it in place
and then building a fresh venv at the same path
(uv-tool/src/lib.rs:
create_environment → "Remove any existing environment" → create_venv). That is not
atomic and has no rollback.

On POSIX it is harmless: unlinking a file another process holds open leaves that
process's inode intact. On Windows uv's kbagent.exe trampoline loads the venv's
interpreter in-process, so those files are locked — the removal deletes everything it
can, hits a locked file, and aborts. Your environment was not half-upgraded; it was
half-deleted. Upstream tracks the same class of failure as
astral-sh/uv#11930.

Your ModuleNotFoundError: No module named 'keboola_agent_cli' is the sharpest evidence
we have of this. In #528 the damage was individual files missing inside packages that
still existed (rich/_windows.py, typer/rich_utils.py); in your case the removal got
far enough to take kbagent's own package out of site-packages. That is exactly what the
remove-then-recreate sequence predicts, and it is not what a "dependency conflict" or a
partial upgrade would produce.

It also matters that you hit this on the v0.76.2 → v0.77.0 update. v0.76.2 shipped a
fix for this issue that reordered the update but still ran the installer from inside the
environment being replaced. Your report is an independent confirmation that the reorder
was not enough — thank you, that was genuinely useful.

Fix: #543. On Windows kbagent no longer installs into its own live environment at
all — the reinstall is handed to a detached helper that waits until every kbagent process
has exited. If kbagent never exits it installs nothing and says so, rather than risking a
partial install. It also stops killing a slow installer on timeout, which was a second way
we produced the same damage ourselves.

On your suggestion of rolling back to the previous install: we went further and avoid
mutating the live environment in the first place, so there is nothing to roll back. A
rollback would need a copy of the environment made before the removal, which uv does not
give us a hook for.

Closing as a duplicate of #528 — please follow that issue for the release. Your recovery
command is the right one in the meantime, and it stays the documented recovery path.

[padak]

Follow-up, because the answer you got from me here was incomplete.

Your report was closed as a duplicate of #528, and the corruption you hit is indeed fixed. But the deferred self-update that replaced it never actually applied on Windows — from 0.78.0 all the way to 0.80.1 it announced an update and then silently did nothing. So if you have been running kbagent on Windows since, you are very likely still on the version you recovered to by hand, and kbagent update will not have moved you.

Fixed in v0.80.2 (#571 / #572): the helper was spawned without a console, which powershell.exe cannot start without, so it exited 0 having run nothing. Verified 3/3 against 0/3 for the old flag on a real Windows 11 machine.

One reinstall unsticks it, after which auto-update works normally:

uv tool install --force --reinstall "keboola-cli @ https://github.com/keboola/cli/releases/download/v0.80.2/keboola_cli-0.80.2-py3-none-any.whl"

Your ModuleNotFoundError: No module named 'keboola_agent_cli' traceback is still the sharpest single piece of evidence anyone sent for the original corruption, and it is what made the remove-then-recreate diagnosis provable rather than plausible. Thank you for that — and apologies that the fix which followed took two more releases to actually reach you.