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
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 2/5
- Tiempo estimado
- 1-3 horas
- Aptitud para principiantes
- 78/100
Línea de trabajo
Lee .github/workflows/update-astro.md, changeset.md y sighthound-security-scan.md; después ejecuta gh aw compile update-astro changeset sighthound-security-scan para comprobar la configuración del workflow. Añade enrutamiento Economy basado en el coste a cada workflow y concede copilot-requests: write en los dos archivos que lo necesitan. La tarea estará terminada cuando la compilación se complete sin nuevas advertencias, las primeras ejecuciones enrutadas usen los modelos Luna esperados y cuesten menos, y los PR de Update Astro sigan superando la compilación de la documentación.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Go
- Estrellas
- 5.6k
- Forks
- 615
- Merge medio
- 5 h 36 min
- PR fusionados (30 d)
- 805
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Incluye un Dockerfile o un archivo de Docker Compose
- Sin 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/gh-aw
-
agentic-workflows
Dificultad 1/5 Menos de una hora Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 1/5 Menos de una hora Aptitud para principiantes 65/100
Los mantenedores suelen responder en 1 día
-
automation cli cookie documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
automation cookie documentation
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
automation observability optimization traces
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
Los mantenedores suelen responder en 1 día
Todos los issues de github/gh-aw
Issues similares
-
Query cache: a failed cache page read leaves the set request's read lock held, so the scan hangsAbierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
turbot/steampipe-plugin-sdk#986 · 1 comentario ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
router-for-me/CLIProxyAPI#7307 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
betterleaks/betterleaks#460 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
openmcp-project/service-provider-crossplane#330 ·
Los mantenedores suelen responder en 1 día