correct 403 response processing#74
Merged
Merged
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
zizhengtai
reviewed
Mar 3, 2026
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
zizhengtai
approved these changes
Mar 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
Medium Risk
Moderate risk: changes error handling for the cloud session creation path and adds dynamic attributes on raised exceptions, which may affect downstream callers’ error parsing/behavior.
Overview
Improves handling of
403 Forbiddenresponses when creating a cloud browser session by parsing the response body (via newApiErrorPayload) and raising aRuntimeErrorthat includes attachedstatus_codeand parseddetailfor programmatic consumption.Non-403 failures keep the existing behavior (raising a generic
RuntimeErrorwith status/text), but the client now attempts to interpret JSON error payloads more robustly.Written by Cursor Bugbot for commit 87db542. This will update automatically on new commits. Configure here.