feat(settings): gate the Agents and Harness settings tabs behind enable-chat-v3-agents - #6089
Merged
ehayes2000 merged 1 commit intoSep 1, 2026
Conversation
Contributor
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
ehayes2000
force-pushed
the
eric.hayes/gate-agent-settings-tabs
branch
from
August 31, 2026 23:40
655fa9a to
d4f9de4
Compare
ehayes2000
force-pushed
the
eric.hayes/gate-agent-settings-tabs
branch
from
September 1, 2026 15:05
d4f9de4 to
3a8b425
Compare
ehayes2000
force-pushed
the
eric.hayes/gate-agent-settings-tabs
branch
from
September 1, 2026 15:42
3a8b425 to
512ee2f
Compare
ehayes2000
force-pushed
the
eric.hayes/gate-agent-settings-tabs
branch
2 times, most recently
from
September 1, 2026 16:16
56e1def to
c814550
Compare
…le-chat-v3-agents
ehayes2000
force-pushed
the
eric.hayes/gate-agent-settings-tabs
branch
from
September 1, 2026 16:49
c814550 to
962fd7f
Compare
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.
Stacked on #6031.
The new Agents and Harness settings tabs (and their sidebar group) were unconditionally visible —
useSettingsTabAvailablereturnedtruefor both, while sibling tabs sit behind flags (Bots→bot-management,CRM→enable-crm).This gates both tabs behind
enable-chat-v3-agents, the same PostHog flag that already gates the channel agent-mention surfaces (useChatV3AgentsFlag), resolved through the tab config's existinguseFeatureFlagpattern. The sidebar group disappears automatically when both items are hidden, anduseSettingsTabAvailableis the single gate the settings panel and app sidebar both consult, so nothing else needs touching.Known behavior while the flag is off: the macrod pairing deep link (
/app/settings/harness?pair=CODE) dead-ends — intended for a gated rollout.Note
Low Risk
Single gate change in settings tab visibility; no auth or data-path changes, only rollout alignment with an existing feature flag.
Overview
Agents and Harness settings tabs (and the sidebar Agents group when both are hidden) are no longer always shown. They now follow the same
enable-chat-v3-agentsPostHog flag—and dev override—as channel agent-mention UI, viauseFeatureFlaginuseSettingsTabAvailable.With the flag off, users won’t see agent settings they can’t use in chat; direct URLs such as
/app/settings/harness?pair=CODEwon’t surface those tabs until the flag is on.Reviewed by Cursor Bugbot for commit 962fd7f. Bugbot is set up for automated code reviews on this repo. Configure here.