-
Notifications
You must be signed in to change notification settings - Fork 2
Migrate opencode + omp + zcode clients to Provider Injection #435
Copy link
Copy link
Open
Labels
campaign:0.1.90.1.9 coexistence provider injection & DSH client campaign0.1.9 coexistence provider injection & DSH client campaignenhancementNew feature or requestNew feature or requestneeds-triageMaintainer needs to evaluate this issueMaintainer needs to evaluate this issuephase:beta40.1.9 phase: opencode/omp/zcode migration0.1.9 phase: opencode/omp/zcode migration
Description
Metadata
Metadata
Assignees
Labels
campaign:0.1.90.1.9 coexistence provider injection & DSH client campaign0.1.9 coexistence provider injection & DSH client campaignenhancementNew feature or requestNew feature or requestneeds-triageMaintainer needs to evaluate this issueMaintainer needs to evaluate this issuephase:beta40.1.9 phase: opencode/omp/zcode migration0.1.9 phase: opencode/omp/zcode migration
Summary
Migrate opencode, omp, and zcode from Managed Takeover to Provider Injection. Phase 4 of campaign 0.1.9 (target 0.1.9-beta4).
Scope
opencode (largest delta — full overwrite today)
opencode_config_text(gateway.rs:5725-5787) currently emits a complete file containing only codexhub providers. Change to surgical edit of the existingopencode.json: insert/update the codexhub provider entry, preserve all foreign keys and providers.model/small_model; activation becomes user-owned.omp
models.yml: stop full overwrite (omp_models_yml_text,gateway.rs:5936-5971); insert codexhub providers preserving foreign ones.config.yml:modelRoleshandling already surgical — stop forcing default role to codexhub; activation user-owned.zcode
config.jsonprovider map is already surgical — mostly readback-semantics migration to block fingerprint.codexhub.jsoncatalog + cache are CodexHub-owned separate files; full overwrite of own files is compatible with coexistence — keep, but document ownership boundary.Existing managed users
Acceptance criteria
Related