Skip to content

fix: correct shell-exit prompt copy that falsely implies a live session - #1018

Merged
norrietaylor merged 2 commits into
mainfrom
inbox-patch/fix-shell-exit-prompt-copy-c86e7e281aa1c102
Jul 29, 2026
Merged

fix: correct shell-exit prompt copy that falsely implies a live session#1018
norrietaylor merged 2 commits into
mainfrom
inbox-patch/fix-shell-exit-prompt-copy-c86e7e281aa1c102

Conversation

@gominimal-aw-bot

@gominimal-aw-bot gominimal-aw-bot Bot commented Jul 29, 2026

Copy link
Copy Markdown
Contributor

Fixes #1015
Routing-Key: inbox-route/I_kwDOSUhdos8AAAABKkzwRQ

What

The minimald shell-exit prompt offered Detach, leaving the session running
as its first option. That prompt is shown only after the session's shell
process has already exited (the MainloopExitReason::ProcessExited branch in
session_host.rs), so nothing is left running. A user reading it could
reasonably conclude their processes are still alive and that they can reattach
to a live shell — they cannot. What actually survives is the session's on-disk
state, which is what makes the choice meaningful against the Delete option
below it.

Change

A single string literal at crates/minimald/src/session_host.rs:504:

  • before: Detach, leaving the session running
  • after: Exit, leaving the session filesystem in place and recoverable

The new copy states what is preserved (the filesystem) and what that buys the
user (recoverability), drops the false "running" claim, and parallels the
Delete option, which is already phrased in terms of files. The option
ordering and Selection::At(0)/At(1) indices are unchanged, so the
detach/delete control flow below is untouched.

The SHELL_EXIT_PROMPT constant (session_host.rs:47) is asserted against in
session.rs:1853 and session.rs:1923, but those .contains(...) checks
match the prompt header, not the option text, so the change does not break
them — confirmed both by reading the assertions and by the green test run.

The Distillery precedent pass (project minimal) surfaced only distinct prior
work (PR #431 terminal-reset-on-detach; PRs #375/#425/#462 session infra);
none bears on this user-facing copy fix.

Verification

All commands run from the workspace root against target/Cargo.toml with
--locked (CI parity). Every command exited 0.

  • cargo fmt --all --check --manifest-path target/Cargo.toml — clean, no drift.
  • cargo clippy --workspace --locked --manifest-path target/Cargo.toml -- -D warnings — exit 0, no warnings.
  • cargo build --workspace --locked --manifest-path target/Cargo.toml — exit 0 (Finished dev profile in 4m 29s).
  • cargo test --workspace --locked --manifest-path target/Cargo.toml — exit 0; all workspace tests and doctests passed (no name filter; the minimald session_host/session suites are included).

Generated by inbox-patch ·

Note

Fix shell exit dialog label that falsely implied a live session was detaching

Updates the first option in the shell exit prompt in session_host.rs from 'Detach, leaving the session running' to 'Exit, leaving the session filesystem in place and recoverable'. Selection behavior is unchanged.

Macroscope summarized f819154.

…sion

The first option on the shell-exit prompt read "Detach, leaving the
session running", but the prompt only appears after the shell process
has already exited, so nothing is left running. A user could wrongly
conclude they can reattach to a live shell.

Change the option to "Exit, leaving the session filesystem in place
and recoverable", which states what actually survives (the on-disk
session state) and parallels the "Delete" option below it.

The SHELL_EXIT_PROMPT constant asserted against in session.rs matches
only the prompt header, not the option text, so no tests are affected.
@coderabbitai

coderabbitai Bot commented Jul 29, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 35 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 830da499-e2e2-4608-ac9e-6ed83633320c

📥 Commits

Reviewing files that changed from the base of the PR and between 0f08972 and f819154.

📒 Files selected for processing (1)
  • crates/minimald/src/session_host.rs

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

@norrietaylor
norrietaylor marked this pull request as ready for review July 29, 2026 04:47
@norrietaylor
norrietaylor enabled auto-merge (squash) July 29, 2026 04:47
@norrietaylor
norrietaylor merged commit df22d71 into main Jul 29, 2026
29 checks passed
@norrietaylor
norrietaylor deleted the inbox-patch/fix-shell-exit-prompt-copy-c86e7e281aa1c102 branch July 29, 2026 05:37
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.

Shell-exit prompt copy: "Detach, leaving the session running" is misleading — nothing is running

1 participant