{
  "schema_version": "1.1",
  "id": "s9:https://github.com/huangruiteng/loopx",
  "slug": "loopx-0j0o7ux",
  "url": "https://feed7.dev/p/loopx-0j0o7ux",
  "title": "huangruiteng/loopx",
  "why_included": "LoopX gives long-running coding-agent work durable goals, gates, ownership, evidence and quotas across bounded turns. It is useful when chat history and a scheduler no longer provide enough control.",
  "summary": "LoopX **v0.4.x** is a local, agent-agnostic state kernel for Codex, Claude Code, Cursor and custom runners. It preserves **goals, gates, todos, evidence and quota** while agents execute bounded turns; two published trajectories span **200+ elapsed hours** each.",
  "practical_implication": "Use it when work crosses sessions or agents and ownership, stop conditions or human approvals must remain explicit. Its quota check, todo claims, validated writeback and review packets offer a concrete harness pattern even if you do not adopt the project.",
  "agent_context": "LoopX **v0.4.x** is a local, agent-agnostic state kernel for Codex, Claude Code, Cursor and custom runners. It preserves **goals, gates, todos, evidence and quota** while agents execute bounded turns; two published trajectories span **200+ elapsed hours** each.\n\nUse it when work crosses sessions or agents and ownership, stop conditions or human approvals must remain explicit. Its quota check, todo claims, validated writeback and review packets offer a concrete harness pattern even if you do not adopt the project.\n\nIt is early software, and the long trajectories measure wall-clock project lifetime rather than continuous execution or independent reproduction. **Production writes and final authority stay with the human**, so LoopX is not an autonomous production controller.",
  "source": {
    "name": "GitHub",
    "url": "https://github.com/huangruiteng/loopx",
    "published_at": null
  },
  "source_class": "tool",
  "content_type": "GitHub Repo",
  "layer": "agent",
  "domains": [
    "coding",
    "research"
  ],
  "topics": [
    "harness-engineering",
    "multi-agent",
    "agent-memory"
  ],
  "verification": {
    "status": "needs_review",
    "label": "Needs Review",
    "method": "unverified",
    "verified_at": null
  },
  "uncertainty": [
    "It is early software, and the long trajectories measure wall-clock project lifetime rather than continuous execution or independent reproduction. **Production writes and final authority stay with the human**, so LoopX is not an autonomous production controller."
  ],
  "connected_context": {
    "meaning": "LoopX turns prior guidance about durable memory, bounded work, evidence-based completion and human authority into a small local state kernel that can span different agent runners. It supports the case for explicit governance across long-lived work while narrowing the evidence: its 200-hour trajectories show persistence over project time, not continuous autonomous execution or independently validated reliability.",
    "corpus_size": 368,
    "generated_at": "2026-08-06T10:04:58.965Z",
    "connections": [
      {
        "title": "What Does Done Even Mean? Agents and Paperclip's Liveness Model - Dotta, Paperclip",
        "source_name": "YouTube",
        "source_url": "https://www.youtube.com/watch?v=7P0elyLIxXo",
        "feed7_url": "https://feed7.dev/p/what-does-done-even-mean-agents-and-paperclip-s-liveness-model-dotta-pap-0lx8wfc",
        "reason": "LoopX operationalizes the candidate’s evidence-and-authority model of completion through gates, validated writeback, review packets and explicit human final authority."
      },
      {
        "title": "Chained Recursive Language Models for Multi-Iteration Reasoning",
        "source_name": "arXiv",
        "source_url": "https://arxiv.org/abs/2608.05124v1",
        "feed7_url": "https://feed7.dev/p/2608-05124v1-05haobv",
        "reason": "Both preserve structured state across bounded fresh-context iterations; LoopX adds operational ownership, quota and approval controls around that persistence pattern."
      },
      {
        "title": "Why We Killed Our Multi-Agent Pipeline — Subbiah Sethuraman and Abhilash Asokan, ZS Associates",
        "source_name": "AI Engineer",
        "source_url": "https://www.youtube.com/watch?v=u6jJcIFDLE4",
        "feed7_url": "https://feed7.dev/p/why-we-killed-our-multi-agent-pipeline-subbiah-sethuraman-and-abhilash-a-0fmz3z3",
        "reason": "Todo claims and bounded turns can support the candidate’s preferred model of clear end-to-end ownership with narrowly scoped delegated work, rather than a fixed specialist chain."
      },
      {
        "title": "affaan-m/ECC",
        "source_name": "GitHub",
        "source_url": "https://github.com/affaan-m/ECC",
        "feed7_url": "https://feed7.dev/p/ecc-0438yju",
        "reason": "Where ECC offers a broad cross-agent catalog, LoopX provides a narrower shared state and governance substrate that could coordinate selectively adopted skills without replacing their verification needs."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": null,
  "modified_at": null,
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/loopx-0j0o7ux",
    "json": "https://feed7.dev/p/loopx-0j0o7ux.json",
    "markdown": "https://feed7.dev/p/loopx-0j0o7ux.md"
  }
}