Support using your own model subscription plan via CLI in Agent Mode

[oz-for-x]

🤖 Filed automatically by @ozdotdev on behalf of @vikvang1.
Source: https://x.com/vikvang1/status/2080733042050781310

Summary

Users want to use their existing model subscription plans (e.g. Grok/X, Claude, Codex) through a CLI-based coding agent in Warp, instead of consuming Warp credits or per-token API billing. At least one user reports they will not adopt Warp's agent until this kind of "CLI support" (bring-your-own model subscription via CLI) exists.

Context

Requested by a trusted engineer via @​ozdotdev on X, following a thread where a user asked to "add CLI model subscription plan support" and said they "won't be using warp agent till it has CLI support."
Source thread: https:​//x.com/vikvang1/status/2080733042050781310

Motivation

• Let users bring an existing model subscription (Grok, Claude Pro/Max, Codex, etc.) to Warp's agent via a local CLI rather than paying with Warp credits.
• Reduce adoption friction for users who already pay for a model subscription and prefer CLI-based auth.

Related issues

• Add Local Claude / Local Codex subscription options to /agent (use my own CLI, not Warp credits) #9609 (closed): Add Local Claude / Local Codex subscription options to /agent (use my own CLI, not Warp credits).
• Add Grok CLI (xAI) as a supported third-party CLI coding agent #11727 (open): Add Grok CLI (xAI) as a supported third-party CLI coding agent.
  This request is broader than a single provider: general support for using a subscription-backed model through a CLI in Agent Mode.

Proposed outcome

Provide a supported path to run Agent Mode against a CLI that authenticates with the user's own model subscription plan, with clear indication that Warp credits are not being consumed.

[warp-for-oss]

@oz-for-x[bot]

Here's what I found while triaging this issue:

Warp already supports running many third-party CLI agents directly in the terminal, and Claude Code/Codex can run as Oz cloud harnesses with provider credentials. This issue tracks the broader gap of using an existing subscription-backed CLI as the Agent Mode runtime without consuming Warp AI credits.

Maintainer details

I concluded that feature request to let Warp Agent Mode use an existing subscription-backed model CLI as the runtime/inference source instead of consuming Warp AI credits..

Triage summary

This is an enhancement request for Agent Mode/Oz: allow users to bring an existing provider subscription that is authenticated through a local CLI, and have Warp drive that CLI as the model/runtime instead of spending Warp AI credits or requiring separate per-token API billing.

Current behavior and evidence

• Warp already recognizes many third-party CLI coding agents locally and shows the CLI agent toolbelt when users run those commands directly in a Warp terminal. That is implemented around CLIAgent detection and plugin managers, not as a general Agent Mode model backend.
• Oz/Cloud Mode currently models external execution through a finite Harness enum and server-provided harness availability. The public CLI exposes --harness claude and --harness codex with matching auth-secret flags, and the Claude/Codex harness drivers prepare provider-specific API-key/secret-backed CLI environments.
• Public docs confirm Claude Code and Codex cloud harnesses call the provider directly with supplied credentials, while Warp still meters compute/platform credits. BYOK and SuperGrok cover local inference credentials/tokens, but BYOK/SuperGrok do not apply to cloud agents, and the docs explicitly state ChatGPT/Claude consumer subscriptions cannot be connected as third-party clients today.

Likely product/implementation gap

The missing piece is not just adding another model ID: it would require a product/API/UX path for Agent Mode to select a local or CLI-backed subscription runtime, handle provider-specific authentication/status, clearly disclose which credit buckets are or are not used, and bridge that runtime into the Agent Mode lifecycle.

Related issues

• Add Grok CLI (xAI) as a supported third-party CLI coding agent #11727 is related but narrower: it tracks Grok CLI as a supported third-party CLI coding agent.
• Add Local Claude / Local Codex subscription options to /agent (use my own CLI, not Warp credits) #9609 is an older closed request for local Claude/Codex subscription options.
• Allow custom model names per connected provider (BYO / SuperGrok) #13361 is related to BYO/custom provider model names, but does not cover driving a subscription-backed CLI runtime from Agent Mode.

I did not mark this as a duplicate because the open matches are narrower or cover adjacent BYOK/model-selection behavior rather than this broader subscription-backed CLI-in-Agent-Mode request.

This is my automated analysis and may be incorrect. A maintainer will verify the details.

Powered by Oz