claude-code - 💡(How to fix) Fix Session cut mid-task by credit limit — no warning, context lost, costly model switch

Problem

Two related issues happened in the same day:

1. Opus 4.8 consumed 2 full sessions (~20€) without completing any work

I was working on a multi-file debugging task. Claude Opus 4.8 was making progress, then the session was cut by the credit limit. I restarted — same thing happened again. Two sessions consumed, ~20€ spent, zero commits produced.

Claude Sonnet 4.6 then had to reconstruct the entire context and redo the work from scratch.

2. Session cut mid-task at 38% with no warning

A separate session (Sonnet 4.6) was interrupted at 38% completion while actively editing files. No warning was shown before the cut. The modified files were uncommitted, so all in-progress work was in an undefined state until the next session reconnected and reconstructed the context from git diff.

Expected behavior

• Low credit warning shown in the UI before a session is terminated, with enough time to commit work-in-progress
• Or at minimum: a clear error message explaining why the session ended, not a silent cut

Why this matters

For long coding sessions with file modifications, a sudden cut without warning can leave:

• Uncommitted partial changes with no record of what was being worked on
• Expensive model sessions that produced nothing billable
• Wasted time reconstructing context in the next session

Environment

• Platform: Claude Code (desktop app, Windows 11)
• Models affected: Claude Opus 4.8 (credit drain), Claude Sonnet 4.6 (mid-task cut)
• Task type: multi-file debugging across a Node.js/Electron project

Suggestion

A simple warning banner before the session is cut would prevent most of this friction, e.g. "⚠ Low credit — consider committing your work".