loopx
LoopX is a local-first semantic control plane and research workbench for long-running agent teams. Its premise is that a single session can finish a task, but long work breaks down when objectives change, owner decisions appear, evidence goes stale and agents hand work to peers. LoopX keeps the goal, accepted requirements, decisions, ownership and evidence durable across sessions, restarts and runtimes; your agent host supplies the model and tools.
The README describes it as an agent-native Kanban for long-running work: cards carry identity, authority, evidence and continuation, and moves are validated operators such as claim, gate, monitor and writeback. Registered agents are peers coordinated by claims, leases and typed continuation rather than a fixed leader. It is pitched at multi-day engineering, research and benchmark objectives, PR loops that must preserve scope and review state, and heartbeat or monitor work. It is explicitly not an autonomous production controller: dangerous permissions and publishing stay with the human.
Install with pip install loopx and loopx workflow-skills --install, then call $loopx in Codex or /loopx in Claude Code; Python 3.11+ and Node.js 22.22.3+ are required. The project published a 46-task study on Long-Horizon Terminal-Bench in which LoopX Heartbeat reached a higher mean reward than plain Codex and native Codex Goal with the same model, and the README spells out the study's limits. Apache-2.0 licensed.
Features
Why choose it
Trade-offs
Maintenance check
- Last commit
- 2026-10-26
- Commits, last 90 days
- 100+
- Releases, last 90 days
- 30
- Latest release
- desktop-main-40414081337-1 (2026-10-26)
- Open issues
- 175
- Recent issues with at least one comment
- 2/11
Oldest week on the left; the latest four weeks are orange. Source: GitHub commit activity.
Status rule: archived on GitHub = Archived; last commit within 90 days = Active; 91 to 365 days = Slowing; older = Stale. All figures come from the GitHub API on the date shown.
Most discussed open issues
- #4447 [Task]: Semantic vocabulary convergence follow-ups after RFC PR #4433 / 语义词表收敛后续任务14 comments · 2026-09-15
- #4069 Scoped review invitations and module stewardship12 comments · 2026-09-07
- #5136 [Architecture]: two modules both claim to own "private-looking text"11 comments · 2026-09-26
- #5685 [Bug]: the pinned top-level module budget is already exceeded on main (150 measured against 147)9 comments · 2026-10-05
- #4339 Help wanted: capable manager & semantic handoff / 强能力管家与语义交接(RFC #4330)9 comments · 2026-09-13
Issue titles are quoted from GitHub. Open the link to check whether a problem still applies to the version you use.
Compatibility
Quick start
Use cases
Alternatives
Comments
No comments yet. Be the first!