Launched this week
Codeflow
tree-sitter, CodeMirror, no install
7 followers
tree-sitter, CodeMirror, no install
7 followers
Open an unfamiliar folder and CodeFlow unfolds it into an interactive node graph you can actually read — a semantic map grouped by feature, or a physical map ranked by importance. Change the flow on the canvas — add, delete, reconnect, annotate — and it rewrites the real files to match, every change shown as a line-by-line diff you Keep or Undo.
The diff view keeps things honest, which I really appreciate — too many tools hide what they actually changed. Dragging nodes around to restructure a folder felt weirdly satisfying, almost like organizing a whiteboard.
@meryemdemi73015 Thanks, Meryem. I’m really glad the diff made the changes feel more trustworthy — that was important to me. And I love the whiteboard comparison. That’s exactly the feeling I’m trying to get to when you’re moving things around and thinking through a structure.
Being able to scope the graph to just the files in a git branch would be huge for reviewing PRs, since right now it always shows the whole repo. A dropdown to filter by branch or commit, with the diff view tied to those changes specifically, would make Codeflow feel built right into the review workflow.
@ceydakl6mhw That’s such a good point. A graph that starts from a branch or commit range would be much more useful for an actual PR review than dropping you into the whole repo every time. I’d want it to show the changed pieces first, then pull in just enough surrounding context to make the impact clear. Curious: would you use current branch vs main most often, or a custom commit range?