feat: Error categorization system

[sagarsrc]

Scope

backend, frontend

What do you want?

Categorize tool failures by error type to answer "what's the most common error?" and "where is Claude making mistakes?"

Backend:

• Define error pattern categories:

  - User Interruption: "user doesn't want to proceed", "[Request interrupted"
  - Command Timeout: "Command timed out"
  - File Not Read: "File has not been read yet"
  - File Modified: "File has been modified since read"
  - File Too Large: "exceeds maximum allowed"
  - Content Not Found: "String to replace not found", "No module named", "No such file or directory"
  - Permission Error: "Permission denied", "was blocked"
  - Tool Not Found: "command not found"
  - Code Runtime Error: "Cannot find module", "Traceback"
  - Syntax Error: "SyntaxError", "syntax error", "jq: error"
  - Port Binding Error: "while attempting to bind on address"
  

• Regex matching on tool_result content
• Add error_category field to tool_use events
• API endpoint for error analytics

Frontend:

• Error breakdown chart (pie/bar)
• Error trends over time
• Error rates by tool type
• Filterable error list

Estimated effort: 2-3 days

Why?

Users specifically ask "where is Claude making mistakes?" Currently we only show tool success/failure counts with no categorization of failure reasons. This directly answers that question.

[sagarsrc]

Assistant:

Input
{
  "command": "uv add --optional all piper-tts kokoro soundfile"
}

Result
Error: The user doesn't want to proceed with this tool use. The tool use was rejected (eg. if it was a file edit, the new_string was NOT written to the file). STOP what you are doing and wait for the user to tell you how to proceed.

Users:
[Request interrupted by user for tool use]

Reference Image: