zlacker

[parent] [thread] 4 comments
1. within+(OP)[view] [source] 2026-01-23 06:48:20
Do people actually use this mode? Having to approve diffs in the ide is too annoying.
replies(2): >>solumu+S5 >>HumanO+np1
2. solumu+S5[view] [source] 2026-01-23 07:43:14
>>within+(OP)
Depends on my task. If it’s complex and my expectation is for Claude to get things wrong the diff preview is helpful.
replies(1): >>vidarh+id
◧◩
3. vidarh+id[view] [source] [discussion] 2026-01-23 08:49:17
>>solumu+S5
Even then, I'd wait until it's had a chance to iterate and correct itself in a loop before I'd even consider looking at the output, or I end up babysitting it to prevent it from making mistakes it'd often recognise and fix itself if given the chance.
replies(1): >>solumu+Su
◧◩◪
4. solumu+Su[view] [source] [discussion] 2026-01-23 11:24:47
>>vidarh+id
True. I’ve been strictly in the terminal for weeks and I have a stop hook which commits each iteration after successful rust compilation and frontend typechecks, then I have a small command line tool to quickly review last commit. It’s a pretty good flow!
5. HumanO+np1[view] [source] 2026-01-23 16:51:10
>>within+(OP)
You can tell it not to do that and it will show inline diffs.
[go to top]