Skip to content

fix(reload): restart from error page (382) - #410

Merged
Rchari1 merged 1 commit into
mainfrom
fix/382-restart-button
Aug 17, 2026
Merged

fix(reload): restart from error page (382)#410
Rchari1 merged 1 commit into
mainfrom
fix/382-restart-button

Conversation

@Rchari1

@Rchari1 Rchari1 commented Aug 17, 2026

Copy link
Copy Markdown
Member

Fixes #382 — Restart button on 'Something went wrong' was non-functional inside the Amicode panel.

Root cause

  • packages/app/src/entry.tsx platform.restart only did window.location.reload(). Inside the deck iframe the server may be down/unreachable, so a reload alone kept the panel in the error state.

Fix

  • Upstream fix: google token auth like Claude + revert dock blank + restart opencode#210: entry.tsx restart now posts {source:"amicode", kind:"command", command:"amicode.restartServer"} to the extension host before reloading (800 ms grace), so the server restarts and the panel recovers. error.tsx wraps restart in try/catch with fallback reload.

  • This repo (amicode#382): documents the trace in extension.ts — the amicode.restartServer command is already allowlisted in chat_bridge.ts, so the iframe's post now reaches the host.

Verification

  • Trigger an error (e.g. kill opencode), click Restart in the error page → panel shows restart log and recovers, not stuck.

Fixes #382
Upstream harmoniqs/opencode#210

The 'Something went wrong' Restart button was a no-op in the Amicode
iframe because platform.restart only did window.location.reload without
restarting the underlying opencode server. Upstream harmoniqs/opencode#210
fixes the app's restart to post amicode.restartServer to the extension
host before reloading, so the server restarts and the panel recovers. The
extension's allowlist already permits that command (chat_bridge), and this
documents the trace so a future regression is diagnosable.

Fixes #382
Upstream: harmoniqs/opencode#210
@coderabbitai

coderabbitai Bot commented Aug 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 57 minutes

Limit details: You’ve used all 3 included reviews currently available under your plan.

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

Review profile: CHILL

Plan: Pro Plus

Run ID: ecf09a57-9065-40b5-96ec-da139b77bb28

📥 Commits

Reviewing files that changed from the base of the PR and between 1f0b0fc and 1c9b6f5.

📒 Files selected for processing (1)
  • packages/extension/src/extension.ts

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

@Rchari1
Rchari1 merged commit b712baa into main Aug 17, 2026
7 checks passed
@Rchari1
Rchari1 deleted the fix/382-restart-button branch August 17, 2026 20:09
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: Restart button on 'Something went wrong' error page is non-functional

1 participant