ce-code-review: allow user-configured cross-model peer routes (e.g. GLM via an Anthropic-compatible endpoint)
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à
- Tranquilla
- Stack tecnologico
- shell, typescript, yaml
Direzione di ricerca
Start with scripts/cross-model-adversarial-review.sh and references/cross-model-review.md, then trace how cross_model_peer: is read from .compound-engineering/config.local.yaml and how route validation, host exclusion, announcements, and receipts work. The issue sketches desired custom-peer settings but leaves security and design choices open. Done means deciding whether custom routes are supported or curated routes remain the policy, then implementing that decision and documenting it.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
What I ran into
I wanted to use GLM-5.3 (served over z.ai's Anthropic-compatible endpoint) as the independent cross-model adversarial peer in ce-code-review. There is no supported way to do that today, even though the mechanism it would need already exists.
Two hard stops in scripts/cross-model-adversarial-review.sh:
CROSS_MODEL_FIXED_ROUTEonly acceptscodex | claude | grok-cli | grok-cursor | cursor | composer. Anything else fail-closes, which is correct behaviour — but it means the route set is not extensible.validate_model_overrideacceptsclaude:opus|sonnet|haiku|claude-*only, so binding a non-Anthropic model id to theclauderoute is rejected as a cross-family substitution — also correct, and also a dead end for this case.
The only mechanically working workaround is to export ANTHROPIC_BASE_URL (or shim a claude binary) so the sanctioned claude route silently reaches a different provider. That defeats the entire point of the disclosure and receipt machinery: the pre-egress announcement would name Anthropic while the diff goes somewhere else. I am not doing that, and I don't think anyone should.
Why this seems worth supporting
The design already separates "which provider" from "which model/effort", already has a user-facing preference key (cross_model_peer: in .compound-engineering/config.local.yaml), and already distinguishes receipt-verified from receipt-less routes in the announce wording. A user-defined route would slot into that structure rather than fight it.
Concretely, several strong coding models now ship an Anthropic-compatible endpoint and are driven by the same claude -p adapter you already have. The delta is a base URL, an auth source, and a model id — not a new adapter.
Rough shape of a proposal
Something like a cross_model_custom_peers: block in config.local.yaml:
cross_model_custom_peers:
- name: glm
adapter: claude # reuse the existing claude -p adapter
base_url: https://api.z.ai/api/anthropic
model: glm-5.3
family: glm # participates in same-family host exclusion
receipt: false # announce as 'serving model unverified on this route'
with, I would suggest:
- a custom peer never being reachable by default — it must be named in
cross_model_peer:orCROSS_MODEL_PEERS, so nothing changes for existing users; - the announce naming the endpoint host alongside the model, since the recipient is no longer implied by the route name;
receipt: falsebeing the default for custom peers, so the existing "requested X at Y; serving model/effort unverified on this route" wording carries the honesty burden;- the declared
familyfeeding the same host-exclusion check, withunknownskipping the pass exactly as it does today.
Happy to be told this is out of scope — the curated-route model is a defensible position, and a self-declared family field is weaker evidence than an attested host. But if the answer is "curated only", it would help to say so in references/cross-model-review.md, because the presence of cross_model_peer: reads like an extension point.
Context: I got here from a project that already treats external review egress as an explicitly authorized, provider-named decision in its own conventions file. The thing I most want to avoid is people reaching for the base-URL workaround because the honest path does not exist.
- Lingua principale
- TypeScript
- Stelle
- 25.6k
- Fork
- 2.1k
- Merge medio
- 3h 57m
- PR unite (30g)
- 170
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di EveryInc/compound-engineering-plugin
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
EveryInc/compound-engineering-plugin#2085 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
EveryInc/compound-engineering-plugin#795 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 80/100
EveryInc/compound-engineering-plugin#2084 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
EveryInc/compound-engineering-plugin#2083 ·
I maintainer di solito rispondono entro 1 giorno
-
Host support: DeepSeek Harness (dsh)Forse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 3/5 1-2 giorni Idoneità per principianti 48/100
EveryInc/compound-engineering-plugin#2072 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di EveryInc/compound-engineering-plugin
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
e2e-failure ready-to-code
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
redhat-developer/rhdh-plugin-export-overlays#4794 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
I maintainer di solito rispondono entro 1 giorno
-
area: plugins documentation good first issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 83/100
CatVinci-Studio/Textus#727 ·
I maintainer di solito rispondono entro 1 giorno