loopx-project/loopx

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

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 1 hour ago
Added to GitGenius on September 19th, 2026
Created on May 31st, 2026
Open Issues & Pull Requests: 109 (+0)
GitHub issues: Enabled
Number of forks: 561
Total Stargazers: 5,906 (+1)
Total Subscribers: 28 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 60
New in 7 days: 45
Closed in 7 days: 30
Avg open age: 21 days
Stale 30+ days: 12
Stale 90+ days: 0

Recent activity

Opened in 7 days: 30
Closed in 7 days: 24
Comments in 7 days: 2
Events in 7 days: 11

Top labels

  • triage (40)
  • bug (23)
  • enhancement (22)
  • control-plane (15)
  • direction/architecture-evolution (9)
  • direction/operator-surface-im (5)
  • capability-extension (4)
  • direction/shared-coordination (4)

Detailed Description

LoopX is a control plane for long-horizon AI agents that runs on top of existing agent harnesses like Codex, Claude Code, and Cursor.

The problem LoopX solves is that long-running agentic work loses state, governance, and human oversight across multiple turns and tool switches. Traditional agent harnesses execute bounded tasks but lack the infrastructure to preserve objectives, gates, evidence, quotas, and handoffs across extended workflows. LoopX provides a lightweight, local-first state kernel that sits above these harnesses, maintaining durable control state while the harness executes individual work units. This separation of concerns lets the harness focus on bounded execution while LoopX handles semantic decisions about what happens next, recovery, and human-agent collaboration.

LoopX suits teams building long-horizon workflows where work spans multiple agent sessions, tools, or days. It is particularly valuable when you need to preserve and inspect the reasoning trail, restart interrupted work, hand off between different agent harnesses, or maintain human oversight over autonomous decisions. The tool is provider-neutral, meaning it works across different agent implementations rather than locking you into a single vendor. If you are working with short, isolated tasks that complete in a single session, the overhead of a control plane may not be justified. The project emphasizes local-first operation and human judgment, positioning itself for scenarios where auditability and human-in-the-loop governance matter more than pure speed.

The project maintains active development with regular updates to both the core control plane and the Personal Workspace interface. Documentation is comprehensive, spanning a developer book, getting-started guides, and full API reference materials. The codebase shows ongoing refinement of state management, workspace features, and integration patterns with multiple agent harnesses. Community engagement appears steady through the public website, blog, and bilingual documentation supporting both English and Chinese-speaking developers.