Skip to content

Surface more descriptive errors for local-to-cloud handoff failures#11012

Merged
harryalbert merged 1 commit into
masterfrom
harry/app-4496-make-error-toasts-more-descriptive-for-handoff
May 15, 2026
Merged

Surface more descriptive errors for local-to-cloud handoff failures#11012
harryalbert merged 1 commit into
masterfrom
harry/app-4496-make-error-toasts-more-descriptive-for-handoff

Conversation

@harryalbert
Copy link
Copy Markdown
Contributor

@harryalbert harryalbert commented May 15, 2026

Description

We were using one generic error toast message for a bunch of different local -> cloud handoff modes (and weren't logging descriptive warnings/errors in all cases). This made debugging harder , and also made it harder for folks to understand why local -> cloud handoff was failing in some cases.

To fix this, we should make all of the error toasts clear and descriptive, and add helpful logging for debugging in all cases.

Testing

  • I have manually tested my changes locally with ./script/run

Agent Mode

  • Warp Agent Mode - This PR was created via Warp's AI Agent Mode

@cla-bot cla-bot Bot added the cla-signed label May 15, 2026
Copy link
Copy Markdown
Contributor Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

@harryalbert harryalbert force-pushed the harry/app-4496-make-error-toasts-more-descriptive-for-handoff branch 2 times, most recently from efb917c to 671435a Compare May 15, 2026 15:21
@harryalbert harryalbert marked this pull request as ready for review May 15, 2026 15:23
@harryalbert harryalbert changed the title Surface descriptive errors for local-to-cloud handoff failures Surface more descriptive errors for local-to-cloud handoff failures May 15, 2026
@oz-for-oss
Copy link
Copy Markdown
Contributor

oz-for-oss Bot commented May 15, 2026

@harryalbert

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Copy link
Copy Markdown
Contributor

@oz-for-oss oz-for-oss Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR replaces the generic local-to-cloud handoff failure toast with branch-specific messages and adds more contextual warnings.

Concerns

  • The new cloud pane failure warning logs forked_conversation_id, which is later persisted as the server conversation token for the local fork. That token should not be written to client logs.

Security

  • Omit or redact forked_conversation_id from the new warning so conversation tokens do not end up in logs.

Verdict

Found: 0 critical, 1 important, 0 suggestions

Request changes

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

Comment thread app/src/workspace/view.rs
Comment thread app/src/workspace/view.rs Outdated
@harryalbert harryalbert force-pushed the harry/app-4496-make-error-toasts-more-descriptive-for-handoff branch from 671435a to d7b3aa3 Compare May 15, 2026 18:09
@harryalbert harryalbert enabled auto-merge (squash) May 15, 2026 18:09
@harryalbert harryalbert merged commit a992526 into master May 15, 2026
40 of 42 checks passed
@harryalbert harryalbert deleted the harry/app-4496-make-error-toasts-more-descriptive-for-handoff branch May 15, 2026 19:02
lawsmd pushed a commit to lawsmd/cortex that referenced this pull request May 22, 2026
…arpdotdev#11012)

## Description
<!-- Please remember to add your design buddy onto the PR for review, if
it contains any UI changes! -->

We were using one generic error toast message for a bunch of different
local -> cloud handoff modes (and weren't logging descriptive
warnings/errors in all cases). This made debugging harder , and also
made it harder for folks to understand why local -> cloud handoff was
failing in some cases.

To fix this, we should make all of the error toasts clear and
descriptive, and add helpful logging for debugging in all cases.

## Testing
<!--
How did you test this change? What automated tests did you add? If you
didn't add any new tests, what's your justification for not adding any?

Manual testing is required for changes that can be manually tested, and
almost all changes can be manually tested. If your change can be
manually tested, please include screenshots or a screen recording that
show it working end to end.

You can run the app locally using `./script/run` - see WARP.md for more
details on how to get set up.
-->

- [x] I have manually tested my changes locally with `./script/run`

## Agent Mode
- [x] Warp Agent Mode - This PR was created via Warp's AI Agent Mode
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants