[rig-summarizer] Daily file summary — 2026-10-22
Mantenedores costumam responder em até 1 dia
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 1/5
- Tempo estimado
- Menos de uma hora
- Facilidade para iniciantes
- 1/100
- Tipo de issue
- Documentação
- Clareza
- Precisa de esclarecimento
- Status de atividade
- Ativa
- Stack de tecnologia
- typescript
- Domínio
- tooling
Direção de pesquisa
This issue contains an automatically generated summary of Rig files, but does not request a change or describe any work to complete. Start by reading the linked Daily Rig File Summarizer workflow to understand why the report was posted; there is no completion condition stated in the issue.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Global Summary
The project is Rig, a TypeScript agent harness. The core runtime (rig.ts) provides schemas, prompt intents and a Copilot SDK runtime. Alongside it are pluggable provider engines (Anthropic, Codex, DeepSeek, Gemini, Pi), a launcher and launch tool, ambient workflow helpers, and CI fixtures, drivers and integration tests for a "three judges" provider check.
Individual File Summaries
| File | Summary |
|---|---|
| ./.agents/skills/rig/engines/anthropic.ts | Engine adapter that runs Rig agents on the Anthropic SDK, with tool support and structured output. |
| ./.agents/skills/rig/engines/codex.ts | Engine adapter that runs Rig agents on the OpenAI Codex SDK via threads. |
| ./.agents/skills/rig/engines/deepseek.ts | Engine adapter that runs Rig agents on the DeepSeek harness SDK. |
| ./.agents/skills/rig/engines/gemini.ts | Engine adapter that runs Rig agents by spawning the Gemini CLI as a subprocess. |
| ./.agents/skills/rig/engines/pi.ts | Engine adapter that runs Rig agents on the Pi agent-core library and its model providers. |
| ./.agents/skills/rig/engines/utils.ts | Shared engine helpers: turn lifecycle with abort and no-concurrency enforcement, tool schema and result utilities. |
| ./.agents/skills/rig/globals.ts | Ambient workflow helpers (call, pipeline, parallel) that delegate to the active workflow run. |
| ./.agents/skills/rig/launch-tool.ts | Creates a Copilot SDK tool that launches a Rig program in a subprocess with a timeout. |
| ./.agents/skills/rig/rig.ts | The ~3,400-line core runtime: schemas, prompt intents, agents, addons, workflows, the Copilot engine and the launcher CLI. |
| ./.agents/skills/rig/run.ts | Entry point that runs the installed skill's launcher CLI. |
| ./.github/drivers/codex-fixture-mcp.ts | Test driver that serves the three-judge fixture to Codex through an MCP launcher and checks the result. |
| ./.github/drivers/copilot-sdk-driver.ts | Driver that runs the Copilot SDK with the Rig launch tool for CI integration workflows. |
| ./.github/drivers/pi-rig-extension.ts | Pi extension tool that runs the three-judge fixture and validates the output. |
| ./.github/fixtures/assert-three-judges.ts | Assertions that validate three-judge fixture output for each engine, model and criterion. |
| ./.github/fixtures/pi-gateway.ts | Loads and validates the Pi aw-gateway provider configuration and builds the Pi model gateway. |
| ./.github/fixtures/provider-fixture.ts | Builds the provider-specific three-judge fixture from environment configuration. |
| ./.github/fixtures/provider-three-judges.ts | Default export of the provider fixture. |
| ./.github/fixtures/three-judges.ts | Defines the three-judge workflow (clarity, safety, feasibility) used to test engines. |
| ./scripts/haiku.integration.test.ts | Integration tests that run the haiku, sonnet and complex samples through the launcher with a real token or SDK URI. |
| ./scripts/rig-launch-tool.integration.test.ts | Opt-in live test that runs the three-judge fixture through a harness-owned launch tool. |
Note: the listing is limited to the first 20 files, and summaries were produced by inspecting file headers and sizes directly rather than by calling the sub-agent.
Generated by Daily Rig File Summarizer · copilot · auto · 13.9 AIC · ⌖ 0.518 AIC · ⊞ 3.9K · ◷
- expires on Oct 29, 2026, 2:37 PM UTC
- Linguagem predominante
- TypeScript
- Estrelas
- 14
- Forks
- 0
- Merge médio
- 9h 27min
- PRs com merge (30d)
- 34
Preparar o ambiente
Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de githubnext/rig
-
agentic-workflows
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 35/100
githubnext/rig#713 ·
Mantenedores costumam responder em até 1 dia
-
ai-agent automation
Dificuldade 4/5 3-5 dias Facilidade para iniciantes 25/100
githubnext/rig#712 ·
Mantenedores costumam responder em até 1 dia
-
agentic-workflows
Dificuldade 4/5 1-2 dias Facilidade para iniciantes 35/100
githubnext/rig#711 ·
Mantenedores costumam responder em até 1 dia
-
agentic-workflows
Dificuldade 4/5 1-2 dias Facilidade para iniciantes 35/100
githubnext/rig#710 ·
Mantenedores costumam responder em até 1 dia
-
ai-agent automation
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 1/100
githubnext/rig#709 ·
Mantenedores costumam responder em até 1 dia
Todas as issues de githubnext/rig
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
awesome-dsh-plugin/awesome-dsh-plugin#9184 ·
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 75/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 85/100
farion1231/cc-switch#8829 ·
Mantenedores costumam responder em até 1 dia
-
[core-client] Remove unused hand-maintained transport helpers after the definition-table cutoverAbertadoc-audit enhancement
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 88/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 85/100