Sessions stop unexpectedly, requiring manual 'continue' prompts
Resolved 💬 4 comments Opened Jan 4, 2026 by one-kash Closed Jan 7, 2026
Description
Claude Code sessions are stopping mid-task and requiring manual prompts like "continue" or "keep going" to resume work. This happens repeatedly across multiple sessions.
Environment
- Claude Code CLI (latest)
- Platform: Linux (Amazon Linux 2023)
- Model: Opus 4.5 (via AWS Bedrock)
Steps to Reproduce
- Start a Claude Code session with a multi-step task (e.g., creating test files, running builds)
- Let Claude work on the task
- Session stops mid-task without completing or asking for input
Expected Behavior
Claude Code should continue working on the task until completion or until it needs user input/clarification.
Actual Behavior
Sessions stop unexpectedly mid-task. User must type "continue" or "keep going" to resume. This has happened multiple times across different sessions (Jan 3-4, 2026).
Additional Context
- Happening during complex tasks involving file creation, test execution, and builds
- No apparent error or timeout message displayed
- Context window doesn't appear exhausted - conversation continues normally after "continue"
- Tasks are well within normal scope (creating ~50 lines of code, running gradle commands)
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗