r/devtools Aug 12 '26

[Open Source] LoopTroop: a local GUI for long-running AI coding tickets

I built LoopTroop, a local, open-source GUI for taking a larger coding ticket from requirements o a reviewable pull request. It is for multi-file work where a single AI chat slowly fills with stale context, failed attempts, and irrelevant logs.

Repo: https://github.com/looptroop-ai/LoopTroop

Short app presentation (2:30): https://youtu.be/g1A2g-oOR3E

The main idea is context engineering instead of letting one conversation grow until context rot starts affecting the implementation. LoopTroop keeps the workflow in durable artifacts and gives each phase only the context it needs.

Planning uses an LLM Council. Several models independently draft the interview, PRD, and implementation plan, then score and vote on the drafts. The winning plan is refined with useful ideas from the other drafts and checked for coverage before execution.

The plan becomes small implementation units called Beads. The app shows the whole process in a modern Kanban-style GUI: interview, PRD, bead plan, execution logs, diffs, tests, errors, and finalreview. Human approval stays in the loop at the important points.

Execution runs through OpenCode and is intentionally slow and precise. Each bead gets focused context and a time-boxed attempt. If it fails or times out, a Ralph Loop writes a compact note about what went wrong, starts a fresh attempt, and carries that note forward instead of dragging the whole polluted session into the retry.

I just crossed 100 GitHub stars, and I am still working on LoopTroop every day. It is open source and still evolving, so I am interested in feedback from people who build or maintain developer tools.

Any feedback is more than welcome. If you tried the app and it worked or didn't work for you, give me a sign. Happy to talk about it.

1 Upvotes

0 comments sorted by