v6.8.2

Published to npm as oc-codex-multi-auth@6.8.2.

npm install -g oc-codex-multi-auth@6.8.2

Fixed

gpt-5.6-sol rejected through the plugin while working in the Codex CLI/TUI for the same account (#196, #199)

Follow-up to the 6.8.1 auto-fallback fix: that made Sol degrade gracefully, this addresses the reported rejection itself. Diffing the plugin's request against upstream openai/codex found two client-identity mismatches versus what the Codex CLI sends:

• Missing Codex User-Agent. The plugin declared originator: codex_cli_rs but sent the host runtime's UA. The backend reads the client version from the UA product token, and the model catalog gates the 5.6 tiers on minimal_client_version: 0.144.0. Requests now carry codex_cli_rs/<version> (<os> <osver>; <arch>). Opt out with CODEX_AUTH_DISABLE_CODEX_USER_AGENT=1; override the advertised version with CODEX_AUTH_CLIENT_VERSION.
• Non-upstream openai-organization pinning. The plugin pinned the token's organizations[0] on every request for accounts carrying an organization claim — a header upstream Codex never sends on ChatGPT-Codex requests (workspace routing is carried entirely by chatgpt-account-id), and one that can shift the backend's entitlement evaluation to a workspace outside the narrow Sol preview while the broader Terra/Luna preview still passes. The header is no longer sent by default; restore the legacy behavior with CODEX_AUTH_SEND_ORGANIZATION_HEADER=1. The org-variant account deduplication is untouched.

Verified against the live backend: gpt-5.5, gpt-5.6-sol, and gpt-5.6-terra all stream successfully with the new identity (probed from the published package). The failing condition itself is workspace-account-specific, so if Sol still fails for you on 6.8.2, please comment on #196 with codex-health output.