[Bug]: Presence of a custom endpoint yields OpenAI parameters on Google endpoint

[AetherMagee]

What happened?

hi its me again
The contents of this bug are extremely similar to #5196 except this time the button doesn't disappear, but contains params like Stop sequences, Freq. and Pres. penalty, etc, which Google obviously does not have.
...and why is Google literally the only endpoint with the settings in a button I thought you had a sidebar for that?

Steps to Reproduce

1. Generate at least 2 responses from the Google endpoint
2. Switch to a custom endpoint, generate at least 1 response from that
3. Switch back to Google, generate 1 more response
4. observe le bug. again.

What browsers are you seeing the problem on?

Chrome, Mobile (Android)

Relevant log output

No response

Screenshots

lc-bug-2.mp4

Code of Conduct

• I agree to follow this project's Code of Conduct

[danny-avila]

Thanks again. I know exactly the issue and I may need to be more aggressive in preventing it.

...and why is Google literally the only endpoint with the settings in a button I thought you had a sidebar for that?

I still have to migrate Google to the new Parameters UI. It has the most complex params (i.e. examples), and I may just remove them for simplicity sake as they are likely little used.

[AetherMagee]

Wait, google has more than temp, top_p/k and stop sequneces? I haven't seen those used on api often, if ever.
IMO it would be fair to discard them for now, given how even fairly power user UIs (i.e. tavern) don't include them.