claude-code - 💡(How to fix) Fix [FEATURE] PostAssistantResponse

{
  "hooks": {
    "PostAssistantResponse": [
      {
        "hooks": [
          {
            "type": "command",
            "command": "cat >> ~/claude_responses.log"
          }
        ]
      }
    ]
  }
}
The hook payload could follow the same pattern as existing hooks — a JSON object on stdin with at minimum:


{
  "text": "<full assistant response text>",
  "session_id": "..."
}


### Alternative Solutions

_No response_

### Priority

High - Significant impact on productivity

### Feature Category

Configuration and settings

### Use Case Example


Routing long responses to a local documentation site or sketchbook (avoiding terminal clutter)
Logging assistant output for review or auditing
Triggering notifications when a task completes
Post-processing responses with custom scripts (summarization, tagging, archiving)

### Additional Context

Why a pseudo-terminal wrapper does not work[¶](http://localhost:8005/#why-a-pseudo-terminal-wrapper-does-not-work)
A pty.spawn wrapper around the Claude Code binary captures raw terminal bytes including ANSI escape codes and Terminal User Interface chrome (borders, spinner, status bar). Extracting clean assistant text from that stream requires complex post-processing and is fragile. A first-class hook is the only reliable solution.

PreToolUse / PostToolUse hooks already demonstrate this pattern works well
Many users have asked for ways to log or redirect Claude output (see related issues) ```