Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

First-class provider support for subscription CLIs: OpenCode Go and Command Code (GOAT)

Aperta
  • Qualcosa non va?
#545 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
node.js, typescript
Ambito
developer-experience, tooling

Direzione di ricerca

Start with src/shared/agentProvider.ts and compare the existing agy, codex, and grok provider setups. Then trace how providers populate the Add-Agent model picker and Settings → AI Engines, and check the existing custom-provider limitations. Done means the issue's chosen scope is explicit and the supported path or limitations for both subscriptions are documented or implemented.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Problem / motivation

Two $10/month coding subscriptions have no first-class path in the harness, so a worker can't use them the way it uses Claude Code / Codex.

  1. Command Code (GOAT plan, $10/mo). Install is npm i -g command-code, binary cmd. There is no commandcode entry in the AgentProvider union in src/shared/agentProvider.ts, so the only route is provider: 'custom'. That preset is hiveAware: false, declares no hookBridge and no bridge, and is canReceiveInbox: false — the worker gets no live status, its inbox mail bounces to the god, and it has no model quick-picks. Users also report the GOAT subscription is tied to Command Code's own CLI/account, so "just use the underlying key elsewhere" isn't a given.
  2. OpenCode Go ($10/mo). OpenCode is already a supported provider, but it isn't clear whether the Go subscription's model set appears in the Add-Agent model picker (does that list come from the installed CLI's own catalog?) or whether a go provider key/endpoint has to be configured in Settings → AI Engines first.
Proposed solution
  • A first-class commandcode preset: defaultCommand: 'cmd', model flag + quick-picks, and a hookBridge/bridge so it gets live status and inbox delivery the way agy / codex / grok do.
  • A documented path for OpenCode Go — either the model picker already picks it up (worth stating in the docs), or an entry in Settings → AI Engines / providerBaseUrls.
  • If neither preset is planned, document the custom-provider route and its limits (no hooks, no inbox delivery, no model catalog) so users know what they lose before picking it.
Timeline

Is there a roadmap position for subscription-CLI providers like these two? Even "not planned, PR welcome" helps. Related: pi already has a third-party pi-commandcode-provider that does subscription login, so the pi bridge may be the cheapest integration point; and cost/live-status parity for non-Claude engines is already tracked in #535.

Screenshot, mockup or recording

None attached. I couldn't run the app to capture a screen on this machine. The gap is visible in the Add-Agent provider list (no Command Code / OpenCode Go entry) and in the key fields under Settings → AI Engines.

Alternatives considered
  • provider: 'custom' with cmd — runs, but loses live status, inbox delivery, cost accounting, and model quick-picks.
  • pi + the third-party pi-commandcode-provider — keeps the pi hooks bridge, but depends on an unofficial package.
Area

Onboarding / config

Pre-flight
  • I attached a screenshot, mockup or recording above. — not attached, see the note above.
  • I searched existing issues for "Command Code" and "OpenCode Go" and found no duplicate.
Lingua principale
TypeScript
Stelle
8.5k
Fork
1.2k
Merge medio
1g 14h
PR unite (30g)
71

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di HarnessMD/munder-difflin

Tutte le issue di HarnessMD/munder-difflin

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.