LoopX · Blog

Engineering the long run.

Design, engineering, and field notes on long-horizon agents.

Context delivery · Mechanisms and examples

· Updated November 3

An Agent needs a way to look things up, too

One voice task explains JSON Pointers, batched selection, index depth, complete requirements, exact sharing and compaction-cycle deltas, paired with ANN 18h (7,159 vs 5,753 QPS) layered byte/token ablations and early-window/cross-task counterexamples.

Read article

Research notes · EdgeBench and LHTB

EdgeBench / LHTB: notes from historical runs

Exploratory notes by songoow on historical, partly interrupted EdgeBench/LHTB runs. The feedback-first option is withdrawn; these are not official LoopX results or current capability claims.

Read the article

LoopX 2.0 · Engineering

LoopX 2.0: Two Months of TypeScript Control-Plane Engineering

From an incremental migration proposal to complete transactions, shared authority, semantic checks, and retirement of old paths. How real callers and counterexamples changed the design.

Read article

Agentic Software · Development

Agentic Software: Infrastructure for Long-Horizon Development

Using LoopX to explore infrastructure for agentic software: preserve goals, evidence, and human feedback across sessions, and carry exploration into verifiable delivery.

Read article

Research notes · EdgeBench

· Revised November 3

What does an agent achieve with ten more hours?

Follow the research from early October to early November: reliable feedback, goals, experiment size and recovery, tested across New Foundations Consistency’s 18h plateau breakthrough, Schema’s plateau counterexample and five-arm causal attribution.

Read article

Design perspective · Self-improvement

General long-horizon capability is a prerequisite for RSI

From its first Meta Goal to Personal Workspace: four months of bootstrapping, 6,848 non-merge commits, and a case for making improvements compound across rounds.

Read the article

Postmortem · Field notes

Five freshness incidents in 47 days: a LoopX postmortem

Our own advisory agent answered from stale, partial, or unread sources five times while every health signal stayed green. What failed, why local fixes were not enough, and the contract that makes the gap visible.

Read the article

Scenarios · Practice and research

Where LoopX fits: complex tasks, open-ended exploration, and continuous delivery

See how goals, evidence, and delivery responsibility work across three scenarios, alongside signals from SWE-Marathon, DeepSWE × Sol, and V4 Flash max.

Read the article

Agent-native Kanban · Long-running collaboration

LoopX: Native Kanban for long-running agents

Four diagrams explain Goals, Todos, claims, leases, gates, evidence, and shared authority state—and how they support long-running collaboration.

Read the article

Architecture · Design notes

From one-shot agents to long-horizon control

How LoopX uses goals, a state kernel, and Effect Programs to carry work across sessions, preserve human judgment, and recover from interruptions.

Read the article

Community reading

从上下文窗口到控制平面:长周期 AI Agent 如何实现可持续、可治理与可恢复运行

By 张彦峰ZYF · Original Chinese article on CSDN · CC BY-SA 4.0.

A community perspective on coordinating long-running agents through goals, evidence, human decisions, and recovery. Its bounded verified transitions (BVT) and proposed metrics are the author's design suggestions; assess current LoopX behavior against the Developer Book and implementation evidence.

The article cites ArshTechPro's introduction to LoopX among its sources. This reading entry links to the author's original text.

Read the original on CSDN
Start using LoopXOpen the Developer Book →