[tracisiebel]

Summary

From Traci:
Caseware is using skills and they mentioned that

The SDK docs say skill content is delivered only through FDv2 (FDv2SkillStore), and that we'd get a 403 if FDv2 isn't enabled for our account.

I want to clarify that it is enabled for all accounts

FDv2SkillStore's 403 message (_FORBIDDEN_ADVICE) and the client README's beta caveat said FDv2 is "opt-in per account" and told users to ask support to enable it. That's no longer true. In production, fdv2-protocol-control allows /sdk/poll and /sdk/stream for every account under its "Server Side SDKs (GA)" rule. A customer recently asked us to "enable FDv2" because of this wording.

• The 403 advice now tells the user to check that the SDK key is the environment's server-side key and that no proxy in between is refusing the request, then to contact support.
• The README caveat now says that an account without Agent Skills access gets no skill content rather than an error status. This matches gonfalon: when SkillDeliveryAllowed is false, the skill payload is left out of the assignment and no error is returned. The ld-relay caveat is unchanged.
• test_a_403_stops_delivery_and_explains_why now asserts on the new wording.

This is the Python counterpart of the matching js-ai-sdk change.

How to test

uv run pytest packages/client/tests/test_skills_fdv2.py -k 403. Also ran ruff check and ruff format --check.

Link to Devin session: https://app.devin.ai/sessions/86607bf5a72840ac922a278d08236eb9
Open in Devin Desktop: https://app.devin.ai/desktop/session/86607bf5a72840ac922a278d08236eb9?variant=devin
Requested by: @tracisiebel

---

Note

Overview
Updates Agent Skills FDv2 operator-facing text so it matches current product behavior: SDK-facing /sdk/poll and /sdk/stream are not described as account opt-in anymore.

FDv2SkillStore replaces _FORBIDDEN_ADVICE for HTTP 403 fatal errors. Users are told to verify the server-side SDK key and check for a proxy blocking the request, instead of asking LaunchDarkly to enable FDv2.

The README beta caveat is aligned: every account can hit the FDv2 endpoints; lacking Agent Skills access means empty skill content, not a protocol gate. 403 is still fatal, with updated troubleshooting wording. The ld-relay limitation is unchanged.

test_a_403_stops_delivery_and_explains_why now expects "proxy" in the failure message and logs instead of "opt-in".

^{Reviewed by Cursor Bugbot for commit 24b3051. Bugbot is set up for automated code reviews on this repo. Configure here.}

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[tracisiebel]

do we want ot prompt them that if you don't have access update your sdk?

[devin-ai-integration]

I don't think this message is the right place for "update your SDK". Two reasons:

• Anyone who sees this message is already running FDv2SkillStore, so they already have an SDK that supports skills. Updating won't make a 403 go away. A 403 on these endpoints means the request itself was refused, either because of the key or because of a proxy in between.
• An account without Agent Skills access doesn't get a 403. Gonfalon (SkillDeliveryAllowed) leaves the skill payload out, so the store just comes back empty and this message never shows up.

The people who actually need "update your SDK" are those on the legacy launchdarkly-server-sdk-ai. They never run this code, so they won't see the message at all. That pointer fits better in the README or docs, for example "Skills need launchdarkly-ai-server >= 0.3.0; the legacy launchdarkly-server-sdk-ai doesn't deliver skills." Happy to add that line to the README here (and in js-ai-sdk#141) if you want it.

Written by Devin