Terminal progress/cursor state not restored when aube exits on error

[SimJoSt]

When aube exits on an error while displaying its interactive progress UI, it appears to leave terminal state behind.

I noticed this with:

aubx @slkiser/opencode-quota show

which currently fails with ERR_AUBE_TRUST_DOWNGRADE.

After the command exits iTerm2 still shows an active progress indicator on the tab.

Reproduction

Run:

aubx @slkiser/opencode-quota show

and have it terminate with an error while the progress UI is active.

Observed with:

aube 2.2.17
macOS
iTerm2

In my case the error is:

ERR_AUBE_TRUST_DOWNGRADE

× dlx install failed
├─▶ failed to resolve dependencies
╰─▶ trust downgrade for effect@4.0.0-beta.83 ...

Observed behavior

After returning to the shell, iTerm2 still considers terminal progress active.

The progress state can be reset with:

printf '\e]9;4;0\a'

Expected behavior

Terminal state used by the progress renderer should always be restored when aube exits, including error paths.

This presumably needs cleanup in a finally/defer-style path so it also runs when dependency resolution fails.

[jdx]

Confirmed, and this has the same root cause as your cursor report in #1557 — one fix covers both.

The progress renderer drives the OSC 9;4 taskbar indicator as it paints and clears it during teardown, alongside restoring the cursor. That teardown was gated on a reference count that can never reach its trigger value (clx keeps a strong reference to the progress job in a process-global registry for the life of the process), so on an error path it simply never ran: no cursor restore, no indicator clear.

Reproduced here through a PTY with TERM_PROGRAM=iTerm.app, running the same aubx @slkiser/opencode-quota show. The last OSC sequence aube emits before exiting:

	last ESC ] 9 ; 4 ; … sequence
before	ESC]9;4;1;4 — normal state, 4% — indicator stays lit
after	ESC]9;4;0;0 — cleared

Fix is up in #1559, with a PTY-driven regression test asserting both the cursor restore and the indicator clear on a failing install. Your printf '\e]9;4;0\a' is the right workaround until it lands.

One gap that fix does not close: Ctrl-C during an install still leaves both behind, since nothing restores the terminal from a signal handler. Tracking that separately.

AI-assisted — Tool: Claude Code; model: anthropic/claude-opus-5; version: 2.1.270.