Skip to content

fix: improve terminal-session errors and host task visibility - #41

Merged
EitanWong merged 1 commit into
mainfrom
fix/41-more-novice-scenarios
Aug 4, 2026
Merged

fix: improve terminal-session errors and host task visibility#41
EitanWong merged 1 commit into
mainfrom
fix/41-more-novice-scenarios

Conversation

@EitanWong

Copy link
Copy Markdown
Owner

Round 3 of novice simulation:\n\n1. joining a closed session now gives plain guidance instead of 'session is terminal'\n2. the host connector window now prints one line per task (completed / failed: reason) so non-technical users see work happening and rejections\n3. ux-smoke extended to 17 checks covering both host-window lines and the closed-session path\n\nLocal: 17/17, check.sh green.

…st window

More novice-path simulation:

- joining a closed session said 'session is terminal'; gateway now maps the
  terminal_session code to plain guidance ('This session has ended; ask the
  operator for a fresh session.')
- the host connector window was silent about tasks; it now prints one line
  per task result ('[rdev] task <id> completed' / 'failed: <reason>'), so a
  non-technical user can see work is happening and when it is rejected
- ux-smoke grew to 17 checks: task result lines in the host window
  (completed + rejected), closed-session join guidance, and a max-tasks 0
  resident host so both task assertions share one host
@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@EitanWong, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 37 minutes

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

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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 8bde2f49-4d8f-4ca5-be37-611bc531b29c

📥 Commits

Reviewing files that changed from the base of the PR and between 098e7b8 and a3a6c9e.

📒 Files selected for processing (3)
  • internal/controlplane/store.go
  • internal/hostcmd/hostcmd.go
  • scripts/ux-smoke.sh

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

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

@EitanWong
EitanWong merged commit 2254329 into main Aug 4, 2026
7 checks passed
@EitanWong
EitanWong deleted the fix/41-more-novice-scenarios branch August 4, 2026 06:30
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.

1 participant