huangruiteng/loopx

Long-horizon agent control plane for durable, governed work across Codex, Claude Code, and other harnesses.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 49 minutes ago
Added to GitGenius on August 11th, 2026
Created on May 31st, 2026
Open Issues & Pull Requests: 30 (-1)
GitHub issues: Enabled
Number of forks: 419
Total Stargazers: 4,811 (+1)
Total Subscribers: 14 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.1 hours
Mean response time: 7.4 hours
90th percentile: 19.1 hours
Tracked items: 68

How this project is maintained

Around half of the issues opened in the past year never receive a reply. Only 17% of issues opened in the past year have been closed. Three people close 98% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 17
New in 7 days: 36
Closed in 7 days: 27
Avg open age: 7 days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 36
Closed in 7 days: 26
Comments in 7 days: 25
Events in 7 days: 90

Top labels

  • triage (13)
  • enhancement (8)
  • bug (4)
  • capability-extension (2)
  • control-plane (2)
  • workflow-audit (1)

Detailed Description

LoopX is a lightweight state kernel and control plane for governing long-running AI agent teams.

The problem LoopX solves is that long-running agent work requires durable state management across multiple turns, tool invocations, and agent handoffs—beyond what chat memory and timers can provide. Objectives change, decisions must be made by humans, evidence becomes stale, and schedulers risk spending quota without progress. LoopX keeps this control state in a compact, local-first layer that remains agent-runtime agnostic. It works by maintaining durable goals, executable todos, evidence logs, quota awareness, and verifiable handoffs while the actual work executes in any coding agent runtime such as Codex, Claude Code, or Cursor. The tool validates state transitions through operators like claim, gate, monitor, and writeback, functioning as an agent-native Kanban board where registered agents act as peers without requiring a durable leader identity.

LoopX suits teams running long-running discovery, research, engineering, or operations loops where work spans multiple sessions and agent handoffs. It is designed for projects where human judgment must remain in the loop and work must be reviewable and restartable. The tool is provider-neutral and does not replace the agent runtime; it governs the state layer that lets work continue across runs. Choose it if you need to keep objectives stable, track evidence, manage quota spending, and hand work between agents without losing context or control.

The maintainers respond to new issues and pull requests within a day. Work in the issue tracker centers on enhancement requests and workflow-audit concerns.