[Enhancement]: Hide deprecated features

[brianredbeard]

What features would you like to see added?

It would be great if there was a flag (--hide-deprecated) which would all me to hide deprecated features from users.

More details

Using this block as an example:

LibreChat/client/src/components/Chat/Menus/Endpoints/components/EndpointItem.tsx

Lines 87 to 98 in 3208124

	{/* TODO: remove this after deprecation */}
	{endpoint.value === 'gptPlugins' && (
	<TooltipAnchor
	description={localize('com_endpoint_deprecated_info')}
	aria-label={localize('com_endpoint_deprecated_info_a11y')}
	render={
	<span className="ml-2 rounded bg-amber-600/70 px-2 py-0.5 text-xs font-semibold text-white">
	{localize('com_endpoint_deprecated')}
	</span>
	}
	/>
	)}

I don't use the plugins feature and would prefer to have the visual clutter gone.

Which components are impacted by your request?

No response

Pictures

No response

Code of Conduct

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

[danny-avila]

No need for this as it will be completely removed soon

[onestardao]

Totally get the instinct to clean up deprecated stuff — especially when it keeps yelling at you in bright amber.
But quick heads-up: visual clutter is rarely just aesthetic — it’s often a semantic trap.

What feels like a UI nuisance today might be silently linked to legacy config branches, or even worse:
users copy-pasting half-dead YAMLs thinking “well it’s still visible so maybe it’s fine?”

Seen too many cases where that led to shadow bugs 3 months later —
like: “why is my plugin config still being parsed if it’s marked deprecated?” 🤷

So yeah, hiding deprecated is good.
But removal without invisible fallback logic is even better. Otherwise you get phantom behavior, and those are the real demons.