LoopTroop is a local, open-source GUI app that prevents context rot in long coding tickets by using an LLM council for planning, task decomposition into independent beads, and controlled execution with failure notes, keeping the developer in the loop.
Hy guys. Just built an open source project. Most AI coding tools work well for small edits, but they tend to derail on larger features. The main reason is context rot. When you append all error logs and old code iterations into one long chat history, the model eventually loses the plot. It starts dropping imports, ignoring instructions, or fabricating files. To address this, I built LoopTroop. It is a local, open-source GUI app designed to run complex repository-level tickets. It is not built for speed. It is slow and precise, prioritizing correctness and matching your intent. Here is how the workflow is structured to prevent context rot: Interactive interview. Before any code is touched, the app scans the repository and asks a round of targeted questions to resolve ambiguities in the ticket. LLM Council planning. Instead of relying on a single model, multiple configured models write drafts of the PRD and task breakdown. They then vote anonymously on the drafts. The winning plan absorbs the best ideas from the other drafts and goes through a coverage check. Task decomposition. The council splits the plan into small, independent implementation units called beads. Each bead defines its own target files and acceptance criteria. Ralph Loops for execution. The app executes beads one at a time. If a bead fails or times out within its 20-minute box, the app writes a short note of what went wrong, resets, and starts a fresh execution session. It carries that failure note forward so the model learns from the mistake instead of inheriting a polluted chat transcript. Human in the loop. The developer is in control at every boundary. You review and approve the planning documents and the final code changes before anything is merged. The frontend is a modern Kanban board GUI, so you can manage multiple projects and tickets in parallel without leaving the app. I am looking for feedback on the architecture and the workflow. Any feedback is more than welcome. If you try the app and it works or doesn't work, give me a sign. I am happy to talk about it.
Developer achieves productive local agentic coding with Qwen3.6-35B 4-bit MLX and pi.dev tool, completing real tickets efficiently on current hardware.
A local control system is built to manage agent improvement loops, capturing traces, finding recurring failures, drafting fixes with Codex/Claude Code, and applying changes only after passing checks and evals.
This article introduces Looper, a tool that helps design effective loops for AI goals by critiquing loops, building verification rubrics, setting guardrails and token budgets, and exporting portable artifacts for use with Claude Code.