What value to you get from having this happen on every turn with a change? I get that the ratio should be a lot higher than the default. Doesn't doing this for every turn where something changed slow things down a lot without gain? I haven't experimented, that's why I'm curious. Why not 1 line or 2 in a CLAUDE.md or AGENTS.md so that the agent ups the frequency, but doesn't make it every single time?
skolos•30m ago
1 line in CLAUDE.md I tried (one line, 100 lines, many iterations) - it not always follows style instructions.
The value is very large for me - instead of reading page of Claude produced prose, I mostly just look at focused choices and continue with single button press - significantly less Claude deciphering and typing now. In addition, I do my sessions with /rc so I get nice form on mobile app where I can just select a button instead of typing to continue work.
PS: I think there is confusion in term - "every turn" - I don't mean every tool call, I mean after minutes or hours of agent work when agent decides that its done it gives a report. The report I see now has structure to it with options set to continue (or stop).
Redster•37m ago
skolos•30m ago
The value is very large for me - instead of reading page of Claude produced prose, I mostly just look at focused choices and continue with single button press - significantly less Claude deciphering and typing now. In addition, I do my sessions with /rc so I get nice form on mobile app where I can just select a button instead of typing to continue work.
PS: I think there is confusion in term - "every turn" - I don't mean every tool call, I mean after minutes or hours of agent work when agent decides that its done it gives a report. The report I see now has structure to it with options set to continue (or stop).