// AI Platform Drift
Cloudflare Flagship adds structured evaluation context with nested objects and arrays
Cloudflare developer changelog · published 2026-10-23 17:11 UTC
WHAT CHANGEDCloudflare Flagship now accepts nested objects, arrays, and null values in evaluation context as of 23 October 2026. Targeting rules support dot-separated paths (e.g., profile.plan) and has/not_has operators for array membership. OpenFeature SDKs version 0.6.0+ automatically switch to POST requests when structured context is present.
WHY IT MATTERSExisting flag evaluation code using flat context structures continues to work, but targeting rules that need to check nested attributes or array membership now have native support instead of requiring application-side flattening. SDKs below 0.6.0 cannot send structured context.
WHAT TO DOIf you use Flagship targeting rules and need to evaluate against nested user attributes or tag arrays, upgrade TypeScript, Python, or Go OpenFeature SDKs to 0.6.0 or later. Review targeting rule syntax documentation for dot-path and has/not_has operator usage.
Model-reported confidence 85% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Flagship - Target Flagship feature flags with structured evaluation context +https://developers.cloudflare.com/changelog/post/2026-10-23-structured-evaluation-context/ +Fri, 23 Oct 2026 00:00:00 GMT + +Flagship supports nested objects, arrays, and null in evaluation context. Pass user profiles and tag lists directly, then target nested attributes without flattening your application data. +For example, pass a profile and tags when evaluating a flag through the Workers binding: +const enabled = await env.FLAGS.getBooleanValue("new-checkout", false, { +targetingKey: "user-42", +profile: { plan: "enterprise" }, +tags: ["beta", "early-access"], +});const enabled = await env.FLAGS.getBooleanValue("new-checkout", false, { +targetingKey: "user-42", +profile: { plan: "enterprise" }, +tags: ["beta", "early-access"], +}); +A targeting rule can combine profile.plan equals "enterprise" with tags has "beta" to serve the feature to enterprise users in the beta group. Use dot-separated paths for nested attributes and the has and not_has operators for array membership. Percentage rollouts can also use a nested identifier, such as profile.id, for consistent user assignment. +Structured context works through the Workers binding, the evaluation REST API with a JSON POST body, and the TypeScript, Python, and Go OpenFeature SDKs from version 0.6.0. The SDKs automatically use POST when HTTP evaluation requires structured context. +Refer to targeting rules, the evaluation API, and SDK context support for usage and supported values.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.92, needed 0.5 |
|---|---|
| triage reasoning | New structured evaluation context capability changes how developers pass and target user data through Flagship feature flags. |
| signals | new feature capability added · API behavior change: structured evaluation context now supported · SDK version floor introduced: OpenFeature SDKs from 0.6.0 · HTTP method change: SDKs automatically use POST for structured context · targeting rule syntax expanded: dot-separated paths, has/not_has operators for arrays |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |