mirror of
https://github.com/multica-ai/multica.git
synced 2026-07-12 12:18:55 +02:00
129efb7688
Qoder CN (`qoderclicn`) users could only reach a working custom runtime by misrouting through the Kiro backend, which launches `<cmd> acp --trust-all-tools`. That is incompatible with Qoder's global `--acp` / `--yolo` argv, so the task failed immediately with `kiro initialize failed` and no run messages. Expose `qoder` in the custom-profile protocol_family whitelist across every lockstep layer: - server/pkg/agent SupportedTypes (+ whitelist pin test) - migration 134 runtime_profile protocol_family CHECK (NOT VALID, mirroring 126) - packages/core RUNTIME_PROFILE_PROTOCOL_FAMILIES The existing qoderBackend already honors an ExecutablePath override and launches `<cmd> --yolo --acp`, so a profile with protocol_family=qoder and command_name=qoderclicn now launches with the correct argv instead of the Kiro shape. Provider branding/logo for qoder already exists. MUL-4018 Co-authored-by: J <j@multica.ai> Co-authored-by: multica-agent <github@multica.ai>
20 lines
607 B
SQL
20 lines
607 B
SQL
ALTER TABLE runtime_profile DROP CONSTRAINT IF EXISTS runtime_profile_protocol_family_check;
|
|
|
|
-- Restore the pre-134 whitelist (migration 126 shape, without qoder). NOT VALID
|
|
-- keeps the historical Gemini tolerance so the rollback cannot fail on old rows.
|
|
ALTER TABLE runtime_profile ADD CONSTRAINT runtime_profile_protocol_family_check
|
|
CHECK (protocol_family IN (
|
|
'claude',
|
|
'codebuddy',
|
|
'codex',
|
|
'copilot',
|
|
'opencode',
|
|
'openclaw',
|
|
'hermes',
|
|
'pi',
|
|
'cursor',
|
|
'kimi',
|
|
'kiro',
|
|
'antigravity'
|
|
)) NOT VALID;
|