workflow-friction-audit

You can track recurring tool-call failures by logging friction entries into a persistent log. When enough entries accumulate, the system groups them by root cause and proposes permanent fixes like CLAUDE.md edits or script updates.

The best way to group workflow friction logs is to accumulate entries until a specific threshold is reached. Once the threshold is met, the entries are automatically grouped by root cause to surface concrete improvement actions.

You propose permanent fixes for automation quirks by reviewing grouped friction logs. The system recommends applying CLAUDE.md edits, updating scripts, or creating follow-up issues to address the identified root causes.

Yes, you can use CLAUDE.md edits to resolve recurring tool friction in a devcontainer. The friction audit logs environment quirks and proposes edits to CLAUDE.md as a permanent fix for recurring tool-call failures.

You should log workflow friction entries instead of fixing issues immediately when you notice recurring environment quirks. Logging persistent entries allows the system to group them by root cause later and propose structured, permanent fixes during review.