Skip to content

fix: reset stopped runs to a pristine terminal - #93

Merged
kbuffardi merged 3 commits into
mainfrom
fix/pristine-stop-reset
Sep 15, 2026
Merged

kbuffardi merged 3 commits into
mainfrom
fix/pristine-stop-reset

Conversation

@kbuffardi

Copy link
Copy Markdown
Owner

Summary

  • Reset an active run to a pristine terminal prompt on STOP or Ctrl+C, clearing terminal output and input state rather than printing an interruption transcript.
  • Ignore stdout and run-result messages that arrive after a stopped run, and terminate the compiler worker synchronously during tab unload.
  • Bump the extension version to 0.4.9.

Verification

  • npm run test:e2e
  • npm run lint
  • npm run build
  • npm run test:browser:chrome
  • npm run version:check

Review

Reviewed for correctness, readability, architecture, security, and performance. The change is limited to terminal run teardown, defensive unload cleanup, regression coverage, and synchronized release metadata.

Closes #92

@kbuffardi
kbuffardi merged commit d797149 into main Sep 15, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: browser crash after an infinite loop stop

1 participant