Showcase & Good Case
LoopX preserves goals, gates, todos, claims, quota, run history, and evidence outside any single agent session.
Top showcase cases
13+ hour C++ algorithm accuracy run
An independent user reported a >13h multi-stage C++ accuracy task that stayed on goal, found a public code-memory tool, and improved the final precision.
Proof: A >13h engineering run can remain aligned, change method through public research, and retain an understandable evidence trail.
Four-day unattended agent run
An independent user reported that an agent ran for four days without human intervention, continued useful work, and exposed a weekly-report capability.
Proof: A user observed four days of unattended work and judged the work useful, with a later reporting surface available for inspection.
Public engine refactor across seven merged PRs
A user attributed a public Engine decomposition to LoopX; the repository shows the work landing incrementally through seven merged PRs.
Proof: One public refactor goal landed as seven merged PRs instead of a monolithic change.
Overnight PR batch with reviewable control
An overnight LoopX run can produce many PR-sized slices while keeping review, validation, and public evidence boundaries visible.
Proof: High-throughput multi-lane work can remain PR-sized, reviewable, and merge-safe.
PR issue automatic fix loop
Review feedback should become an ordered repair workflow with repro, fix, validation, and reviewer handoff.
Proof: Issue and review feedback can enter an executable repair loop.
Agent-to-agent PR comment and fix loop
PR review feedback can become an owned agent todo with fix evidence instead of a loose chat reminder.
Proof: Multiple agents can coordinate around PR review comments without losing owner review.
Overnight project refactor as PR-sized slices
A broad refactor can run overnight while staying split into human-sized review units.
Proof: Long unattended refactors can split into moderate PR slices instead of one unreviewable diff.
Dynamic workflow for hardware-agent development
A fuzzy long-running engineering goal needs a shared control plane when multiple worker agents participate.
Proof: Fuzzy goals, multiple workers, and long unattended runs can still converge.
LoopX self-iteration loop
A high-churn LoopX repo stayed legible while benchmark, product, docs, planning, and peer lanes moved in parallel.
Proof: A high-churn multi-lane project can keep state, boundaries, and evidence coherent.
Blocked P0 with safe P1/P2 rotation
A gated P0 lane should not stall a whole long-running goal when safe fallback work exists.
Proof: A user decision should not block all safe work.
Experimental today-value path
A lower-priority entry point for users who want to pick one useful LoopX capability today without replacing the showcase first screen.
Appendix case
DSH × LoopX Replan
A real DSH session changes a logging-library decision after a serverless constraint while preserving the original evidence and successor work.
Proof: A host-native agent can change plans without erasing why the old plan was superseded.
Creator-operator long-running agent case
A creator-operator needs a long-running agent loop that keeps research moving while publishing decisions stay gated.
Proof: A creator-operator needs a long-running agent loop that keeps research moving while publishing decisions stay gated.