Repository navigation
fix(cli): identify Cloudflare challenges instead of suggesting login #105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
chuyeowego
wants to merge
2
commits into
main
Choose a base branch
from
devin/1792463743-edge-challenge-diagnostics
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+170
−1
Draft
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🟡 Bundled skill misclassifies challenged 403 responses
A challenged 403 now exits 6, but the agent exit-code table assigns every code-less 403 to exit 3. The shipped agent guidance remains wrong for the response this change targets.
Learn more
The embedded skill is the published operating contract for agents. Its exit-code table tells agents that any 403 without an API code exits 3 and prescribes login, whereas marked 403 challenges are now deliberately emitted as exit 6.
Example: A hotel-search challenge has status 403 and no problem code. The CLI exits 6, while the bundled table predicts exit 3 and says to log in.
Recommended fix: Update the embedded skill's exit-code table to distinguish a
cf-mitigated: challengeresponse from an ordinary 403. Keep the table consistent with the actual CLI taxonomy and the repository's rules governing changes toskills/.Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed. The bundled exit-code table still classifies every code-less 401/403 as auth, every 404 as not-found and every 429/503 as retryable. A response explicitly marked
cf-mitigated: challengeis now an exception: exit 6, preservecf_ray, report the challenge, and do not log in again, refresh, re-search or automatically retry.I left this finding open because AGENTS.md explicitly prohibits editing
skills/. The repository owner needs to update the bundled guidance or explicitly authorize that narrow edit. The mismatch is also called out in the PR's Notes for reviewers.The transport findings are fixed in the follow-up commit, with compiled-binary regressions covering the challenge marker before auth, not-found and retry shortcuts.