[jdx]

https://entire.io/gh/jdx/mise/trails/790

Pressing Ctrl+C twice in mise watch no longer ends with an error banner. With watchexec 2.8.0 the second Ctrl+C makes watchexec exit with status 130 (128 + SIGINT), and mise reported that as a failure:

^Cmise ERROR command ["watchexec", "--clear", "--restart", "--", ".../mise", "run", "..."] exited with code 130
mise ERROR Version: 2026.10.11 linux-x64 (2026-10-15)
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

Now mise watch treats watchexec ending with exit status 130, or being killed by SIGINT, as the user interrupting it: it prints nothing and exits with 130. Any other non-zero status from watchexec is still an error, and a SIGTERM is not mistaken for Ctrl+C.

Reported in discussion #8269.

Validation

• Added a unit test for the exit-status classification (130, SIGINT, success, generic failure, SIGTERM).
• cargo clippy --workspace --all-targets -- -D warnings is clean.
• No e2e test: reproducing it needs a pty and a watchexec that exits 130.

🤖 Generated with Claude Code

AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: claude-code_2-1-299_agent.

---

Note

Low Risk
Narrow change to mise watch exit-status handling and UX; no auth, data, or security-sensitive paths.

Overview
mise watch no longer prints an error when watchexec stops because the user hit Ctrl+C (including watchexec 2.8’s exit code 130 after a second interrupt).

Watchexec is run with unchecked() so mise can read the exit status. A new interrupted_exit_code helper treats exit 130 and Unix SIGINT as a user interrupt and exits via request_exit(130) without the failure banner; other non-zero exits still fail with bail!, and SIGTERM is not treated as Ctrl+C. A Unix unit test covers the status classification.

^{Reviewed by Cursor Bugbot for commit 169aa27. Bugbot is set up for automated code reviews on this repo. Configure here.}

[coderabbitai]

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 3 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 10 included reviews currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

• Configuration used: Repository YAML (base), Central YAML (inherited), Organization UI (inherited)
• Review profile: CHILL
• Plan: Advanced
• Run ID: 2c3fbe3d-a761-4c7d-9f9d-1da17f5cb052

📥 Commits

Reviewing files that changed from the base of the PR and between c585c7a and 169aa27.

📒 Files selected for processing: 1

• src/cli/watch.rs

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[greptile-apps]

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Summary

mise watch now exits quietly with status 130 when watchexec exits with 130 or dies from SIGINT.

• Pressing Ctrl+C stops mise watch without an error banner.

_{Reviews (1) · Last reviewed commit: "fix(watch): exit quietly when watchexec ..." · Reviewed by Greptile}

[github-actions]

Instruction counts

benchmark	trend	instructions	Δ	wall (min)	Δ
env	▁▄▃▇▅█▅▄▆▆▄	28,023,431 → 28,002,723	-0.07%	20.09 → 19.87ms	-1.07%
hook-env	▂█▁▆▂▅▇▂▄▅▅	30,279,961 → 30,276,472	-0.01%	20.54 → 20.78ms	+1.17%
ls	▁▇▄▅▆▅▆█▇▄▆	32,200,440 → 32,219,586	+0.06%	21.83 → 22.04ms	+0.95%
registry	▄▁▄▆█▇▆▄▇█▂	40,366,185 → 40,306,775	-0.15%	18.40 → 17.84ms	-3.03%
startup	▇█▁▃▂▃▂▂▂▂▂	11,080,275 → 11,076,806	-0.03%	12.04 → 12.01ms	-0.28%

No instruction-count regression above 1%.

_{Only instruction counts gate. Wall clock is shown for context — on identical hardware it moves 4-20% run to run.}

_{Measured by tak — instruction-counted CLI benchmarks, stored in this repository's git notes.}

_{169aa27de154 vs c585c7a6c1fd · measured on the runner, not pushed to the history.}