Post

Ernesto Jiménez
@ernesto-jimenez.com

That's super interesting! Really looking forward to try it out. One use-case you might want to cover: collaboration with coding agents. Where the result of the review is a prompt for changes to the agent with all the comments. I already wanted something like this when working with Claude Code :)

Paul
@ptsou.bsky.social

As someone who reviews quite a bit of code, this would be really nice to try out. Looking forward to the journey and alpha builds hopefully in early 2026.

fintohaps.bsky.social
@fintohaps.bsky.social

Hey 😊 I'm one of the maintainers on @radicle.xyz, and came across your blog. It's super interesting and quite the undertaking – love to see it 😍 It would be great to explore how Flirt could work with Radicle. We've thought about some of these problems in the past too – without any solutions (yet!)

Remo Senekowitsch
@buenzli.dev

Very cool! I skimmed the user guide's sections on patches. It looks like Radicle doesn't have its own concept of code review? That's a good thing, from the perspective of making a Flirt-backend for Radicle. There's no need for an "adapter" between Radicle's and Flirt's concepts of code review.

fintohaps.bsky.social
@fintohaps.bsky.social

Currently, there is a data model for reviews, but it's been more of a light-PoC, and definitely needs more thought. That's where linking in with Flirt would really help! Radicle is also extensible, so there could be a Flirt specific COB (Collaborative Object).

Remo Senekowitsch
@buenzli.dev

I think I'll have to read a little more about the Radicle protocol to understand what a Flirt backend for it would entail. It looks super interesting so far!

fintohaps.bsky.social
@fintohaps.bsky.social

I'll be curious about how you want tackle consistency for comments. Diff algorithms have parameters that can be chosen by the end-user. So, we've wondered how to give power to the users while also having a consistent view 🧐