chore: Add toggle for context engine enable/disable#110645
Conversation
github-actions
Bot
added
the
Scope: Frontend
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
| query, | ||
| insert_index: calculatedInsertIndex, | ||
| on_page_context: screenshot, | ||
| override_ce_enable: overrideCtxEngEnable, |
There was a problem hiding this comment.
Override field always sent regardless of feature flag
Medium Severity
The override_ce_enable field is unconditionally included in every sendMessage POST request, regardless of whether the seer-explorer-context-engine-fe-override-ui-flag feature flag is active. Before this PR, the field was never sent. Now all users — even those without the feature flag — send override_ce_enable: true by default. If the backend distinguishes between the field being absent and it being explicitly true, this changes behavior for all users, not just those with the toggle UI.
Additional Locations (1)
There was a problem hiding this comment.
that's fine, it's only used in the backend if the backend flag is enabled
| : t('Context engine disabled (click to enable)') | ||
| } | ||
| > | ||
| <ContextEngineToggle> |
There was a problem hiding this comment.
This can probably just use <Flex align="center" gap="xs" padding="xs sm" height="100%">. The remaining styles look unnecessary.
shruthilayaj
deleted the
shruthi/chore/add-frontend-toggle-for-seer-explorer-chat
branch
2 participants
Adds a toggle in the chat toolbar to allow AI/ML team to enable or
disable context engine