[CurleighBraces]

If you haven't read the first blog post it's pretty good at explaining the concepts.

https://blog.buenzli.dev/announcing-development-on-flirt/

The demo is particularly good if you can get past ( by the authors own admission ) slow typing speed.

As with everything these days I can see this being even more useful in reviewing agent code.

For example if an agent has spat out a bunch of code that I've reviewed and then I've asked it to make changes, I definitely do not want to review all that code again in the same diff later.

[OJFord]

That's a really good point, at the moment I struggle to get past wanting it to create small logical changes that I can commit individually. If I could review them better such as Flirt describes, then maybe I don't care so much, and a big 'create initial implementation' commit becomes more acceptable, for example.

[ale]

How is this different than simply committing between changes? Or even asking the agent to commit changes as it edits files.

[CurleighBraces]

Because I don't review everything between changes, there might be 10 small commits I review and state I am happy with, then I might prompt the agent to perform some small refactors after the review, I don't want the diff to show me everything in those 10 commits again in the diff ( like the usual PR would ) I want it only to show me new stuff.