Skip to content

Teach agents to use Access service tokens - #98

Closed
scottbuscemi wants to merge 2 commits into
cloudflare:mainfrom
scottbuscemi:improve-access-service-token-guidance
Closed

scottbuscemi wants to merge 2 commits into
cloudflare:mainfrom
scottbuscemi:improve-access-service-token-guidance

Conversation

@scottbuscemi

Copy link
Copy Markdown
Contributor

Summary

  • trigger the Cloudflare One skill when non-browser clients encounter Access-protected webpages or APIs
  • document safe service-token discovery and request handling, including redirect and secret safeguards
  • route Access and service-token scenarios from the broader Cloudflare skill

Validation

  • git diff --check

@kale-stew kale-stew left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Thanks, this fills a real gap: nothing on main tells an agent what to do when it hits an Access login page. I checked it against the service tokens docs (reviewed at 230569b). The header pair, the Service Auth requirement ("otherwise, Access will prompt for an identity provider login"), and the single-header option all match. A few things before it can land:

  1. Rebase. The branch conflicts with main in README.md and skills/cloudflare/SKILL.md. skills/cloudflare-one/SKILL.md still merges cleanly.
  2. Use markdown routes for docs links in skill files (<route>/index.md, per CONTRIBUTING). README links stay on HTML routes.
  3. Keep the cloudflare skill's scope to product discovery. The new routing row is enough to send these requests to cloudflare-one. I'd drop the added sentence in the cloudflare description and the README row change for cloudflare, and keep the cloudflare-one description change, which is the right trigger.
  4. Single-header mode behaves differently, and agents will trip on it. Per the docs, failures return 401/403 instead of a 302 to the login page, Allow policies and CF_Authorization cookies are ignored, and no cookie is returned, so every request needs the header. One line would cover it.
  5. Small: CF_ACCESS_CLIENT_ID / CF_ACCESS_CLIENT_SECRET aren't documented names. "such as" makes that OK, but "the project's configured secret store or environment variables" says the same without inventing names.

@kale-stew
kale-stew requested a review from a team November 6, 2026 16:44
@kale-stew

Copy link
Copy Markdown
Member

Closing in favor of #269, which carries this forward with the original authors credited. It's rebased onto main, uses index.md docs routes, keeps the cloudflare skill's description unchanged, and adds single-header mode behavior from the service token docs.

@kale-stew kale-stew closed this Nov 6, 2026
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.

2 participants