fix: remove experimental toggle

[louis-menlo]

Describe Your Changes

Fix issue: #5753

This change removes the experimental toggle. All servers will be disabled by default, and users must toggle them all. This eliminates the need for the experimental toggle. The model shows a tool indicator but can't find tools to enable which is weird.

Fixes Issues

• Closes #
• Closes #

Self Checklist

• Added relevant comments, esp in complex areas
• Updated docs (for bug fixes / features)
• Created issues for follow-up changes or refactoring needed

---

Important

Remove experimental toggle, affecting ChatInput, SettingsMenu, and useGeneralSetting, with corresponding test updates.

• Behavior:
  • Removes experimentalFeatures toggle from ChatInput.tsx, SettingsMenu.tsx, and useGeneralSetting.ts.
  • MCP Servers are now always shown in SettingsMenu.tsx.
  • Tools are filtered based on model capabilities without experimental toggle in useChat.ts.
• Tests:
  • Updates tests in SettingsMenu.test.tsx to reflect removal of experimental toggle.
  • Removes tests related to experimentalFeatures in useGeneralSetting.test.ts.
  • Updates general.test.tsx to remove checks for experimental features toggle.
• Misc:
  • Removes experimentalFeatures from useGeneralSetting.ts state and related functions.

^{This description was created by for 8de5c17. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to cfbc6b9 in 1 minute and 19 seconds. Click for details.

• Reviewed 218 lines of code in 5 files
• Skipped 0 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. web-app/src/containers/ChatInput.tsx:60

• Draft comment:
  Removed the experimentalFeatures toggle: the destructuring now only retrieves spellCheckChatInput and the tool dropdown now checks only for model capabilities and MCP server status.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, describing what changes were made without providing any actionable feedback or suggestions. It doesn't ask for confirmation or suggest improvements.

2. web-app/src/containers/SettingsMenu.tsx:14

• Draft comment:
  Removed experimentalFeatures import and its conditional usage: the MCP servers menu item is now rendered unconditionally.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, describing what was changed without providing any actionable feedback or suggestions. It doesn't ask for confirmation or suggest improvements.

3. web-app/src/hooks/useChat.ts:246

• Draft comment:
  Removed the experimentalFeatures check from tool filtering: availableTools now depends solely on model capabilities, which simplifies the logic.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, explaining what was done in the code without providing any actionable feedback or suggestions. It doesn't ask for confirmation or suggest any improvements.

4. web-app/src/hooks/useGeneralSetting.ts:6

• Draft comment:
  Removed the experimentalFeatures state and its setter from the Zustand store, cleaning up the general settings as the experimental toggle is no longer needed.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, describing what was done without providing any actionable feedback or suggestions. It doesn't align with the rules for useful comments.

5. web-app/src/routes/settings/general.tsx:208

• Draft comment:
  Removed the Experimental Features toggle UI and its associated handler from the Advanced settings card to simplify the UI.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is purely informative, explaining what was done without providing any actionable feedback or suggestions. It doesn't align with the rules for useful comments.

Workflow ID: wflow_6S1TxL6UTY7nmpbx

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 8de5c17 in 1 minute and 18 seconds. Click for details.

• Reviewed 524 lines of code in 3 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. web-app/src/containers/__tests__/SettingsMenu.test.tsx:26

• Draft comment:
  Removed the experimentalFeatures property from the useGeneralSetting mock. Verify that SettingsMenu no longer depends on experimentalFeatures (e.g. for rendering MCP servers) and that the tests reflect the new default behavior.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the PR author to verify that a specific change does not affect the functionality of the SettingsMenu component. This falls under asking the author to ensure behavior is intended, which is against the rules. The comment does not provide a specific suggestion or point out a specific issue with the code.

2. web-app/src/hooks/__tests__/useGeneralSetting.test.ts:40

• Draft comment:
  Removed experimentalFeatures and related setExperimentalFeatures tests from the hook. Ensure all remaining state updates (like currentLanguage, spellCheckChatInput, and huggingfaceToken) are unaffected.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% The comment is asking the author to ensure that certain state updates are unaffected by the removal of experimental features. This falls under asking the author to ensure behavior, which is not allowed by the rules.

3. web-app/src/routes/settings/__tests__/general.test.tsx:294

• Draft comment:
  Removed tests for experimental features toggle from the general settings route. Confirm that the UI now consistently renders MCP servers and that testing focuses on the remaining settings (e.g. huggingface token, spell check).
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_SlIxslvRjsmSVLSI

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[github-actions]

Barecheck - Code coverage report

Total: 37.01%

Your code coverage diff: -0.10% ▾

Uncovered files and lines

File	Lines
web-app/src/containers/ChatInput.tsx	89-91, 113-114, 116-118, 134-135, 176-177, 199-201, 208-209, 212-215, 218-228, 231, 233-235, 241, 243, 245-246, 248-252, 255-256, 259, 261-264, 266-270, 272-284, 286-296, 298-307, 309-312, 315-316, 318-321, 324-325, 328-332, 335-336, 338-341, 344-346, 349-351, 354-357, 359-360, 362-366, 368-370, 373-374, 377-379, 381-383, 385-386, 388-389, 391-396, 399-404, 406-410, 446-454, 456-461, 463-465, 467-469, 471-472, 530, 572-586, 602-604, 609-613, 628-632, 647-661, 664-678, 688, 706, 723, 725-728
web-app/src/containers/SettingsMenu.tsx	185
web-app/src/hooks/useChat.ts	83-95, 109-115, 125-147, 150, 152, 154, 157, 160-165, 167-168, 173-175, 178-182, 185, 188-190, 192-200, 221, 250-251, 253, 268-279, 307-309, 312-313, 316-326, 328-332, 334-337, 339-366, 368-386, 388-390, 393-399, 401-402, 404-410, 412-417, 419-422, 424-432, 435, 437, 439-442, 444-454, 456-461, 463-472, 480-482, 513-514, 521-522
web-app/src/routes/settings/general.tsx	66, 70-71, 91, 93-94, 105-106, 120, 125, 129-130, 134-141, 144-148, 150-155, 158-165, 167-180, 182-183, 185-188, 191-197, 199-204, 227-237, 239-244, 246, 281, 286, 291-296, 325-335, 337-338, 373-377