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 · 简体中文

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.

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

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.

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:

objective / issue / project
   │
   ▼
LoopX state: objective + gates + todos + scope + evidence + quota
   │
   ├─ human judgment needed? ── yes ─▶ ask a concrete question and wait
   │
   ├─ safe fallback available? ──────▶ run one bounded agent slice
   │
   ▼
Codex / Claude Code / Cursor / shell agent executes one turn
   │
   ▼
write evidence + handoff + next todo ─▶ quota decides the next tick

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 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.

LoopX is useful when you run:

• multi-day engineering, research, benchmark, or experiment objectives;
• issue and PR loops that must preserve scope, evidence, and review state;
• recurring heartbeat or monitor work;
• projects with owner, safety, publication, or private-data gates;
• peer-agent teams where ownership, leases, and handoff matter;
• creator, research, or operations workflows whose progress must remain legible to a non-engineering operator.

LoopX is not an autonomous production controller. Dangerous permissions, publishing, production writes, and final ownership stay with the human.

Personal Agents, Teams, and Self-Improving Workflows

Meta Muse and Grok Bot make persistent personal agents and delegated work a familiar product idea. LoopX approaches that space as an open, provider-neutral control plane for agents you already run—not as a hosted replacement for either product.

• Personal agent: use the shipped Workspace and connected Lark surfaces to inspect goals, steer work and resolve decisions. The persistent steward and semantic handoff RFC extends this toward one capable front door for a team; the complete journey remains under qualification.
• Agent team: share goals without erasing worker ownership. Claims, evidence and explicit returns keep implementation and review connected. See the three-agent collaboration demo for a bounded example, including corrections and two review rounds.
• Self-improving workflows: connect feedback to the next attempt through Reward Memory, and evaluate candidate changes through Explore. Both are optional. The link to recursive self-improvement (RSI) is the engineering loop—propose, test, review, retain—not a claim that LoopX has demonstrated autonomous model improvement or compounding capability gains.

A personal steward is an interaction role, not a second source of authority. Background execution still needs an available host and configured runtime. The overall roadmap separates shipped foundations from the next end-to-end acceptance milestones.

Evidence

LHTB: Higher Mean Reward With the Same Model

LoopX 1.0.3 Heartbeat reaches 0.4948 mean reward across 46 matched tasks: +17.3% over Plain Codex and +10.6% over native Codex Goal. All three use GPT-5.6 Sol, max reasoning effort, and disabled Web Search. Long-Horizon Terminal-Bench goes beyond coding: these tasks span research reproduction, scientific simulation, multimodal analysis, professional workflows, games, and systems work.

The ≥0.80 threshold is a supplementary, post-hoc view; ≥0.95 remains the