ZDR is checked per-model, but it is a property of the agent that runs it

Aperta
#69 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

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
python, shell
Ambito
cli, security, tooling

Direzione di ricerca

The selector is in select-panel.py; start at its zdr_pool filter and trace how each seat resolves an agent. Compare debate-acpx.json with ~/.acpx/agents/luna-or/start.sh and the other named agent entry points. Done means private-repo selection accepts only seats whose resolved agent is ZDR-capable, while direct OpenAI, Google, and Anthropic agents cannot satisfy the constraint.

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

Descrizione

What happens

On a private repo, select-panel.py treats ZDR as a property of the model:

zdr_pool = [m for m in pool if m.get("route") == 31501]

But whether content actually reaches a ZDR endpoint depends on the agent that runs the model, not the model itself. The same registry entry can be ZDR or not depending on the seat:

  • gpt56_luna reached through the luna-or agent goes to OpenRouter. ~/.acpx/agents/luna-or/start.sh pins openrouter/openai/gpt-5.6-luna and authenticates with OPENROUTER_API_KEY.
  • The same model reached through the codex agent goes to the local Codex CLI, straight to OpenAI.

One is ZDR, one is not, and the registry cannot express the difference.

Why it matters, in both directions

Under-marking blocks a safe panel. Nothing OpenRouter-served currently carries route: 31501, so on a private repo the fallback preset — whose whole purpose is "the local Codex CLI is broken" — refuses to run:

only 1 ZDR model(s) available for 4 seats on a private repo;
ZDR is a hard constraint — request fewer seats or add ZDR models

The one qualifying model, deepseek_v4flash, is transport: proxy, and PROXY_AGENT = "opus" means it only reaches the proxy branch on an opus seat. No fallback seat is one, so in practice the preset cannot run on a private repo at all.

Over-marking would be worse. The obvious fix — adding route: 31501 to gpt56_luna — makes a codex seat eligible for it on a private repo, and that seat sends the diff to OpenAI directly while the selector reports the panel as ZDR-clean. That is a silent failure of the exact control the flag exists to enforce.

There is currently no registry edit that fixes the first problem without creating the second.

Suggested direction

Move the ZDR decision to the agent, or to the (agent, model) pair:

  • Mark agents ZDR-capable rather than models — an agents section, or a zdr_agents list. luna-or, kimi-k3 and deepseek all authenticate with OPENROUTER_API_KEY and qualify; codex, antigravity (Google's agy) and opus (claude --print) do not.
  • Then zdr_pool filters on the seat's resolved agent, and a model is ZDR only via a ZDR agent.
  • Failing that, at minimum let a seat declare zdr: true in debate-acpx.json so the OpenRouter-backed seats can be marked without making their models globally eligible.

Worth checking antigravity explicitly while doing this. It is in the fallback preset but runs agy directly, so it can never satisfy a ZDR constraint and should probably be excluded from that preset, or the preset documented as non-ZDR.

Workaround

Build a run-scoped registry containing only the OpenRouter-served entries and pass it via --registry. That gets a ZDR panel without leaving a wrong marking behind in ~/.claude/debate-models.json.

Found while reviewing a private repo where Codex was rate-limited and fallback was the intended path.

Lingua principale
Shell
Stelle
10
Fork
4
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

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

  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 STRML/cc-debate

Tutte le issue di STRML/cc-debate

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.