Skip to content

Latest commit

 

History

History
23 lines (20 loc) · 1.64 KB

qoder.md

File metadata and controls

23 lines (20 loc) · 1.64 KB

Qoder Client Integration

Qoder follows the shared client-integration ownership contract; this page records only what is specific to it.

Qoder settings ownership

Qoder IDE / qodercli uses JSON at settings.json under QODER_CONFIG_DIR, default ~/.qoder; qoderHomeDir resolves that directory once for export, writing and detection, and refuses a relative override. The Qoder exporter in src/clients/config-export.ts writes providers.opencodex and one modelConfigs.customModels entry per model. Array ownership selects both provider and model, preserving same-named models belonging to other providers. Apply, refresh and disable use the existing recorded-fragment writer; restore uses its snapshots. Model IDs that cannot be represented by the shared selector grammar refuse managed contribution construction. The default model is the first normalized model; an empty catalog omits the default. Input limits use authoritative context metadata or Qoder's requested 128000 fallback. Exports reject non-loopback placeholder use; the writer's existing admission gate protects apply while permitting cleanup after a bind change. ocx export --client qoder asks the live /api/client-config route, like Raycast and Factory Droid, so the serving process's bind and unauthenticated loopback listener decide the exported URL. Owned-catalog refresh in ocx sync, /api/sync and catalog refresh includes Qoder. CLI help, Dashboard export rows, integration tabs and preview-path validation register the same Qoder client; the managed path templates live in src/integrations/mutation-plan.ts and the builder in src/clients/config-export/qoder.ts.