Bring your subscription, not just an API key

Most agent clients quietly assume one thing about how you pay: a platform API key, billed per token, from a single vendor. That’s fine until you realize you’re already paying for a subscription that includes the exact models you want to code with, and your tooling can’t touch it.

Warden now can. It speaks OpenAI’s subscription-tier path through a real OAuth sign-in, so the plan you already hold drives the agent, sitting right next to your Anthropic and Gemini accounts in the same client.

Why a second billing lane matters

Warden’s whole premise is that you shouldn’t be locked to one provider’s pricing, availability, or model lineup. Pooling accounts means that when one hits a rate limit, work keeps moving on another. A subscription lane, not just another API key, widens that further. It’s a different cost structure entirely, so you can route everyday work against a flat-rate plan and save metered spend for when you actually need it.

The point isn’t any single provider. It’s that Warden treats providers as interchangeable supply, and the more lanes you give it, the harder it is for any one of them to slow you down.

Sign-in that survives a headless box

A lot of OAuth flows assume a desktop browser on the same machine. Plenty of developers run their agent inside WSL or over SSH, where that assumption breaks. Warden’s sign-in handles that case directly with a paste-back flow for environments that have no local browser, so connecting your account doesn’t require a workaround. You authorize once, the one-time terms notice is acknowledged and recorded, and you’re driving.

Where it stands

This is live in Warden today (still pre-alpha, MIT, no version promises yet). Warden is the client that treats facts as facts. It queries TheAuditor instead of dumping files into the prompt, remembers through Curator, and is dispatched across providers by Arbiter. See where Warden fits the stack or grab the RSS feed.