Comment by reasonableklout
16 hours ago
How do you stay in the loop with CC? I find myself using it for the exact opposite use case: large features or greenfield projects where I can just let it rip autonomously for a while. I find the TUI awkward for reviewing code.
I stay in the loop by reviewing each edit and telling it to do something differently asap if something was wrong.
The opposite approach is also possible: just hit the option (or .json setting) to accept all edits. Then you'd review the persisted changes using your favorite Git tool.