loopx-project/loopx

**Give your agents a goal. Keep the work moving.**
The open, local-first control plane for long-horizon agents and personal agent teams.
Keep goals, decisions and evidence across sessions. Work with Codex, Claude Code, DeepSeek Harness and other supported runtimes.
Get started · Workspace · LHTB results · Docs · 简体中文
Source-built App on an authored Workspace stories replay ; no live Agent execution · watch the 32-second walkthrough
**Start in Codex App in two steps.** Install once:
Restart Codex App, then type this in a thread opened on your project:
LoopX connects the project, plans the work as Todos and sets up the heartbeat that keeps it moving. Claude Code uses /loopx <complex task> · other Agent hosts
**LHTB · 46 tasks · GPT-5.6 Sol:** LoopX 1.0.3 Heartbeat reaches **0.4948 mean reward** — **+17.3% vs Plain Codex**, **+10.6% vs native Codex Goal**.
Results and pass rates ↓
---
**More verified work. Less human attention.** LoopX gives agents durable goals,
bounded continuation, peer ownership and recoverable handoffs. Your runtime
provides the model and tools; LoopX keeps track of what to do next, what is
accepted, and when to ask you.
| What you want to do | Start here |
| --- | --- |
| Keep a coding or research agent working across sessions | Install and start |
| Manage personal projects, schedules and decisions in one place | Personal Agent Workspace |
| Let agents collaborate and deliver verifiable results | Agent collaboration guide |
Meet the Personal Agent Workspace
Keep long-horizon goals in one local-first workspace. Goals, attention,
conversations, tasks, files, schedules, and recovery stay durable across days,
restarts, and harnesses. Reopen a project, inspect the previous turn’s state
and evidence, and continue the next permitted action.
LoopX 1.0 brings these long-horizon control states into the Personal Workspace. It gives you one place to:
- see what needs you, what is running, what is being watched, and what is
scheduled or stopped;
- configure Goal capabilities, distinguish machine defaults from Goal overrides,
and preview changes before applying them;
- steer a live turn, queue a message, or use the async inbox from a connected
Lark conversation with explicit Goal/Agent/session routing;
- inspect deliverable files, periodic reports, and their supporting evidence;
- continue across Codex, Claude Code, direct-model, and other registered Agent
sessions without losing Goal state or evidence;
- review protected changes through typed preview, explicit confirmation, and
receipts while LoopX state—not the browser—remains authoritative.
For Manager group conversations, LoopX keeps message visibility separate from
Turn authority; see the bilingual Lark Manager context and authority
contract.
loopx dashboard is the supported browser/PWA launch path. You can also download
native desktop previews from the 1.0 release;
they reuse the same loopback services and Goal state. Apple Silicon macOS supports
signed App updates that pair the shell with its bundled runtime, plus repair and
recovery. Python 3.11+ is required; the App is ad-hoc signed, not notarized.
Windows preview installers currently use manual updates and a separately installed CLI.
Desktop installation, updates, and source development.
Capability settings and reproducible workspace scenarios
From a source checkout, run python -m demo.workspace serve to explore a community
event, a home-energy comparison, and a neighborhood website release. Each has four
work roles, 18 tasks, two decisions, and two watches. The screenshot above comes
from this reproducible workspace. Scenarios and replay instructions.
Watch the full 32-second walkthrough
· Read the workspace guide
· Try the five-minute tour
Why LoopX
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:
Agent runtimes execute the work. LoopX governs the state that lets engineering,
research, discovery, and operations loops continue across runs. It is not
another agent framework or a provider-specific orchestration runtime.
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