Changelog

1. July 29, 2026SDKs

   Evaluation inspectors across the server SDKs

   Inspectors let you watch every flag evaluation from inside your own process. Register a callback and it fires on each variation call with the flag key, the context you passed, the value the caller received, the variation key, the reason, and whichever rule or prerequisite decided it. This is the piece you need to send exposure data to an analytics tool without hand-wrapping every call site.

   • onEvaluation inspectors in the JavaScript, Node.js, Python, Go, Java, Ruby and PHP SDKs
   • Flag-change notifications in the JavaScript and Node.js SDKs (client.on('update')) and the .NET SDK (FlagsChanged), batched into one call and resolved back through prerequisites
   • A served variation key the flag does not define now reports an error reason and hands back your default, instead of a success reason that was quietly wrong
   Analytics integration guide →SDK overview →
2. July 25, 2026Integration

   Terraform provider on the Registry

   The Featureflip provider is published on the Terraform Registry at v0.1.0. Projects, environments, flags, variations, targeting rules, segments and SDK keys are all resources, so your flag configuration goes through the same version control and review that the rest of your infrastructure already does. The provider is open source in its own repository and talks to the public API, which means it runs against the free plan too.

   • Resources for projects, environments, feature flags, per-environment flag config, segments and SDK keys
   • Data sources for reading an organization, project, environment, flag or segment that Terraform does not manage
   • terraform import for flags and projects that already exist, so adoption does not start with a teardown
   • Source and issues at canopy-labs/terraform-provider-featureflip
   Terraform provider docs →Guide: feature flags as code →Terraform Registry →
3. July 14, 2026Integration

   OpenFeature providers for Node.js and .NET

   OpenFeature is the CNCF vendor-neutral API for feature flags. Two providers now sit behind it, @featureflip/openfeature-node on npm and Featureflip.OpenFeature on NuGet. Your call sites talk to the OpenFeature client instead of ours, which turns swapping vendors into a provider registration rather than a rewrite. That cuts both ways and we ship it anyway, because a team weighing a small vendor is right to want a cheap exit.

   • Boolean, string, number and object resolution through the standard OpenFeature client
   • Context mapping from OpenFeature targetingKey to the Featureflip user key, with reason and error mapping preserved
   • Tracking forwards through to the OpenFeature track() API
   • Apache 2.0, the same license as every Featureflip SDK
   OpenFeature provider docs →Guide: OpenFeature and feature flags →
4. July 10, 2026Integration

   Manage flags from Claude Code and Cursor

   The @featureflip/mcp server puts flag management inside any editor or agent that speaks the Model Context Protocol. You say what you want in English and the agent calls the Management API for you: create a flag, check where it is enabled, add a targeting rule, archive the dead ones. Most established vendors ship an MCP server now. Ours works on the free plan.

   • One npx command and a config block, authenticated with a Personal Access Token
   • Works in Claude Code, Cursor, and every other MCP client
   • Tools for creating, toggling, targeting, archiving and auditing flags, plus finding the stale ones
   • Included on the free Solo plan, not held back for paid tiers
   MCP server docs →Guide: feature flags from your AI editor →Model Context Protocol glossary entry →
5. July 9, 2026API

   Management API, on every plan

   Everything the dashboard does is available over REST at api.featureflip.io. Projects, environments, flags, variations, toggles, targeting rules, segments and SDK keys each have endpoints under /api/v1, authenticated with a bearer token. It is on every plan, the free one included, on the view that a configuration you cannot read out programmatically is a configuration you do not really own.

   • Personal Access Tokens for people, organization-scoped Service Tokens for CI
   • Idempotency-Key on creates, so a retried request cannot double-write
   • X-RateLimit headers on every response and a frozen, machine-readable error envelope
   • Cursor pagination and a generated OpenAPI reference for every endpoint
   Management API docs →Quickstart →API reference →Guide: the feature flag management API →

Per-version detail for each SDK, including patch releases, lives in that package's CHANGELOG on GitHub. Longer write-ups of the bigger releases are on the blog.