Benchmark: run the paired premise-checking A/B on Claude (Copilot SDK and Claude Agent SDK)
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- github, javascript, typescript
- Área
- ai-infra-agents, testing
Línea de trabajo
Start with scripts/premise-checking-ab.mjs on the bradygaster-premise-checking-plan branch and review the existing Copilot SDK calls and benchmark protocol. Then verify the Claude Agent SDK mapping against its current docs before extracting HostDriver and adding the Claude driver. Done means a frozen paired row matches its protocol hashes under the unchanged Copilot driver and the Claude host completes a pilot and paired calibration with the required usage and ledger data.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Summary
Run Squad's paired premise-checking A/B benchmark (scripts/premise-checking-ab.mjs, on branch bradygaster-premise-checking-plan) on Claude. That gives Claude users a measured "Claude alone vs. Claude + Squad" comparison. Related: #2438 (Claude Code projection).
Claude users will ask two separate questions:
- Model: does Squad help when the model is Claude?
- Harness: does Squad help inside Claude Code itself?
Results from Copilot alone answer neither.
Design: one fixture, varying only the host
| Copilot SDK (existing driver) | Claude Agent SDK (new driver) | |
|---|---|---|
| Claude model | Phase A (done for calibration, below) | Phase B |
| gpt-5.3-codex | existing results | n/a |
The fixture, oracle criteria, arms, prompt sources, budgets, blinding and adjudication all stay frozen. Pin one Claude model ID across both phases.
Phase A: Claude model through the Copilot SDK
Implemented on branch squad/claude-ab-pilot (commit fae48038):
--model <id>: recorded in the run manifest. Resuming a campaign under a different model is refused. The default staysgpt-5.3-codex, so existing manifests still validate.--reviewer-check: a scripted truth-first run that is told to dispatch the Fact Checker once. It verifies reviewer accounting end to end. It is not a measured arm.--revalidate-pilot: accepts a pilot with no Fact Checker dispatch only if a reviewer check passed on the same model.- Dispatch counts: pilot and paired validation now report Fact Checker dispatches per arm instead of failing when there are none.
Phase B: Claude Agent SDK driver (to do)
- Driver interface: put the harness's Copilot SDK calls behind a
HostDriverinterface (preflight,createSession,sendAndWait,abort, normalizedmessage/usage/toolevents). Re-run one frozen paired row and match its protocol hashes to prove the Copilot driver is unchanged. - Claude driver: add
--host claudeusingquery().- Custom tools go through an in-process MCP server.
allowedToolsis limited toread_evidenceandtask, andsettingSources: []keeps user and project config out.canUseToolrejects everything else.- Usage comes from assistant messages plus
total_cost_usdon the result.
- Fact Checker dispatch: keep it as a separate
query()session, as it is today. NativeAgent-tool dispatch can come later as an optional fourth arm (truth-first-native). - Ledger: record cache-read and cache-write input separately, but charge budgets on all input classes combined.
- Verify the mapping: check it against current Claude Agent SDK docs before building.
Results so far (2026-11-09, claude-sonnet-5.5 through Copilot)
Pilot (revenue-midflight-agent, all 3 arms):
- 2 coordinator calls per episode.
- About 78K input tokens per episode, roughly half of them cache reads, and about 310 output tokens.
- 7–20 s per episode.
- Claude made no Fact Checker dispatch. That failed the original gate until the reviewer check passed (2 reviewer calls, about 17K input tokens, every evidence read traced).
Paired calibration (16 runs: 8 families × baseline/truth-first):
- 16 of 16 completed, and the instrumentation check passed.
- 927,615 input tokens (340K cache reads, 587K cache writes) and 5,743 output tokens, in 125 s altogether.
- About $1.60 at API rates on Sonnet 5.5 and about $3.10 on Opus 5.5.
- Fact Checker dispatches: 0 of 8 in baseline and 0 of 8 in truth-first.
- Before blinded adjudication:
- Both arms refused every unsupported premise and kept authorized work going.
- Truth-first answers state more often what wasn't checked or dispatched.
- Blinded human adjudication is still to do.
Takeaway: on this fixture, Claude handles the premises carefully at baseline without a reviewer call. A Claude write-up shouldn't promise a large truth-first gain here. Instead it should:
- report the reviewer cost Claude avoids;
- add harder episodes, with ambiguous evidence or claims that would trigger an action, where review should matter.
Projected cost (Claude API rates, plus about 50% for retries)
| Campaign | Sonnet 5.5 | Opus 5.5 |
|---|---|---|
| Paired calibration (16) | ~$2–4 | ~$4–8 |
| Full plan (20 episodes × 3 arms) | ~$8–15 | ~$16–30 |
Through Copilot, runs use premium requests instead. Phase B adds Claude Code's own system prompt when using the claude_code preset, so measure that in its pilot.
Scope
This is a prompt-behavior evaluation on a synthetic fixture, not a coding benchmark. Pair it with a separate coding benchmark, for example a SWE-bench Verified subset comparing Claude Code alone with Claude Code + Squad.
Tasks
- Land
squad/claude-ab-pilot(or rebase it onto the harness branch once that is ondev) - Blinded adjudication of the Sonnet 5.5 paired calibration
- Harder fixture episodes where review should change the outcome
- Extract
HostDriver; prove the Copilot driver unchanged - Claude Agent SDK driver (
--host claude): pilot, then paired calibration - Optional
truth-first-nativearm - Publish the write-up: per-family tables, tokens/cost/time, manifests, raw JSONL, and a one-command rerun
- Lenguaje dominante
- TypeScript
- Estrellas
- 3.4k
- Forks
- 516
- Merge medio
- 1 d 15 h
- PR fusionados (30 d)
- 116
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de github/squad
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
Todos los issues de github/squad
Issues similares
-
bot:ai-assisted component:platform-js status:untriaged
Dificultad 1/5 Menos de una hora Aptitud para principiantes 74/100
midnightntwrk/platform-js#38 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
ranxianglei/billion-context#7068 ·
Los mantenedores suelen responder en 1 día
-
vendor: bump whisper.cpp past 6a8addd — the current pin aborts the app on a failed Metal initAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
mybigday/whisper.rn#348 ·
-
enhancement severity:low
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Battle-Cattle/BCUK-Bot-4#1075 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
ilan-pinto/roaring-lions#1552 ·
Los mantenedores suelen responder en 1 día