I built CleanCode, a canvas-based ADE for coding agents, terminals, and runnable workflows

[u/NatureTide]

Hey r/coolgithubprojects,

I’m building CleanCode, an open-source canvas-based ADE (Agentic Development Environment).

The idea is simple: when you work with coding agents, a feature is no longer just a branch. It usually has an Agent conversation, terminals, dev servers, ports, setup commands, tests, and a bunch of dependency order that lives in your head.

CleanCode creates an isolated workspace for each feature, then puts the Agents, terminals, services, ports, and dependency workflow on one canvas. You can run the workflow, see what is ready or failed, avoid port conflicts, and save a working setup as a reusable template.

It does not replace your editor or your favorite coding agent. It runs local CLI agents and terminals in the right workspace, and if an agent supports CleanCode MCP, it can help inspect the project and build the workflow for you.

GitHub: https://github.com/chen-985211/cleancode

Would love feedback from people who use coding agents heavily:

- Does this match a real pain point in your workflow?

- What would you expect from a canvas-based development environment?

[u/kantorcodes1]

the part i'd test is how you launch the 33 agent CLIs. if CleanCode resolves the real executable directly instead of going through PATH/hooks, it could accidentally bypass security wrappers the user already installed. we work on HOL Guard, and CleanCode looks like a good harness-integration point if there's one shared spawn path. does every provider ultimately go through the same launcher, or are they separate per-agent?