Show HN: Claude-thermos keeps your Claude session warm for you

Yes, this wastes cycle. They dump your cache and deallocate the VMs so that others can use it. This will result in tokens wasted and downtime for others.

Re: Show HN: Claude-thermos keeps your Claude session warm for you

#7

Post by jonas21 » Thu, Jul 23, 2026, 6:23 PM UTC

Is the 5-minute expiration correct? I thought it was more like ~1 hour.

Re: Show HN: Claude-thermos keeps your Claude session warm for you

#8

Post by j45 » Thu, Jul 23, 2026, 6:23 PM UTC

This is a good idea if it could manage it in an acceptable way.

For example, there might be something I intended to complete in one sitting, but took two sittings in the same day unexpectedly. Maybe it could just be a few cache delays per day or something, tagged in advance somehow.

Re: Show HN: Claude-thermos keeps your Claude session warm for you

#9

Post by szin » Thu, Jul 23, 2026, 6:25 PM UTC

On a subscription Claude Code already defaults to 1h TTL and on an API key you opt in with ENABLE_PROMPT_CACHING_1H=1.

Was the ~22% claimed in the repo is measured against the 5m default, or with the 1h flag on?

Re: Show HN: Claude-thermos keeps your Claude session warm for you

#10

Post by unholiness » Thu, Jul 23, 2026, 6:27 PM UTC

I've directly inspected calls for pro/Max plans and as of today they have 1hr cache expiries. This has definitely degraded to 5 min in the past but that's the behavior today.

If you're paying API rates, you can choose 5m or 1hr yourself (and pay different rates).

Keeping a 1hr cache warm could still be useful, sure, but outside that, I don't see much use of this today.