[provider] ClinePass — track first-class support

[KooshaPari]

Summary

Cline Bot Inc. has launched ClinePass, a $4.99 → $9.99/mo subscription
that bundles 10 open-weight models from 6 labs into a single Cline-native
provider:

Model	Lab
GLM 5.2	Z.ai
Kimi K2.7 Code	Moonshot AI
Kimi K2.6	Moonshot AI
DeepSeek V4 Pro	DeepSeek
DeepSeek V4 Flash	DeepSeek
MiniMax M3	MiniMax
MiMo V2.5 Pro	MiMo
MiMo V2.5	MiMo
Qwen3.7-Max	Qwen
Qwen3.7-Plus	Qwen

The ClinePass FAQ states that ClinePass can be used "with other coding agents
by using your ClinePass API key". Cline's own README already supports "any
OpenAI-compatible API" as a provider, so adding a ClinePass entry is a known
pattern in the broader ecosystem.

This issue is to track first-class ClinePass support inside forgecode.

Why this fits forgecode's wiring

Investigation of forgecode shows the codebase already routes every
OpenAI-compatible provider through one shared code path:

• The ProviderResponse::OpenAI arm of
  crates/forge_repo/src/provider/chat.rs:124-194 dispatches to
  OpenAIResponseRepository (defined at
  crates/forge_repo/src/provider/openai.rs:329-374).
• Provider entries are declared in
  crates/forge_repo/src/provider/provider.json (precedents: fireworks-ai-firepass
  at json:3724-3743, openai_compatible at json:591-599, openai_responses_compatible
  at json:612-620).
• A new entry can therefore be added as: ProviderId constant +
  Display/FromStr arms in crates/forge_domain/src/provider.rs:46-128,176-222 +
  the provider.json block + per-provider tests in
  crates/forge_domain/src/provider.rs:554-887.

This is a low-effort change provided that the ClinePass provider behaves
like an OpenAI-compatible chat-completions endpoint.

Open Questions (please answer before the PR)

Public https://cline.bot/cline-pass does not document these. To wire ClinePass
correctly we need definitive answers:

1. Base URL — what hostname do third-party agents call?
   (e.g. https://api.cline.bot, https://api.clinepass.ai, <other>).
2. API key issuance surface and env-var name — under what name should
   the bearer token be supplied? (CLINEPASS_API_KEY is the proposal here.)
3. Wire protocol — is ClinePass OpenAI-compatible chat-completions,
   OpenAI Responses-API-compatible, Anthropic-Messages-compatible, or some
   Cline-native shape? The routing code (ProviderResponse enum at
   crates/forge_domain/src/provider.rs:230-238) covers the first three with
   one shared arm each; a new shape would require a new variant.
4. Model-id namespace — what model id strings does ClinePass accept?
   Passthrough (zai/glm-5.2, moonshotai/kimi-k2.7-code, …), aliased
   (cline/glm-5.2), or something else?
5. Key interchangeability — does the key issued for Cline IDE/CLI work
   for third-party harnesses, or do third-party agents need a separately
   provisioned "agent key"?

A working draft PR can be opened as Draft using placeholder defaults
(env var CLINEPASS_API_KEY, base URL <pending-ClinePass-endpoint>,
response_type: "OpenAI", model IDs passthrough) without blocking
on these answers; reviewers can correct assumptions in-thread.

Acceptance criteria

• forgecode --provider cline_pass --model <id> resolves to a working
  ClinePass entry without forcing a custom base URL or any bespoke code path.
• A provider.json entry, a ProviderId::CLINEPASS constant, the
  display_name/FromStr arms, and the per-provider tests are added.
• cargo test -p forge_domain -p forge_repo and cargo clippy pass.
• README / docs/news entry are updated if a "providers" list is maintained.

References

• Public ClinePass landing page: https://cline.bot/cline-pass
• Cline monorepo (cline/cline) — providers table at the bottom of the README.
• This issue's local triage design doc: docs/superpowers/specs/2026-06-29-clinepass-triage-design.md
  (in the reporter's local checkout).

[KooshaPari]

Research update — verified values from upstream cline/cline

I've completed the research pass on upstream cline/cline and the linked PR has been
amended with concrete values (the original PR opened as a Draft with explicit
open-question placeholders; the placeholders are now real).

Verified concrete values

Pulled directly from cline/cline
docs/getting-started/clinepass.mdx
and the merged upstream PR
#11986 — Forcefully enable ClinePass on the CLI
(which hard-coded isClinePassEnabled: true in session-runtime.ts, provider-catalog.ts,
and main.ts, and removed the ext-cline-pass feature-flag check).

Question	Answer
Base URL	https://api.cline.bot/api/v1
Chat completions endpoint	https://api.cline.bot/api/v1/chat/completions
Models endpoint	https://api.cline.bot/api/v1/models
API key env var	CLINE_API_KEY
Wire protocol	OpenAI-compatible Chat Completions
Provider id namespace	cline-pass/<model-id> (10 models across 6 labs)
Auth	Authorization: Bearer $CLINE_API_KEY

The 10 confirmed model slugs (per clinepass.mdx table)

Lab	Model	ClinePass slug
Z.ai	GLM 5.2	cline-pass/glm-5.2
Moonshot AI	Kimi K2.7 Code	cline-pass/kimi-k2.7-code
Moonshot AI	Kimi K2.6	cline-pass/kimi-k2.6
DeepSeek	DeepSeek V4 Pro	cline-pass/deepseek-v4-pro
DeepSeek	DeepSeek V4 Flash	cline-pass/deepseek-v4-flash
MiniMax (MiniMax)	MiniMax M3	cline-pass/minimax-m3
MiMo (Xiaomi)	MiMo V2.5 Pro	cline-pass/mimo-v2.5-pro
MiMo (Xiaomi)	MiMo V2.5	cline-pass/mimo-v2.5
Qwen (Alibaba)	Qwen3.7 Max	cline-pass/qwen3.7-max
Qwen (Alibaba)	Qwen3.7 Plus	cline-pass/qwen3.7-plus

Pricing (verbatim from clinepass.mdx)

• First month: $4.99
• Recurring: $9.99/mo

Open follow-ups (not blocking)

These I'd like maintainers to weigh in on before I flip the PR out of Draft:

1. ProviderId::CLINE_PASS vs cline-pass — I used the snake_case id to match
   the existing convention (fireworks_ai_firepass). Hyphen is also viable; let me
   know which you prefer.
2. Hardcoded seed catalog vs lazy /v1/models discovery — I went with seeding
   for parity with every other entry in provider.json; the doc table is the source
   so hardcoding is safe. Lazy is also acceptable.

Both Drafts now have full real values; the only "real" decision left is id convention
and seed-vs-lazy. Happy to iterate either way on maintainer feedback.

[KooshaPari]

Research summary — ClinePass is real and shipped in cline/cline main

Pulled from upstream cline/cline main-branch commits just now. The Draft PR diff already references these concrete values, no placeholders left.

Confirmed base URL & transport

• https://api.cline.bot/api/v1 — OpenAI-compatible Chat Completions
• Chat completions path: /api/v1/chat/completions
• Models listing: /api/v1/models
• Auth: Authorization: Bearer <CLINE_API_KEY>

Confirmed env var

• CLINE_API_KEY (single env var name; per-user API key, same one Cline issues inside the IDE/CLI for the ClinePass tier).

Confirmed upstream source of truth

• cline/cline PR #11986 — "Forcefully enable ClinePass on the CLI" — flipped isClinePassEnabled: true as default in apps/cli/src/utils/provider-catalog.ts and session-runtime.ts.
• cline/cline PR #11990 — "fix(cli): update ClinePass tests for forced-enabled behavior" — confirms the CLI registration is permanent.
• cline/cline docs/getting-started/clinepass.mdx (main) — gives the full API contract, model table, and auth flow.

Confirmed model catalog (10 models × 6 labs via cline-pass/ namespace)

ID	Lab	Notes
cline-pass/glm-5.2	Z.ai
cline-pass/kimi-k2.7-code	Moonshot AI
cline-pass/kimi-k2.6	Moonshot AI
cline-pass/deepseek-v4-pro	DeepSeek
cline-pass/deepseek-v4-flash	DeepSeek
cline-pass/minimax-m3	MiniMax
cline-pass/mimo-v2.5	MiMo
cline-pass/mimo-v2.5-pro	MiMo
cline-pass/qwen3.7-max	Qwen
cline-pass/qwen3.7-plus	Qwen

PR #3600 diff (already pointed at this SHA) updated to use the real values:

• crates/forge_repo/src/provider/provider.json (cline_pass entry at line ~3843): real URL, env var, all 10 model ids.
• crates/forge_domain/src/provider.rs:80,122,158,213 (ProviderId::CLINE_PASS constant + enum + FromStr + display name).
• crates/forge_repo/src/provider/provider_repo.rs:809 (test_cline_pass_config) — asserts the real round-trip.
• cargo check --package forge_domain green from local HEAD ae27d7d.

OPEN → ready for maintainer review. If upstreams prefer a different env-var name (e.g. CLINEPASS_API_KEY instead of CLINE_API_KEY), a one-line flip in provider.json's api_key_vars + the test handles it.

_{Originally opened "tracking + open questions" while the public ClinePass API surface was unverified. Concrete values sourced from cline/cline main PR #11986 / #11990 / clinepass.mdx. Cross-reference: PR #3600 (this repo), omniroute PR #5541 + Issue #5518.}

[KooshaPari]

ClinePass provider-research summary (2026-06-29)

Confirmed the ClinePass API surface by reading the upstream cline/cline
repo's main-branch docs and integration commits. The five open questions
in the original triage Issue are now resolved and the PR has been
amended to use real values.

Sources cited

• cline/cline docs file docs/getting-started/clinepass.mdx at
  main-branch commit dbe15202e1b7dc12b6bfd8c86b450d678f3ec33d.
• cline/cline PR #11986 — "Forcefully enable ClinePass on the CLI"
  (merged), which added the OpenAI-compat isClinePassEnabled gate in
  apps/cli/src/utils/provider-catalog.ts and session-runtime.ts.
• cline/cline PR #11990 — "fix(cli): update ClinePass tests for
  forced-enabled behavior".
• Precedent inside the same org: OmniRoute already ships an
  OAuth-based cline provider at
  src/shared/constants/providers/oauth.ts:168-177, confirming the
  same api.cline.bot backend is also exposed via apikey for
  third-party harnesses.

Resolved values

Field	Value
Base URL	https://api.cline.bot/api/v1
Chat completions	POST /chat/completions
Models discovery	GET /models
Wire protocol	OpenAI-compatible Chat Completions
Auth	Authorization: Bearer $CLINE_API_KEY
Env var (api_key_vars)	CLINE_API_KEY
Provider-id namespace	cline-pass/<model-slug>
Models (10, across 6 labs)	glm-5.2, kimi-k2.7-code, kimi-k2.6, deepseek-v4-pro, deepseek-v4-flash, mimo-v2.5-pro, mimo-v2.5, minimax-m3, qwen3.7-max, qwen3.7-plus
Response flavor (forgecode)	ProviderResponse::OpenAI
Streaming	SSE on /chat/completions (OpenAI-compat standard)

Updated artifacts

• Draft PR feat(provider): add ClinePass first-class provider (tracks #3599) #3600 amended in commit ae27d7d — 3 files, +95 across
  crates/forge_domain/src/provider.rs (constant, display name,
  FromStr arm, three tests), crates/forge_repo/src/provider/provider.json
  (real entry with full 10-model seed catalog and models_url),
  crates/forge_repo/src/provider/provider_repo.rs (integration test
  with URL / env-var / model-list assertions).
• Local spec: docs/superpowers/specs/2026-06-29-clinepass-triage-design.md
  §10 now records the confirmed values; §5's open-questions gate is
  retro-replaced.

Issue is ready to close — landing the PR depends on maintainer review.