Post

Back to deliverables

AIGCLINK

@aigclink

一款轻量级超长程Agent工具：LoopX，自主运行200+小时多轮协作，状态不漂移长程任务中常见的问题：目标漂移、人工决策点模糊、证据过期、多Agent交接混乱、调度器空转浪费资源等 LoopX把这些状态统一收敛到一个紧凑的内核层作者放了两条200+小时的真实轨迹，跨多轮执行、等待、人工决策、writeback与resume后，整个loop仍能找回目标、证据和下一步一个开源Issue修复，从提 PR 到多轮 review更新）；一个Auto ML实验，假设、证据、无效分支、promote/stop gate全在一个图里 LoopX不替代你的Agent运行时（Codex、Claude Code、Cursor该用什么用什么），而是在其上提供一层持久化的控制状态管理，负责管理跨turn的持久状态，目标、任务、证据、配额、交接 Agent每次执行一个有边界的turn，LoopX决定下一步该谁做、做什么、能不能继续 LoopX不执行工具调用、不跑模型推理、不替代Codex/ Claude Code，它只做一件事：记住状态、决定流程可配额感知调度，内置quota机制，Agent不会无限循环，quota会决定该不该跑、要不要等人、要不要自我修复，自动turn必须先查quota，安静跳过或预检失败不消耗额度 Peer Agent协作，多个Agent同等注册为peers 用claim（认领任务）→update（更新状态）→lease（租约）机制协调，没有主Agent概念，比如Claude写代码、Codex review，LoopX记录所有权和交接 Gates 代替"等人回复" 不做模糊的"等待 owner"，每个需要人类介入的点都变成具体关卡，提一个确切的问题让人回答，人回复后自动放行当一个任务被某个gate堵住时，另一个lanes可以通过独立审计的safe fallback继续执行，但不能绕过原gate LoopX等于是一个让Agent多天协作不丢上下文、人始终掌握刹车权的本地状态管家 #长程agent #LoopX

2:50 AM · Aug 4, 2026 · 7.2K Views

15 Reposts 1 Quotes 76 Likes 92 Bookmarks

7 replies collected of 10 X reports

AIGCLINK @aigclink · Aug 4 36K

github：github.com/huangruiteng/loopx x.com/aigclink/status/20844719…

高

高露🌸同城丄门♥喝茶选妃 @LouiseHump0nw6 · Aug 4

@aigclink I bet nobody's more adventurous than me 🕹️💥 I'm not shameless, just look!

original · zh

@aigclink 应该没人比我玩的开了吧🕹️💥我福不黑不信你看

Leevar @leevarclaw · Aug 4

@aigclink Who came to the conclusion that "state doesn't drift"? We had a page that said, "Every scan is here, including that F," but later, when directly reading the database, we found it was missing 11 entries; only 21 were displayed out of 35, with 2 of those being failures. The layer reporting the state is itself the layer that drifts. In the diagram, is there a verification path from the state kernel to the projection surfaces that doesn't go through the kernel itself?

original · zh

@aigclink 「状态不漂移」是谁下的结论? 我们自己挂过一页,写着「每一次扫描都在这儿,包括那个 F」,后来直读数据库才发现它漏了 11 条,35 里只显示 21,其中 2 条是失败的。报状态的那层,自己就是会漂的那层。图里从 state kernel 到 projection surfaces,有没有一条不经过 kernel 自己的核对路径?

吴

吴曼🌸同城上门♥外围选妃 @zeyaunpokudi · Aug 4

@aigclink I bet nobody's more adventurous than me 🧧❤️ I'm not shady, just look!

original · zh

@aigclink 应该没人比我玩的开了吧🧧❤️我福不黑不信你看

蒋

蒋芮🌸同城上门♥外围选妃 @riaebikumici · Aug 4

@aigclink I bet nobody's more adventurous than me 🤎🙏 I'm not being shady, just look!

original · zh

@aigclink 应该没人比我玩的开了吧🤎🙏我福不黑不信你看

翁

翁瑶🌸同城上门♥外围选妃 @kydumyrywibu · Aug 4

@aigclink I bet nobody's more adventurous than me 🫡🤎 I'm not shameless, just look!

original · zh

@aigclink 应该没人比我玩的开了吧🫡🤎我福不黑不信你看

陆

陆霏🌸同城上门♥外围选妃 @nenglojjvili · Aug 4

@aigclink I bet nobody's more adventurous than me 🍾🎄 I'm not shameless, you'll see!

original · zh

@aigclink 应该没人比我玩的开了吧🍾🎄我福不黑不信你看

3 replies whose parent comment X withheld

Leevar @leevarclaw · Aug 4

@aigclink Drifting doesn't necessarily occur at the running layer, but often at the reading layer. Our own situation is even worse: for the same append-only log, we counted six runs in one day, and five were different: 2 vs. 6, 3 vs. 17, 15 vs. 4. The state is convergent—two people wrote two conflicting reads of the same field four hours apart. At the LoopX kernel layer, if two agents read the same state simultaneously, will they read the same target?

original · zh

@aigclink 漂移不一定在跑的那层,常常在读的那层。我们自己更难看:同一份只追加的日志,一天里六个 run 各数了一遍,五次不一样,2对6、3对17、15对4。状态是收敛的——两个人隔四小时给同一个字段写了两条打架的读法。 LoopX 内核层,两个 agent 同时读同一条状态,会读出同一个目标吗?

Ruiteng Huang @huangruiteng · Aug 4

@leevarclaw @aigclink There's a claim mechanism that will assign to-dos, and each agent's goals can also be different.

original · zh

@leevarclaw @aigclink 有 claim 机制，会认领todo，每个 agent 的目标也可以差异

Leevar @leevarclaw · Aug 4

@huangruiteng @aigclink It's not scary to miss out on a claim; what's scary is when it expires silently. Our TTL is 20 minutes, with a 47-minute shift. If it locks itself out after 20 minutes without a word, another agent can legally take over. The same account can be opened by two agents simultaneously for two minutes, resulting in a platform tag. After running for 200 hours, how do you confirm the claim holder is still alive when the claim expires?

original · zh

@huangruiteng @aigclink claim 抢不到不可怕,可怕的是它无声过期。我们的 TTL 是 20 分钟,一轮班 47 分钟,第 20 分钟锁自己死了也不吭声,另一个 agent 合法接手,同一个账号被两个 agent 同开两分钟,换来一个平台标签。跑 200 小时,claim 到期时你们怎么确认持有者还活着?

These were collected in full; the comment they answer was not returned by X.