Repository navigation
Teach agents to use Access service tokens - #269
Merged
Merged
Conversation
When a non-browser client hits a Cloudflare Access login page, check for an authorized service token and send its header pair on the original request. Cover Service Auth policies, secret handling, cross-origin redirects, and single-header mode. Route these requests from the cloudflare skill to cloudflare-one. Co-authored-by: scottbuscemi <4336848+scottbuscemi@users.noreply.github.com> Co-authored-by: Brendan Irvine-Broque <1221592+irvinebroque@users.noreply.github.com>
sandmich
approved these changes
Nov 6, 2026
acoyfellow
reviewed
Nov 6, 2026
acoyfellow
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for picking this up. It all checks out against the docs except one bullet. Details are inline.
reviewed-sha: 5230d02
Co-authored-by: Jordan Coeyman <coeyman@gmail.com>
rozenmd
approved these changes
Nov 6, 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
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.
Takes over #98. Nothing on
maintells an agent what to do when it reaches a Cloudflare Access login page. This teaches it to check for an authorized service token and send it correctly.What changed
skills/cloudflare-one/SKILL.md: an "Access-Protected Webpages and APIs" section with theCF-Access-Client-Id/CF-Access-Client-Secretheader pair. It covers:skills/cloudflare/SKILL.md: a routing row that sends these requests tocloudflare-one.README.md: thecloudflare-onerow mentions service-token access.Changes from #98
These follow the review on #98:
main.index.mdroutes (Cleanup docs links, prefer explicit markdown routes #211).cloudflareskill's description and README row unchanged; the routing row is enough to reachcloudflare-one.401or403instead of redirecting, and noCF_Authorizationcookie is returned, so every request needs the header.CF_ACCESS_CLIENT_ID/CF_ACCESS_CLIENT_SECRETnames.Validation
git diff --checkpasses.