Customer.ioAutomate Messaging Everywhere — Startups Get 12 Months Free
Promoted
Launched this week
GitWarren
Review code with your coding agents before committing
81 followers
Review code with your coding agents before committing
81 followers
It’s a local, PR-like code review app that works directly with your working tree. You can review committed, staged, unstaged, and untracked changes, leave inline comments, and organize the work into actual reviews without having to push anything anywhere. You connect whatever AI you're using through MCP and have a coherent experience without all the mundane copy-pasting. All comments live in threads attached to specific code changes, so it’s easy to follow what’s going on over time.
GitWarren
Theneo
Looks very promising, will give it a try this weekend
dif.sh
Love the unique approach to managing your personal workspace. @xfor congrats to your launch!
I run separate git worktrees per agent task rather than multiple agents in the same working tree. Does GitWarren handle reviewing across several worktrees of the same repo at once, or is it scoped to one working tree per instance? If it's the latter, curious if that's a deliberate scope decision or just not the use case you built for first.
GitWarren
@wwenioaguiar once your repository is registered in the app, you define your review compare - 99% of cases it's your feature branch against your main branch - worktree or not it just works out of the box :)
Dial
relatable problem, the copy-pasting review comments between terminals is exactly the kind of friction that quietly eats a day. since you mentioned juggling 5-7 simultaneous ai sessions, curious how gitwarren handles it when two of those sessions touch overlapping files in the same working tree at the same time - does it just show the working tree as one flat diff regardless of which agent made which change, or can it flag that two edits are about to collide before you get to the review stage?
GitWarren
@galdayan interesting question - for now, this app is purely about discussing changes on some branches - spotting potential conflicts between these is something I haven't thought about yet to be honest - I need to think about it
Dial
@xfor fair answer, honest is better than hand-wavy. it's probably an edge case worth flagging since more people will be running multiple parallel agent sessions on the same repo, not just reviewing sequential changes
Reviewing unstaged and untracked changes without pushing them anywhere is really useful. That feels like a much more natural workflow for catching issues before a PR even exists.
GitWarren