Repository navigation
chore(features): make 13 features GA and fold 4 flags - #5883
Merged
Merged
Conversation
… libraryUsage and workbot Removes every check of auditLogs, auditLogsCompact, litellm, gatewayCloudSignIn, opencodePlugin, remoteSessionTargets, installLinks, mcpConnections, simplifiedOnboarding, connectorReadiness, driveResumableUploads, implicitCloudSkills and platformAuditReads, keeping only the on behaviour. analyticsIntegrated now follows libraryUsage; workbotCalendar, workbotSideChats and workbotDefaultModel follow workbot. Retired keys are ignored when stored or sent, and Helm still accepts them so old values files install. /v1/org keeps capabilities.installLinks, mcpConnections and auditLogs, and connectEnabled, for older clients.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub. 4 Skipped Deployments
|
benjaminshafii
temporarily deployed
to
pr-internal-specs
October 12, 2026 20:18 — with 
GitHub Actions
Inactive
GitHub Actions
Inactive
Contributor
Contributor
Warden: not approvedSecurity review found 1 high severity finding. Fix it and push; Warden reviews again automatically. If it is a false positive, a maintainer can approve by hand. Security findings (1 finding) high: Retiring the org switch bypasses explicit Connect opt-outs in `docs/marketplace-capabilities-architecture.md:202`An organization with a persisted `mcpConnections: false` override can now use `/mcp/agent` to search and execute marketplace capabilities, including retrieving capability content, if a member has the relevant resource grant. The changed code no longer applies that org-wide deny; resource grants do not replace the explicit Connect opt-out. Preserve a server-side deny for opted-out organizations on both search and execution. Clear when the persisted opt-out makes search return no marketplace matches and execution return `unknown_capability`. Reviewed |
- Provider catalog: an empty catalog read still offers LiteLLM. - Audit logs: open Technical details before reading compact policy facts. - Connector readiness: a connection is checked when saved, so start at Ready. - Library usage: integrated stat cards mark attention without icons. - Download: target the rendered search trigger (hidden duplicates are skipped since #5848).
benjaminshafii
temporarily deployed
to
pr-internal-specs
October 12, 2026 20:47 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
benjaminshafii
temporarily deployed
to
pr-internal-specs
October 12, 2026 20:50 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
benjaminshafii
temporarily deployed
to
pr-internal-specs
October 12, 2026 21:14 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
Connect stays generally available with no flag or admin switch, but a stored opt-out of the retired mcpConnections feature (organization override, deployment rollout or DEN_FEATURE_MCP_CONNECTIONS) still blocks member-facing connections, native Google Workspace and Microsoft 365 actions, marketplace capabilities and Apps, exactly as before. No new opt-out can be written.
benjaminshafii
temporarily deployed
to
pr-internal-specs
October 12, 2026 21:31 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
…ed it off" This reverts commit ec43b86.
…imit legacy Google and Microsoft setups
benjaminshafii
temporarily deployed
to
pr-internal-specs
October 12, 2026 21:40 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
benjaminshafii
had a problem deploying
to
pr-internal-specs
October 12, 2026 22:03 — with
GitHub Actions
Error
GitHub Actions
Error
benjaminshafii
temporarily deployed
to
pr-internal-specs
October 12, 2026 22:04 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
benjaminshafii
temporarily deployed
to
pr-internal-specs
October 12, 2026 22:31 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
benjaminshafii
temporarily deployed
to
pr-internal-specs
October 12, 2026 22:43 — with
GitHub Actions
Inactive
GitHub Actions
Inactive
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this about?
The weekly feature-flag review from the Oct 12 eng sync: 13 features become part of the product and lose their flags, and 4 small flags fold into the feature they belong to. 33 flags → 16.
What problem does it solve?
Too many flags, some layered three deep, made the product hard to reason about and added a feature lookup to many requests. Shipped features stayed hidden from self-hosted installs unless an operator found the right switch.
What was the situation before?
Audit logs, LiteLLM, AWS/Microsoft sign-in, the OpenCode plugin sign-in, remote session targets, install links, Connect, simplified onboarding, connector readiness, resumable Drive uploads, implicit cloud skills and platform read auditing each needed turning on in
/adminor Helm.How is this implemented?
packages/features/src/registry.ts: removedauditLogs,auditLogsCompact,litellm,gatewayCloudSignIn,opencodePlugin,remoteSessionTargets,installLinks,mcpConnections,simplifiedOnboarding,connectorReadiness,driveResumableUploads,implicitCloudSkills,platformAuditReads;analyticsIntegrated→libraryUsage;workbotCalendar/workbotSideChats/workbotDefaultModel→workbot. All 17 go toRETIRED_FEATURE_KEYS, so stored overrides and old clients are ignored.feature_disabledguards). Audit capture still needs the audit entitlement.mcpConnections: falseis ignored (documented inshared-mcp-connections.mdx)./v1/orgkeepscapabilities.installLinks/mcpConnections/auditLogsandconnectEnabled; the Helm schema still accepts retired keys; the desktop treats a 404 from an older Den's runner route quietly.openapi.jsonand the SDK (pnpm features:sync).What else changed?
docs/ai-gateway/litellm.mdxexplains the three key modes in plain words (action item from the sync).litellm-preview-flagbecameai-gateway-provider-catalog.Release note
Audit logs, LiteLLM and AWS/Microsoft sign-in for AI Gateway, OpenCode plugin sign-in, install links and the simplified Cloud onboarding are now available to every organization, including self-hosted installs. Connect is now on for every organization and can no longer be turned off.
Evidence
Changed specs under
evals/specs(audit-logs, connector-readiness, ai-gateway-cloud-sign-in, litellm-gateway-provider, ai-gateway-provider-catalog, signup-workspace-intent, workbot-calendar) — before: each feature appears only after an/admintoggle; after: it is there with no toggle.