[rig-summarizer] Daily file summary — 2026-10-21
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
- 1/100
- Tipo de issue
- Documentación
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- documentation
Línea de trabajo
The issue contains generated daily summaries of Rig files but does not request a change. Start by reading the listed files under .agents/skills/rig/ and .github/fixtures/ to understand the project; there is no stated outcome or completion check.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Global Summary
Rig is a minimal TypeScript agent harness. The core runtime (rig.ts) provides typed schemas, prompt intents, workflows and a Copilot SDK engine. Alternative engines (Anthropic, Codex, DeepSeek, Gemini, Pi) share lifecycle helpers. A launch tool, CI drivers and fixtures (three-judge provider tests) plus integration tests exercise it.
Individual File Summaries
| File | Summary |
|---|---|
| ./.agents/skills/rig/engines/anthropic.ts | Engine adapter running Rig agents on the Anthropic SDK, with tool and JSON-schema output support. |
| ./.agents/skills/rig/engines/codex.ts | Engine adapter running Rig agents through the OpenAI Codex SDK threads. |
| ./.agents/skills/rig/engines/deepseek.ts | Engine adapter running Rig agents on the DeepSeek harness SDK. |
| ./.agents/skills/rig/engines/gemini.ts | Engine adapter that spawns the Gemini CLI process and parses its JSON output. |
| ./.agents/skills/rig/engines/pi.ts | Engine adapter built on the Pi agent core, mapping Rig tools to Pi tools. |
| ./.agents/skills/rig/engines/utils.ts | Shared engine helpers: agent turn lifecycle (abort, no concurrent turns) and tool schema/result utilities. |
| ./.agents/skills/rig/globals.ts | Ambient workflow helpers (call, pipeline, parallel) delegating to the active workflow run. |
| ./.agents/skills/rig/launch-tool.ts | Creates a Copilot SDK tool that launches a Rig program via the launcher with a timeout. |
| ./.agents/skills/rig/rig.ts | Core runtime: schemas, prompt intents, addons, workflows, Copilot SDK engine and launcher CLI. |
| ./.agents/skills/rig/run.ts | Entry point that runs the installed skill's launcher CLI. |
| ./.github/drivers/codex-fixture-mcp.ts | Codex driver exposing the three-judge fixture launcher over an MCP HTTP server. |
| ./.github/drivers/copilot-sdk-driver.ts | Copilot SDK driver wiring the Rig launch tool into gh-aw runs. |
| ./.github/drivers/pi-rig-extension.ts | Pi extension tool that runs the three-judge fixture and validates its output. |
| ./.github/fixtures/assert-three-judges.ts | Assertions validating three-judge fixture results per engine. |
| ./.github/fixtures/pi-gateway.ts | Loads and builds the Pi aw-gateway provider models from harness config. |
| ./.github/fixtures/provider-fixture.ts | Selects and configures the provider engine (codex, deepseek, gemini, pi) for the three-judge fixture. |
| ./.github/fixtures/provider-three-judges.ts | Default-exports the provider-based three-judge fixture. |
| ./.github/fixtures/three-judges.ts | Defines three-judge workflow evaluating a dummy request on clarity, safety and feasibility. |
| ./scripts/haiku.integration.test.ts | Integration tests running haiku, sonnet and complex samples through the launcher when credentials exist. |
| ./scripts/rig-launch-tool.integration.test.ts | Live integration test running the three-judge fixture via the harness-owned launch tool. |
Generated by Daily Rig File Summarizer · copilot · auto · 14.5 AIC · ⌖ 0.515 AIC · ⊞ 7.6K · ◷
- expires on Oct 28, 2026, 2:36 PM UTC
- Lenguaje dominante
- TypeScript
- Estrellas
- 14
- Forks
- 0
- Merge medio
- 9 h 27 min
- PR fusionados (30 d)
- 34
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
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 githubnext/rig
-
agentic-workflows
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
githubnext/rig#713 ·
Los mantenedores suelen responder en 1 día
-
ai-agent automation
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
githubnext/rig#712 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 4/5 1-2 días Aptitud para principiantes 35/100
githubnext/rig#711 ·
Los mantenedores suelen responder en 1 día
-
agentic-workflows
Dificultad 4/5 1-2 días Aptitud para principiantes 35/100
githubnext/rig#710 ·
Los mantenedores suelen responder en 1 día
-
ai-agent automation
Dificultad 5/5 Más de una semana Aptitud para principiantes 1/100
githubnext/rig#709 ·
Los mantenedores suelen responder en 1 día
Todos los issues de githubnext/rig
Issues similares
-
[Bug]: REST API URL starting with "http" but no scheme (e.g. httpbin.org/get) is not given an http:// prefixPosiblemente ocupada @ItsDeadlyProgrammer la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
appsmithorg/appsmith#42471 · 1 comentario ·
Los mantenedores suelen responder en 2 días
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
ehmpathy/rhachet-roles-bhrain#705 ·
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
-
Status: Triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
mermaid-js/mermaid#8546 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
braintrustdata/braintrust-sdk-javascript#2659 ·
Los mantenedores suelen responder en 1 día