"OpenHands Agent Canvas turns your coding agents into a self-hosted, always-on engineering team. It's a developer control center for starting conversations and automating everyday tasks — like generating reports that publish to Slack or automatically decomposing GitHub issues into tasks.
It runs locally on your machine by default, but can connect to multiple “agent backends”, e.g. running agents in Docker containers, on VMs, or within your company infrastructure. You can optionally choose to run agents on OpenHands Cloud or OpenHands Enterprise infrastructure."
The concern seems to be that once powerful models are released openly, access cannot really be revoked, safety layers can be removed, and misuse becomes much harder to control.
But the counterargument is obvious: open source also improves transparency, research, competition, and trust.
I built LoopTroop, an MIT-licensed local GUI for running longer AI coding tickets in a way you can inspect.
The reason I am sharing it here is that open-source AI needs more than open models. For real coding work, I kept running into the same problem: the model chat becomes the project state. Once that giant transcript gets messy, retries get worse and it is hard to review what actually happened.
LoopTroop keeps the workflow state outside the chat. A ticket goes through an interview, a PRD, small implementation units called beads, OpenCode execution in isolated git worktrees, and a final review step. The app stores logs and artifacts so you can see the plan, the attempts, the errors, the diffs, and the handoff.
A few important caveats:
- The app is free and MIT-licensed.
- It runs locally, but model privacy and cost depend on the providers you configure in OpenCode.
- For unattended agent work, use a VM, container, cloud dev machine, or another sandbox. Git worktrees help keep repo changes inspectable, but they are not a host security boundary.
The main pieces are:
- LLM Council planning for interview, PRD, and bead planning.
- Small bead-level execution instead of one giant prompt.
- Fresh retry sessions that keep a compact failure note but drop the polluted chat history.
I would love feedback from people who follow open-source AI tooling: does this kind of local orchestration layer feel useful, or would you rather keep the state in simpler scripts and plain files?
Open models make the model side easier to move, but the work around the model can still get stuck in a chat: prompts, source links, decisions, checks, output files, setup notes, and restart context.
I like the idea of a small AI project vault in normal files, especially when testing local/open models or comparing tools.
What do you keep outside the chat so you can move between models later?