loopx-project/loopx
Turn long-horizon goals into verifiable results. A local-first semantic control plane and research workbench for long-running agent teams, across sessions and runtimes.
Build with Backblaze B2
SDKs, agent skills, IDE extensions, and reference pipelines from Backblaze Labs. All open source.
Loading star history...
Where it stands
Rank, growth pace and release cadence relative to everything GStars tracks.
5 releases in the last 90 days, the latest 4 days ago, with 116 contributors on GitHub.
Peaked at #100 in the weekly ranking the week of Aug 16, its best in the past year.
Use Cases & Benefits
- Provides a local control plane with a durable state kernel to manage long-running AI agent tasks and multi-agent workflows.
- Ensures stable, reviewable, and restartable long-horizon agent work with explicit human judgment gates and evidence-backed handoffs.
- Use for coordinating multi-day engineering or research projects requiring persistent task state and peer agent collaboration.
- Use for managing issue and pull request loops that preserve scope, evidence, and review state across sessions.
- Use for automating recurring monitoring or heartbeat workflows with quota-aware scheduling and safe fallback mechanisms.
Should you depend on it?
License terms, project hygiene and risks, from GitHub metadata and GStars' snapshots.
License
Apache 2.0
Permissive: commercial use, modification and redistribution are allowed with attribution; includes an explicit patent grant from contributors.
Community files
- README: present
- Contributing guide: present
- Code of conduct: present
Watch-outs
No watch-outs from GStars' checks.
General guidance from repository metadata, not legal advice. How we score
From the README
The local control plane for long-running AI agent work.
Keep objectives, gates, todos, evidence, quota, and handoffs stable while Codex, Claude Code, Cursor, or your own runtime executes bounded turns.
把会干活的 Agent，接成可管理、可复盘、可持续改进的数字员工。
A lightweight state kernel and agent-agnostic local control plane for loop engineering, LoopX keeps long-running work reviewable, restartable, and easier to hand off across turns, tools, and agents. It does not replace your agent runtime.
Loop engineering for long-running AI agents and peer agent teams.
Keep the loop moving. Keep the judgment human.
An agent can finish a task in one session. Long-running work is harder: objectives change, owner decisions appear, evidence goes stale, agents hand work to peers, and a scheduler can keep spending after no useful transition remains. Chat memory and a timer are not enough to govern that.
LoopX keeps the durable control state in one compact layer:
A useful mental model is an agent-native Kanban for long-running work. Cards carry identity, authority, evidence, and continuation. Moves are validated operators such as claim, gate, monitor, and writeback. The board is a projection; LoopX state remains the source of truth.
Registered agents are peers. Claims, leases, task boundaries, capabilities, and typed continuation decide who acts next; no durable leader identity is required.
Daily snapshots
Stars gained per day, and how forks and open issues moved, from GStars' daily snapshots
+4,573 stars over 90 days across 22 snapshot days; best day +725 on Aug 7.
Forks
619+469
Open issues
195+172
Compared with peers in AI Agents
Fastest-growing repositories GStars tracks in this cohort for the week of Nov 1, by 7-day star growth
| Repository | Stars | +7d | Health | Last release |
|---|---|---|---|---|
| vercel-labs/agent-desktop | 17.0K | +13.3K | 33 | today |
| thedotmack/claude-mem | 113.6K | +8.8K | 35 | today |
| stablyai/orca | 116.8K | +6.6K | 40 | today |
| milind-soni/OpenMausBot | 13.5K | +6.0K | 45 | today |
| HKUDS/DeepTutor | 55.5K | +5.5K | 65 | 5 days ago |
| loopx-project/loopx | 6.5K | — | 65 | 4 days ago |
| Category median | 55.5K | +6.6K | 40 | — |
Discover Repositories
Search across tracked repositories by name or description