Release notes

Unleash MCP server is now generally available

The Unleash MCP server is now generally available. It gives your AI coding assistants a structured contract for managing feature flags safely, guiding them through evaluating risk, creating flags, wrapping code, and cleaning up after a rollout. It works with tools like Claude Code, Cursor, GitHub Copilot, Kiro, and OpenCode.

New tools to list flags and projects

Two new tools let assistants discover and audit your feature flags directly:

• list_projects lists all Unleash projects available to your token.
• list_flags lists the feature flags in a project, with support for filtering, ordering, and pagination.

These tools power agentic flag-audit workflows and back the detect_flag inventory analysis, so assistants can enumerate flags before creating new ones or identify cleanup candidates. For details, see the tool reference.

Remote MCP server in beta

You can now connect MCP clients to a remote MCP server hosted by your Unleash instance, without installing anything locally. This is useful when developers cannot run MCP servers on their machines, or when you want to manage MCP access centrally. The remote MCP server is in beta. See Enable the remote MCP server for setup steps.

Project-level context fields

Context fields can now be defined at a per-project level. To create one, open a project and go to Settings > Context fields. Once you define project-level context fields, they are available in strategy configuration and the playground for users with access to that project, but are not included in the global context fields overview.

Edit strategies in applied release plans

You can now edit activation strategies in a release plan after the release template is applied to a feature flag. You can edit the configuration, constraints, variants, rollout percentage, or set the status to Inactive, just as you would with any standalone strategy.

User groups with root roles can now be assigned to projects

Previously, groups with a root role could not be added to projects in the Admin UI. This restriction has been removed. You can now add any group to a project regardless of whether it has a root role. This is especially useful for teams that sync groups from SSO providers, as it removes the need to maintain separate groups for root-level and project-level access.

API access URLs for Edge

You can now copy the Edge URLs directly from Admin settings > Access control > API access. For hosted customers, this works automatically. If you are self-hosting, you can configure the EDGE_URL environment variable on startup to ensure the right endpoints are visible in the UI.

Fixed scoping for private project data

We fixed how private projects scope visibility within your organization. Previously, users who weren’t added to a private project could still see some of its metadata, like segments, in global views. Affected views and endpoints now correctly return 404.

Announcement: Automated release management and Unleash MCP in beta

Two new capabilities are now available in beta.

Impact Metrics are lightweight, application-level time-series metrics you can track and visualize right inside Unleash. Counters, gauges, and histograms for things like error rates, latency, and adoption feed directly into release templates, so Unleash can automatically progress a rollout when signals are healthy or pause it when something spikes.

Impact Metrics are currently enabled for select customers. If you’d like to enable it for your organization, reach out to beta@getunleash.io.

We’ve also launched the Unleash MCP server in beta. This gives your AI coding assistants a structured contract for managing feature flags safely. It plugs into tools like Claude Code, Cursor, Windsurf, and Codex, and guides them through evaluating risk, creating flags, wrapping code, and cleaning up after rollout.

Enterprise Edge observability

We extended the observability dashboard for Unleash Enterprise Edge. The dashboard provides visibility into the health and performance of your hosted or self-hosted Enterprise Edge nodes directly within the Unleash Admin UI.

Key metrics include:

• Instance details: Region, instance ID, upstream server, and hosting type.
• Health resources: Current connection status, running version, and real-time CPU and memory usage.
• Traffic and performance: Active streaming clients and granular latency breakdowns for upstream syncs (features, metrics) and downstream evaluations.

Announcement: Unleash Edge OSS enters long-term maintenance

We are sunsetting the Open Source Software (OSS) version of Unleash Edge to focus on Enterprise Edge capabilities. The lifecycle for the OSS version is as follows:

• Long-term support: starts December 12, 2025
• End-of-life: December 31, 2026

We recommend that all OSS users of Edge migrate to Enterprise Edge to ensure continued support and access to security updates.

Global change request overview

We added a global overview for change requests. The table allows you to view all your open and closed change requests in a single location. You can filter the table to show:

• Created by me: Change requests created by you.
• Approval requested: Change requests requesting your approval.

Improved experience for adding strategies to flags

We redesigned how you add activation strategies to flags. The new flow makes it easier to access standard strategies and reusable release templates. When you configure a flag in an environment, click Add strategy and choose one of the following options:

• The project’s default strategy
• A standard strategy, such as gradual rollout or on/off
• An advanced strategy, such as IP or host targeting
• A release template
• A custom activation strategy defined in your instance

You’ll also see a suggested strategy in any environment without an active configuration, so you can preview, edit, or apply your default strategy in a single click.

New lifecycle analytics

We’ve added two new widgets to the Analytics dashboard: New flags in production and Flags archived vs flags created.

New flags in production shows how many flags reached production each week for your selected time period. It gives you a quick view of your team’s delivery pace and how feature output changes over time.

Flags archived vs. created tracks how many flags you archive each week compared to how many you create, alongside your average cleanup ratio. If you consistently create more flags than you archive, that’s a sign that technical debt may be increasing. Over time, aim for a 1:1 ratio (or 100%) of archived to created flags to keep your codebase healthy.

Aligned quick filters in Project Overview

We aligned quick filters in Project Overview to provide a more consistent experience with feature flags lists. You can now use the same filters available on Flags Overview to narrow down flags by lifecycle stage, such as Develop, Production, or Clean-up.

Release Management

We’ve launched Release Management to help you standardize how you roll out new features. You can now define reusable release templates with milestones so you don’t have to manually configure the same rollout strategies across multiple flags. This reduces repetitive work, ensures consistent rollouts, and lowers release risk. Create new templates under Configure > Release templates.

Change request improvements

You now receive an email notification when you’re added as a reviewer to a change request. This helps you maintain momentum by speeding up the approval process.

Change requests also display a cleaner, formatted JSON diff that highlights only the changed values while still letting you expand for the full object. In the new View diff tab, you can review the changes in detail, and easily copy them without relying on tooltips.

In addition, to give you a clear timeline of progress, every state update to a change request now includes a timestamp.

Flag performance and lifecycle updates

We’ve added lifecycle metrics to the Analytics dashboard so you can see a snapshot of how many flags are currently in each major lifecycle stage: Develop, Production, and Cleanup. Each stage shows how many flags are new this week, how many have been there for more than a week, and the median time flags spend in that stage. You can also compare this to the historical median to spot outliers.

This gives you a clear picture of where flags may be stuck, helps you reduce technical debt, and connects engineering work to business outcomes.

To help reduce technical debt, Unleash now also suggests flags that are safe to archive. By analyzing usage, the platform highlights flags in the cleanup stage that haven’t been used for seven days so you can confidently archive them in bulk.

Project list improvements

The Project list view has been redesigned to make it easier to scan, even with a large number of projects. You can now switch between card and list views depending on which format you prefer, making navigation more flexible.

Unknown flag checker

Unleash now highlights any flags your SDKs try to evaluate that Unleash doesn’t recognize. You’ll see these in the Flags overview under Unknown flags, where you can review the full list to spot typos, fix misconfigurations, or remove stale references in your code. This helps keep your setup clean and in sync.

Feature flag lifecycle improvements

You can now mark any flag as Ready for cleanup, even if it never reached production. This helps you clean up flags at any stage in the lifecycle, for example, a kill switch you never enabled in production, and reduce technical debt.

We also renamed Health to Technical debt to align with common engineering terminology. In Project > Project status, you can see a technical debt rating for the project. In Analytics > Technical debt, you can explore the same data at the instance and project levels.

Renamed SDKs and token types

We’ve introduced a more consistent naming pattern for our SDKs and API tokens. Server-side SDKs are now backend SDKs, and client-side SDKs are frontend SDKs. Backend SDKs use backend tokens and frontend SDKs use frontend tokens.

You’ll find the new naming across our documentation and in the Admin UI, such as when creating API tokens or working with permissions. We also standardized SDK repository and registration names to follow the unleash-{language/framework}-sdk pattern. For example, unleash-client-python has been renamed to unleash-python-sdk. Note that SDK artifact names remain unchanged to avoid requiring changes to your codebase.

Grouped events in Event Log

Event Log now marks related events using a Group ID when a single action produces multiple changes. This makes the full sequence of changes easier to trace and audit.

For example, when a change request is approved and applied, all resulting events, such as strategy or flag config changes, appear under the same Group ID. Similarly, if enabling a flag in an environment automatically adds the default strategy, both events share the same Group ID to reflect that they came from the same action.

In addition, we’ve made the date filter optional and added filtering by ID on the Events API.

View connected frontend applications

To help debug frontend application connections, you can now view connected frontend applications inside Configure > Applications and in each project’s Applications tab. If an application uses both backend and frontend SDKs, both are shown on the application’s overview page.

Flag cleanup reminders and automation

To help you stay on top of technical debt, we’ve introduced automated reminders for flag cleanup.

When a feature flag reaches its intended cleanup date and we no longer detect metrics, we’ll remind you to change its lifecycle status to Cleanup. This highlights the flag in the UI, making it clear which flags are ready to be removed.

On the flag’s page, you will see a reminder to remove the flag from your codebase and archive it in Unleash.

External links on feature flags

You can now add external links to your feature flags, allowing you to connect directly to related resources like key metrics, analytics, or issue trackers. Add a link on the Overview page of any feature flag.

In addition, you can define link templates at the project level in Settings > Project settings > Enterprise settings > Project link templates.

These templates automatically populate links for all new feature flags within that project. For example, you can create templates to find all usages of a feature flag in your repository or automatically link to a Jira issue when a flag is created from Jira

Colors on tags

To help you visually differentiate and organize your feature flags, you can now add colors to tags. When you create or edit a tag in Configure > Tag types, you can assign a specific color. This makes it easier to quickly identify and manage flags, especially in projects with many tags.

Improved flag search and Admin UI menu

We’ve renamed Search to Flags overview, to create a centralized place to monitor the status and lifecycle of all your feature flags and releases. This is particularly useful for coordinating flags across multiple teams.

With Flags overview, you can get a clear picture of where each flag is in its lifecycle and its current status—replacing the need for manual tracking or spreadsheets.

We’ve also redesigned the Configure menu and removed redundant items such as Recent projects and Recent flags, which are now accessible from the main Dashboard.

Simplified activation strategies and constraints

We simplified the process of adding or editing activation strategies and constraints. Use Add strategy to add the default activation strategy to a flag; use More strategies to select a different strategy type or get an overview of all available release templates.

Removed deprecated endpoints and schema properties

As part of our commitment to maintaining a clean and robust codebase, several deprecated API endpoints and schema properties have been removed in Unleash v7. Refer to our Migration guide for a detailed list of API changes and additional help with upgrading to Unleash 7.

Improved user roles and permissions overview

We’ve added a new Access overview page for each user, making it easier for administrators to see exactly what a user can do in Unleash and which roles grant those permissions. You can explore permissions at the root level or for specific environments and projects. To view a user’s permissions, go to Admin settings > Users. Select a user and click Access overview.

IP addresses in Event Log

The Event Log now records the IP address of the user who performed each action. This feature requires an Unleash Enterprise plan.

Projects no longer require an Owner

We removed the requirement for projects to have an Owner. This gives you full flexibility when it comes to customizing the project-level roles. Projects without an Owner are shown as owned by System.

New root-level permissions for authentication and instance maintenance

We’ve introduced five new root-level permissions to give more granular control over features that were previously restricted to the Admin role. These permissions cover authentication settings such as single sign-on, instance maintenance tasks like updating banners and toggling maintenance mode, managing CORS settings, and viewing access logs and login history.

Observability metrics for Edge

We’ve introduced a new dashboard that provides detailed observability metrics for Unleash Edge, helping teams efficiently manage all their connected Edge instances. The dashboard offers a high-level view of all Edge instances, with deeper insights into instance ID, region, CPU and memory usage, and upstream/downstream latency. This data helps you ensure that all instances are operational and quickly identify potential issues. You can access these metrics in Network > Connected Edges for Edge instances on version 19.7.0 or later.

Data usage date range selector

The Data Usage dashboard now provides an aggregated view of your requests to Unleash over the last 3, 6, or 12 months—making it simple to track and assess your data usage over time. You can also compare your usage in previous months with the current month. Access the dashboard in Network > Data Usage.

Event Timeline now lives in Dashboard

We have moved Event Timeline to the top of Dashboard for a more seamless experience and easier access.