Make 'enhance prompt' button optional through a setting

[cissna]

What specific problem does this solve?

UI is getting problematically cluttered (subjective, but easily solvable), including several things that many users do not use.
Examples are: codebase indexing, add images to message, enhance prompt.

I'm ok with the other two, so I'm narrowing the scope of this proposal to specifically the 'enhance prompt' button. (also, in my opinion, the stuff below the text box doesn't feel as cluttered as the stuff in the text box, so I think 'enhance prompt' more urgently needs to be made optional).

Additional context (optional)

The real question is where should this setting go. I don't see a great place for it, but my suggestion would be "experimental settings" but it is by default on, or making a new settings page for UI elements (if you choose the latter, I would probably make all 3 of the things I mentioned optional so the settings page doesn't feel like a waste. If this is the way to go, I can redo this ticket to be more focused on that).

Roo Code Task Links (Optional)

No response

Request checklist

• I've searched existing Issues and Discussions for duplicates
• This describes a specific problem with clear impact and context

Interested in implementing this?

• Yes, I'd like to help implement this feature

Implementation requirements

• I understand this needs approval before implementation begins

How should this be solved? (REQUIRED if contributing, optional otherwise)

Make enhance prompt button only usable/visible if its associated setting is turned on.
Add its associated setting in Experimental. By default it is on, the same as before.

How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)

For a fresh install of roo code, the only difference will be an additional, checked "on" setting in 'Experimental'. If that setting is checked off, the button formerly in the top right corner of the prompt text box will no longer be there.

Technical considerations (REQUIRED if contributing, optional otherwise)

n/a, should be very easy.

Trade-offs and risks (REQUIRED if contributing, optional otherwise)

Alternative: add a UI setting that includes toggles for 'enhance prompt', 'codebase indexing', 'add images to prompt', 'api configuration', 'auto-approve', 'text saying "(@ to add context, /to switch modes...", 'send button'. This kind of settings page could also allow for customizing which widgets (e.g. new task, marketplace, settings) are visible which is something else that was bothering me. But that should probably be a later ticket if we add that.

[roomote]

Hi @cissna! I noticed you expressed interest in implementing this feature. I'm here to help out the maintainers and am going to see if I can assist with the implementation or at least get close enough to be helpful! I'll work on adding a setting to make the enhance prompt button optional as you suggested. Feel free to collaborate or provide any additional input!

[daniel-lxs]

Hey @cissna, thank you for creating this proposal. The experimental settings section is meant for settings that shouldn't be enabled by default and are still being tested for stability before being moved elsewhere. Because of that, it wouldn't be the right place for this button.

That being said, I'll assign this issue to you. If you have a better idea for how the UI should look, feel free to explore it. The main goal of placing the button there is to keep it readily accessible, so we'd like to preserve that aspect.