[rig-summarizer] Daily file summary — 2026-10-25
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 1/5
- Geschätzter Aufwand
- Unter einer Stunde
- Anfängerfreundlichkeit
- 10/100
- Issue-Typ
- Dokumentation
- Klarheit
- Muss geklärt werden
- Aktivitätsstatus
- Aktiv
- Tech-Stack
- github-actions, typescript
- Bereich
- ai-infra-agents, tooling
Rechercherichtung
The issue summarizes Rig files but does not request a change or define a completion condition. Read the listed files only if this summary is part of a concrete follow-up; no implementation task is specified here.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Global Summary
The first 20 TypeScript files in the repo (sorted by path) cover the Rig harness: per-provider engine adapters (Anthropic, Codex, DeepSeek, Gemini, Pi) with shared lifecycle utilities, the core runtime (rig.ts), ambient workflow globals, a launcher tool and CLI entry, CI drivers and fixtures for a three-judge provider integration test, and integration tests that run samples and the launch tool through the Copilot SDK. Summaries were derived from reading each file's header and imports, not from a full read.
Individual File Summaries
| File | Summary |
|---|---|
| ./.agents/skills/rig/engines/anthropic.ts | Anthropic engine adapter that builds Rig agents on the Anthropic SDK with beta JSON-schema output and tool helpers. |
| ./.agents/skills/rig/engines/codex.ts | Codex engine adapter built on @openai/codex-sdk, with configurable thread options and response-schema normalization. |
| ./.agents/skills/rig/engines/deepseek.ts | DeepSeek engine adapter that runs agents via the DeepSeek harness SDK client. |
| ./.agents/skills/rig/engines/gemini.ts | Gemini engine adapter that spawns the Gemini CLI as a child process, with configurable command, args, env and approval mode. |
| ./.agents/skills/rig/engines/pi.ts | Pi engine adapter that wraps the Pi agent core and its built-in model catalog as a Rig agent factory. |
| ./.agents/skills/rig/engines/utils.ts | Shared engine helpers: an agentLifecycle that enforces single-turn concurrency and abort handling, plus 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 using a runtime URI and connection token. |
| ./.agents/skills/rig/rig.ts | Core Rig runtime: typed schemas, prompt intents, addons, workflows, the Copilot SDK engine and the launcher CLI. |
| ./.agents/skills/rig/run.ts | Entry point that lazily imports rig.ts and runs the launcher CLI when executed directly. |
| ./.github/drivers/codex-fixture-mcp.ts | Driver exposing the three-judge integration fixture to Codex as a once-only launcher served over MCP/HTTP. |
| ./.github/drivers/copilot-sdk-driver.ts | CI driver that runs the Copilot SDK with a Rig launch tool, configured from required environment variables. |
| ./.github/drivers/pi-rig-extension.ts | Pi extension that defines a no-parameter Rig tool running the three-judge fixture and validating its output. |
| ./.github/fixtures/assert-three-judges.ts | Assertions validating the three-judge result object (engine, model, and per-criterion judgments). |
| ./.github/fixtures/pi-gateway.ts | Parses a gateway config and builds Pi models/providers for OpenAI-compatible completions and responses APIs. |
| ./.github/fixtures/provider-fixture.ts | Builds the provider fixture by selecting the Codex, DeepSeek, Gemini or Pi engine from required environment variables. |
| ./.github/fixtures/provider-three-judges.ts | Default-exports the provider fixture for the three-judge test. |
| ./.github/fixtures/three-judges.ts | Defines the three-judge workflow (clarity, safety, feasibility) over a dummy request using a configurable engine factory. |
| ./scripts/haiku.integration.test.ts | Vitest integration test running the haiku, sonnet and complex samples, skipped unless a Copilot token or SDK URI is set. |
| ./scripts/rig-launch-tool.integration.test.ts | Live vitest integration test running the three-judge fixture through a harness-owned launch tool without credential env vars. |
Generated by Daily Rig File Summarizer · copilot · auto · ~14 AIC · ⌖ ~1 AIC · ⊞ 3.9K · ◷
- expires on Nov 1, 2026, 2:32 PM UTC
- Vorherrschende Sprache
- TypeScript
- Sterne
- 14
- Forks
- 0
- Ø Merge
- 9 Std. 27 Min.
- Gemergte PRs (30 T.)
- 34
Entwicklungsumgebung
Dieses Projekt bietet weder Dev-Container noch Dockerfile noch Beitragsleitfaden – die Einrichtung liegt bei Ihnen. Beginnen Sie mit der README; die allgemeinen Schritte stehen in unserem Leitfaden für den ersten Beitrag.
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus githubnext/rig
-
agentic-workflows
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 12/100
githubnext/rig#738 ·
Maintainer antworten meist innerhalb von 1 Tag
-
ai-agent automation
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 42/100
githubnext/rig#737 ·
Maintainer antworten meist innerhalb von 1 Tag
-
agentic-workflows
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 22/100
githubnext/rig#736 ·
Maintainer antworten meist innerhalb von 1 Tag
-
ai-agent automation
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 18/100
githubnext/rig#735 ·
Maintainer antworten meist innerhalb von 1 Tag
-
ai-agent automation
Schwierigkeit 4/5 3-5 Tage Anfängerfreundlichkeit 12/100
githubnext/rig#733 ·
Maintainer antworten meist innerhalb von 1 Tag
Ähnliche Issues
-
[Bug]: Payment providers removed from config are never disabled in payment_providerEvtl. vergeben @medusa-os-bot hat das heute übernommen. Offentype: bug
Schwierigkeit 2/5 Ein halber Tag Anfängerfreundlichkeit 82/100
medusajs/medusa#17544 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100
software-mansion/argent#1651 ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
Maintainer antworten meist innerhalb von 1 Tag
-
lane:reliability
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
Maintainer antworten meist innerhalb von 1 Tag
-
needs-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
Maintainer antworten meist innerhalb von 1 Tag