Fix systematic exit delay after search output (interactive + non-interactive)

[shouze]

What does this PR do?

Fixes a systematic delay between the moment the final output is printed and the moment the process actually returns control to the shell — noticeable in both interactive and non-interactive (--no-interactive / CI) mode.

Root cause 1 — interactive mode (src/tui.ts)

Keyboard input is read via for await (const chunk of process.stdin). Breaking out of that loop (on Enter, q, or Ctrl+C) forces the JS engine to await the async iterator's implicit return(), which destroys the underlying Readable and waits for its 'close' event before the break actually completes. The output is already printed by then (console.log runs before the break), so the user sees the result immediately but the shell prompt only comes back once that stream teardown resolves.

Fix: call process.stdin.unref() right after setRawMode(false) in both exit paths. An unref'd handle can no longer keep the event loop alive, so the process can exit as soon as the teardown starts instead of waiting for it to fully settle.

Root cause 2 — non-interactive mode (github-code-search.ts)

The post-output "check for update" step races checkForUpdate() against a 2 s timeout via Promise.race:

await Promise.race([
  checkForUpdate(...),
  new Promise((res) => setTimeout(() => { ...; res(null); }, 2000)),
]);

The losing branch's setTimeout is never cleared. Node/Bun timers are ref'd by default, so even when checkForUpdate() wins the race in a few hundred ms, the orphaned 2 s timer keeps the process alive until it actually fires — a near-constant ~2 s delay on every CI/--no-interactive run.

Fix: .unref() the timer so it can't keep the process alive on its own, and clearTimeout it once the race settles (avoids a stray abort() firing after the flow has already moved on). The 2 s network cap behaviour is unchanged.

How did you verify your code works?

• bun run lint — zero errors
• bun run format:check — no diff
• bun test — 871 tests pass, 0 failures, no regressions
• Manual repro/verification (not unit-testable — tui.ts and the CLI entry point are side-effectful, per AGENTS.md):
  • Interactive: run a search, press Enter to confirm selection — shell prompt now returns immediately instead of after a noticeable pause.
  • Non-interactive: run with --no-interactive (or CI=true) — process now exits right after printing output instead of ~2 s later.

[github-actions]

Coverage after merging fix/tui-exit-delay into main will be

96.22%

Coverage Report

File	Stmts	Branches	Funcs	Lines	Uncovered Lines
src
aggregate.ts	100%	100%	100%	100%
api-utils.ts	93.20%	100%	93.75%	93.13%	101–103, 65, 73, 86–87, 91–92
api.ts	94.74%	100%	100%	94.07%	340–344, 405, 422, 63–69
cache.ts	94.67%	100%	100%	94.29%	139–141, 39
completions.ts	99.42%	100%	100%	99.37%	270
group.ts	99.50%	100%	97.44%	100%
output.ts	99.29%	100%	95.65%	99.61%	80
regex.ts	99.39%	100%	100%	99.34%	329
render.ts	89.82%	100%	88.24%	89.89%	172, 196–201, 203–205, 207–208, 229, 417–418, 442–444, 510–514, 526–527, 532–539, 541–549, 551–552
scroll-cooldown.ts	100%	100%	100%	100%
upgrade.ts	88.38%	100%	94.44%	87.89%	128, 131, 133, 153, 167–168, 188–195, 198–204, 209, 214, 250–253
src/render
filter-match.ts	97.44%	100%	92.31%	100%
filter.ts	100%	100%	100%	100%
highlight.ts	96.63%	100%	90.40%	99.31%	284–285
layout-constants.ts	100%	100%	100%	100%
mouse-hit.ts	100%	100%	100%	100%
mouse.ts	100%	100%	100%	100%
rows.ts	97.58%	100%	100%	97.44%	168, 54–55
selection.ts	100%	100%	100%	100%
summary.ts	100%	100%	100%	100%
team-pick.ts	100%	100%	100%	100%
terminal.ts	100%	100%	100%	100%

[Copilot]

Pull request overview

This PR removes a consistent “exit lag” after printing results by ensuring that ref’d async handles (stdin stream teardown and a timeout timer) can’t keep the event loop alive after the work is complete. It aligns with the project’s CLI/TUI architecture by keeping the fixes localized to the side-effectful entry points (tui.ts and github-code-search.ts) without altering the pure rendering/output logic.

Changes:

• Interactive mode: process.stdin.unref() is called during cleanup so breaking out of the for await (const chunk of process.stdin) loop doesn’t hold the process open while stdin teardown completes.
• Non-interactive/CI mode: the 2s update-check timeout is unref’d and explicitly cleared after Promise.race settles to prevent the losing timer from delaying process exit.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File	Description
src/tui.ts	Unrefs stdin on both cleanup paths so interactive exit doesn’t wait on stdin async iterator teardown.
github-code-search.ts	Unrefs and clears the update-check timeout so non-interactive runs don’t linger due to an orphaned timer.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.