Claude needs a nap. You shouldn't have to babysit the clock.

You're deep in the flow, and then:

You've hit your session limit · resets 1:40am

Cool. Cool cool cool. So now you either sit there refreshing, or you wander off and forget all about it until tomorrow afternoon.

This little extension just... handles it. It notices the limit, quietly counts down, and when the clock runs out it wakes your session back up and carries on. Go make tea. Go outside. Sleep. It'll be waiting for you, already working.

How it feels

Claude taps out.
Your status bar picks up the vibe: 🕐 Claude resumes in 4h 32m
You go live your life.
The moment the limit lifts, your session picks up right where you left off — in the same terminal you were already sitting in.

That's the whole thing. No setup, no config, no ceremony.

Getting it

Install, reload the window, and forget it exists. It stays completely invisible until there's actually something to tell you.

The three buttons you might ever want

Hit Ctrl+Shift+P and type "Claude Timeout":

Show Status — how long's left, and a big friendly Resume Now if you're impatient. (Or just click the countdown in the status bar.)
Set Resume Timer — do it by hand. Understands 5h, 90m, at 15:30, whatever.
Cancel Pending Resume — changed your mind. No hard feelings.

Good to know

🌙 Close your laptop. Sleep, hibernate, restart VS Code — the countdown keeps its own time and survives all of it. If the limit lifted while you were away, it just picks up when you come back.
👀 It watches quietly. It reads Claude Code's own session files, so it works even when you run Claude in a terminal outside VS Code.
🤝 It won't nag. One notification when the limit hits, one when you're back.
✋ You're always in charge. Turn off auto-resume and it'll just tap you on the shoulder instead: claudeTimeout.autoResume.

Want to tinker?

There are knobs — which command to run, what prompt to send, how long to wait after the reset, which folder to resume in. All under claudeTimeout.* in settings.

Full details live in DOCS.md next to the extension, if you're into that. Most people never need to open it.

What's fixed in 0.1.1

It now wakes up the terminal you were actually working in.

Before, when the clock ran out you'd get a brand-new terminal off to the side while your real session sat exactly where you left it — still waiting on you to press Enter. Which rather defeats the point of the whole extension.

Three things changed:

Resuming happens in the terminal that hit the limit, not a fresh one. That's the new default (claudeTimeout.resumeTarget). Set it back to newTerminal if you liked the old way.
The terminal no longer gets forgotten. A limit gets spotted twice — once in your terminal, once in Claude's own session files — and only the first knows which terminal it happened in. Whichever showed up second was being thrown away, so half the time that detail vanished and you'd get a new terminal anyway. Now the second sighting fills in what the first was missing.
When it genuinely can't tell, it types into your active terminal instead of giving up and opening a new one.

If the old terminal is really gone — you closed it, the process died — it still falls back to opening a fresh one. Nothing to configure either way.

Made for anyone who's ever stared at a five-hour countdown. Peace. ☮️