[BUG] Repeated session crashes/aborts when processing meeting notes with subagent
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
## Description
Claude Code sessions repeatedly abort/crash when processing meeting notes using the meeting-note-processor subagent. This has happened multiple times in a row, making it impossible to complete work.
## Actual Behavior
Session terminates unexpectedly with no error message. When reconnecting, Claude has no memory of the previous session. Claude is able to process the call transcripts without the subagent.
## Environment
- Claude Code version: 2.1.23
- OS: macOS 15.6.1
- RAM: 32 GB
- MCP servers: Atlassian, Gmail, Obsidian
- Using subagents: meeting-note-processor
## Additional Context
- Happens consistently when processing meeting transcripts
- No crash logs found in ~/Library/Logs/DiagnosticReports/
- Main log (~/Library/Logs/Claude/main.log) shows no obvious errors
- This is blocking critical workflow for meeting note processing
## Impact
Medium - Cannot complete job duties without reliable transcript processing and not using a subagent fills my context window.
What Should Happen?
## Expected Behavior
The subagent should complete processing the transcript and create/update notes without crashing.
Error Messages/Logs
No logs. System says Aborted() and then presents a blank screen that I have to Ctrl-C out of.
Steps to Reproduce
## Steps to Reproduce
- Start Claude Code in Obsidian vault
- Ask Claude to process a call transcript from inbox using a subagent
- Session aborts mid-processing
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.1.21
Claude Code Version
2.1.23
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
iTerm2
Additional Information
Here is the subagent:
meeting-note-processor.md
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗