jlapenna/agent-lcars
Developer toolsこのページは AI により自動翻訳されています。技術的な詳細は原文をご確認ください。 原文を見る
LCARS operations console and agent telemetry pipeline
概要
Agent LCARS is the control plane for headless Claude Code, Codex, and OpenCode work on the shared self-hosted GitHub Actions runner fleet. It turns GitHub issues into accountable agent work, shows maintainers where attention is needed, and retains the session evidence behind each outcome. To dispatch work, add exactly one routing label to an issue in an onboarded repository: The shared agent protocol is the complete behavioral contract for every dispatched run. The LCARS skill is a situational control-plane reference for developers changing dispatch and reconciliation machinery. The console then tracks the run from intake through review, merge, and any maintainer follow-up. See Operations for Work API access and parked-item cleanup. Use the console for decisions and inspection; use the supporting services when working on a specific part of the fleet. The console keeps the active fleet, its decision queue, and its session history in focused workspaces.
README
以下は原文 README の抜粋です。原文を見る。
Agent LCARS
Agent LCARS is the control plane for headless Claude Code, Codex, and OpenCode work on the shared self-hosted GitHub Actions runner fleet. It turns GitHub issues into accountable agent work, shows maintainers where attention is needed, and retains the session evidence behind each outcome.
Dispatch
To dispatch work, add exactly one routing label to an issue in an onboarded repository:
| Label | Agent |
|---|---|
agent:claude |
Claude Code |
agent:codex |
Codex |
agent:opencode |
OpenCode |
The shared agent protocol is the complete behavioral contract for every dispatched run. The LCARS skill is a situational control-plane reference for developers changing dispatch and reconciliation machinery. The console then tracks the run from intake through review, merge, and any maintainer follow-up.
Operating surfaces
See Operations for Work API access and parked-item cleanup.
Use the console for decisions and inspection; use the supporting services when working on a specific part of the fleet.
| Surface | Use |
|---|---|
Console queue (/) |
Work requiring a maintainer action |
Console agents (/agents) |
Active runs, CLI sessions, and recent outcomes |
Console sessions (/sessions) |
Search and inspect session records |
apps/telemetry-watcher |
Interactive and CI session telemetry |
apps/runner-autoscaler |
Runner placement and lifecycle |
apps/github-actions-exporter |
GitHub Actions metrics |
infra/terraform |
GCP services, IAM, storage, secrets, and budget |
Console views
The console keeps the active fleet, its decision queue, and its session history in focused workspaces. The Decision Inbox is the starting point for work that needs a human response; Agents is the live operational view; and the Session Archive is the durable record for investigation and audit.
Active agents
Session archive
Documentation map
The full task-oriented index is docs/README.md, and
ARCHITECTURE.md maps system ownership and proof
boundaries. Common entry points:
| Need | Source of truth |
推奨ツール
別のキーワードを試すか、フィルタを外してください。
インストール
npx skillfish add jlapenna/agent-lcars