Model routing: route Update Astro, Changeset Generator and Sighthound Security Scan (Codex on Copilot) instead of pinning GPT-5.6 Sol and GPT-6 Sol
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 78/100
Direzione di ricerca
Leggi .github/workflows/update-astro.md, changeset.md e sighthound-security-scan.md, poi esegui gh aw compile update-astro changeset sighthound-security-scan per verificare la configurazione del workflow. Aggiungi il routing Economy basato sui costi a ogni workflow e concedi copilot-requests: write nei due file che ne hanno bisogno. Il lavoro è completato quando la compilazione riesce senza nuovi avvisi, le prime esecuzioni instradate usano i modelli Luna previsti e costano meno, mentre le PR di Update Astro continuano a superare la build della documentazione.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Estimated saving: about 450-650 AIC/week. These three Codex workflows already use the Copilot provider but pin a large GPT model. Route them with economy, like Auto-Triage Issues, Ponytail Reviewer and Daily Go Test Parallelizer (#74199, #74201, #74586).
| Workflow | Output | Now | Mode | Agent runs/wk | AIC/run now | Est. saving/wk |
|---|---|---|---|---|---|---|
| update-astro | PR (Astro and npm upgrade for the docs) | copilot/gpt-5.6-sol |
economy |
~2 | ~200 | 250-320 |
| changeset | changeset file pushed to the PR | copilot/gpt-5.6-sol |
economy |
3-6 | ~52 | 130-260 |
| sighthound-security-scan | issue (top Sighthound findings) | copilot/gpt-6-sol |
economy |
5 | ~17 | 50-60 |
AIC/run includes threat detection.
Why
- Codex routing on Copilot works. On AWF v0.29.6, Ponytail Reviewer succeeded on 39 of 40 runs (the one failure was a PR-branch run that never reached routing), Auto-Triage Issues 3 of 3 and Daily Go Test Parallelizer 9 of 9. None of these three workflows uses sub-agents, so the open Codex sub-agent bugs (#71157, #72094) don't apply.
- Routed runs cost much less. Auto-Triage Issues went from 79 to 20 AIC per run (GPT-6 Astra before), Ponytail Reviewer from 15 to 4 (Terra), and Daily Go Test Parallelizer, which also writes code and opens PRs, from 55 to 11-33 on
economy(Terra). Terminal Stylist went from 106 to 35 after leaving its GPT-5.6 Sol pin. economyfor all three. Update Astro's PR has to pass the docs build and is reviewed. Changeset Generator writes one small changeset file. Sighthound finds the violations itself, and the agent only runs when there are actionable findings and summarises the top ones in an issue. For this work, economy picks GPT-5.6 Luna or GPT-6 Luna (hightomax);balancedpicks the same Luna for most of these labels.- Detection gets much cheaper. Threat detection inherits today's pin: about 40 AIC per run for Update Astro, 27 for Changeset Generator (as much as its agent) and 5 for Sighthound. Without a pin it uses the
detectionmodel, about 1 AIC, as on Ponytail Reviewer and Auto-Triage Issues. - No model restrictions. Only a hard cross-system label picks
gpt-5.6-sol:max, which could cost more than today. None of the three works across systems.
Change
In .github/workflows/update-astro.md, changeset.md and sighthound-security-scan.md, delete the top-level model: line and add model-routing to the existing engine block:
engine:
id: codex
model-provider: github
model-routing:
goal: cost
mode: economy
Add copilot-requests: write to permissions in update-astro.md and changeset.md; sighthound-security-scan.md already has it. Keep the prompts, steps and safe outputs. Don't add model restrictions.
Run gh aw compile update-astro changeset sighthound-security-scan. On main (fdfc5d5a0d) these compile with no new warnings: routing is enabled with GPT candidates on Copilot, Update Astro and Changeset Generator move from the COPILOT_GITHUB_TOKEN secret to github.token, and detection uses the detection model.
Check
- Audit the first routed runs with
gh aw audit <run>: expect a Luna pick, and compare AIC per run with the table. - A
gpt-5.6-sol:maxpick means the run was labelled hard cross-system work. If Sighthound keeps getting it and costs more than about 17 AIC per run, restore itscopilot/gpt-6-solpin. - Check that Update Astro's next PRs still pass the docs build.
Estimates use gh-aw usage from 19 October to 3 November and AWF v0.29.6's routing tables; the routed cost per run is estimated from the routed workflows above.
- Lingua principale
- Go
- Stelle
- 5.6k
- Fork
- 615
- Merge medio
- 5h 19m
- PR unite (30g)
- 798
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
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 github/gh-aw
-
automated-analysis code-quality cookie enhancement report safe-outputs testing workflows
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
agent-research
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
ai-inspected community model-routing
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
I maintainer di solito rispondono entro 1 giorno
-
automation cli-tools testing
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
I maintainer di solito rispondono entro 1 giorno
-
cookie maintenance step-naming
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 74/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di github/gh-aw
Issue simili
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
TUM-Dev/Campus-Backend#678 ·
I maintainer di solito rispondono entro 1 giorno
-
fix(app): fail closed if GetGeneralSetting fails during initializationForse già presa @kalavt l’ha presa oggi. Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
tsukumogami/tsuku#2813 ·
I maintainer di solito rispondono entro 1 giorno
-
component:obi contribfest go test
Difficoltà 2/5 Meno di un'ora Idoneità per principianti 83/100
open-telemetry/opentelemetry-ebpf-instrumentation#4143 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno