What problem does it solve? Adding or changing LLM providers in the Omega Loops Rust workspace requires touching provider IDs, auth strategies, provider.json entries, TUI slash commands, and shell plugin aliases across many crates, and mistakes like reimplementing device polling or misconfiguring token refresh cause subtle auth failures. ## Core Features & Use Cases - Provider Integration Workflow: Step-by-step process for adding a new OAuth provider, from ProviderId constants and FromStr aliases through provider.json auth methods to TUI and shell plugin wiring. - SuperGrok / xAI OAuth Reference: Documents the shipped xai_oauth provider using RFC 8628 device-code flow against auth.x.ai, including client ID, scopes, endpoints, and UX labeling. - Pitfall & Debug Guidance: Covers tier-based HTTP 403 entitlement errors, fail-closed model merge bugs, xAI pricing deserialization, and Cargo workspace issues, with verification commands. - Use Case: You want users to log into SuperGrok without an API key. Follow the workflow to register the xai_oauth provider, wire the /supergrok slash command, and verify with focused cargo tests. ## Quick Start Ask the agent to add a new OAuth device-flow provider to Omega Loops following the provider workflow and verify it with the listed cargo check and test commands.
