feat: include session context in notifications #1
Description
Problem
When you get a Slack notification, you have no idea what Claude was working on. You just see "Claude wants to use Bash" - but was it building a feature, running tests, or deploying? Without context, it's hard to decide if it's worth switching back.
Proposal
Include session context in the notification body - what Claude was last working on, the last prompt summary, or the current task description. This helps you prioritize whether to context-switch back immediately or finish what you're doing.
Possible approaches:
- Parse the hook input for additional context fields if available
- Show the last user prompt or a summary of the current task
- Include the working directory and recent git activity as a proxy for what's happening
Expected result
Notifications include enough context to make an informed decision about switching back without needing to open the terminal.