<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Label this issue](https://contributors.gitlab.com/manage-issue?action=label&projectId=278964&issueIid=600611) </details> <!--IssueSummary end--> ## Summary This issue tracks the removal of all Orbit-related feature flags and user-level enablement gates ahead of broader rollout. It serves as the single source of truth for which flags exist, which must be removed or enabled by default before the date: **June 10**. Two operational constraints drive urgency: - **GitLab Dedicated does not support feature flags**, so any flag still in place blocks Dedicated availability. - **Trial accounts must be explicitly blocked** before any flag is enabled globally. ## Owners - Team: AI Foundations / Orbit - Most appropriate Slack channel: `#f_orbit` - Best individual to reach out to: TBD - PM: TBD ## Stakeholders - Dedicated team (flag-free deployment constraint) - Duo platform team (trial-account gating) - Orbit feature owners per flag below ## Flag Inventory The following flags and gates are in scope for review. Each needs an explicit disposition before June 10. | Flag / Gate | Type | Purpose | Owner | Disposition | Target Date | Blocking Issue/MR | Status | |---|---|---|---|---|---|---|---| | `knowledge_graph` | Platform feature flag | Controls Orbit Knowledge Graph availability | TBD | TBD | June 10 | - | 🔲 Pending | | `orbit_foundational_agent` | Platform feature flag | Controls Orbit foundational agent availability | TBD | TBD | June 10 | - | 🔲 Pending | | `orbit_user_preference` | User-level opt-in gate | Per-user Orbit opt-in | TBD | TBD | June 10 | - | 🔲 Pending | | `orbit_agent_enabled` | Granular subsetting | Enables Orbit agent per user | TBD | TBD | June 10 | - | 🔲 Pending | | `orbit_agentic_chat_enabled` | Granular subsetting | Enables agentic chat within Orbit | TBD | TBD | June 10 | - | 🔲 Pending | | `orbit_other_foundational_agents_enabled` | Granular subsetting | Enables other foundational agents within Orbit | TBD | TBD | June 10 | - | 🔲 Pending | | `duo_developer_orbit` | Rollout gate | Changes developer flow version when Orbit user preference is active | TBD | **Verify scope** | TBD | - | 🔲 Needs review | Dispositions must be one of: - `remove before June 10` — temporary rollout scaffolding, no longer needed - `keep temporarily` — still needed for phased rollout; document why and when it will be removed - `out of scope` — not an Orbit flag; close or transfer ## Expectations ### What might happen if this goes wrong? - Flags left in place block GitLab Dedicated from accessing Orbit features. - Trial accounts could gain access to Orbit before gating is confirmed, creating a billing/entitlement risk. - Stale flags accumulate technical debt and make the codebase harder to reason about. ### Cleaning up each feature flag For each flag marked `remove before June 10`, follow the standard cleanup checklist: - [ ] Verify that external API consumers (IDE extensions, Duo CLI, CI integrations) that may query this flag have been updated or can gracefully handle its removal. See the [external API consumer guidance](https://docs.gitlab.com/development/feature_flags/#do-not-use-feature-flags-in-external-api-consumers). - [ ] Create a merge request to remove the flag: - [ ] Remove all references to the flag from the codebase. - [ ] Remove the YAML definition from the repository. - [ ] Create [a changelog entry](https://docs.gitlab.com/development/feature_flags/#changelog). - [ ] Ensure the cleanup MR is deployed to both production and canary. - [ ] `/chatops gitlab run auto_deploy status <merge-commit-of-cleanup-mr>` - [ ] Delete the flag from all environments via `#production`: `/chatops gitlab run feature delete <feature-flag-name> --dev --pre --staging --staging-ref --production` ## Operational Checks - [ ] Confirmed: GitLab Dedicated compatibility is unblocked (no flags remain that Dedicated cannot support). - [ ] Confirmed: Trial-account restrictions are in place before any flag is enabled globally. - [ ] Confirmed: `duo_developer_orbit` scope has been reviewed and a disposition assigned. - [ ] Confirmed: The "Feature flag + rollout plan defined" checkbox in the parent Orbit support issue is updated once this tracking issue is complete. ## GLQL View The query below surfaces all open issues in this project that carry the `feature flag` label and whose title contains one of the known Orbit flag names. Use it to answer "which flags are still blocking Orbit GA?" at a glance. ```glql issues( label: "feature flag", search: "knowledge_graph OR orbit_foundational_agent OR orbit_user_preference OR orbit_agent_enabled OR orbit_agentic_chat_enabled OR orbit_other_foundational_agents_enabled OR duo_developer_orbit", state: opened ) { title, assignees, milestone, state, labels } ``` Once child removal issues/MRs are created and linked here, you can also scope the query to this issue's descendants: ```glql issues( label: "feature flag", relatedTo: #<THIS_ISSUE_IID>, state: opened ) { title, assignees, milestone, state, labels } ``` ## Follow-up Issues / MRs Link each flag's removal MR here as they are created: - `knowledge_graph` removal: TBD - `orbit_foundational_agent` removal: TBD - `orbit_user_preference` removal: TBD - `orbit_agent_enabled` removal: TBD - `orbit_agentic_chat_enabled` removal: TBD - `orbit_other_foundational_agents_enabled` removal: TBD - `duo_developer_orbit` disposition: TBD