Make native Claude request preservation a discoverable pooling default #6546

Area

Multiple areas

What are you trying to accomplish?

Enable multi-account Claude routing from the account-pooling settings without discovering two internal native Messages rollout flags. Preserve native request/cache structure for supported direct Anthropic routes, with an explicit compatibility override.

What prevents this today?

The native account-pool implementation in #6534 remains opt-in through managedMessagesNative and managedMessagesNativeOAuth. The dashboard pooling toggle does not configure that path, and the configuration reference still describes pooled accounts as staying on the bridge.

What should OpenCodex do?

When Anthropic pooling is enabled, prefer native Claude Messages by default. Expose an advanced “Preserve native Claude requests” setting inside the pool controls, allowing legacy translation when needed. Explain route-specific fallback and that account switching may cold-start the replacement cache. Preserve explicit settings while pooling is disabled and do not alter other providers.

Example usage or interface

Providers → Anthropic → Account pooling → enable. Advanced settings show “Preserve native Claude requests” enabled by default. Turning it off selects the legacy bridge for pooled requests. A failed save leaves the previous state intact.

Alternatives or workarounds

Manually enable both native Messages rollout options through ocx api policy. This is difficult to discover and easy to omit.

Additional context

Depends on #6534 (native pooling and request compatibility) and relates to #6532 and #6531 / #6533. This is a separate UI/default-policy contribution; it does not modify the user's installed runtime or account login.

Checks

• I searched existing issues and documentation.
• This request describes a concrete OpenCodex workflow rather than merely naming a desired technology.
• I removed secrets and personal data.