aider-1h-ttl

Extend Aider's cache TTL from 5 minutes to 1 hour for long sessions.

113|8|Updated May 28, 2026
One-click install
npx skills add https://github.com/OnlyTerp/prompt-cache-skills --skill aider-1h-ttl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aider-1h-ttl
Source: https://github.com/OnlyTerp/prompt-cache-skills/tree/main/skills/aider-1h-ttl
Command: npx skills add https://github.com/OnlyTerp/prompt-cache-skills --skill aider-1h-ttl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill extends Aider's cache TTL from 5 minutes to 1 hour, reducing the need for keepalive pings and preserving the cache across long sessions.

Core Features & Use Cases

  • Extended Cache TTL: Enables 1-hour cache for longer, uninterrupted sessions.
  • Reduce Keepalive Pings: Cuts down on unnecessary requests, saving on billing.
  • Use Case: Suitable for long, multi-hour sessions where caching across breaks is important, like in complex coding or problem-solving tasks.

Quick Start

Enable the 1-hour cache for Aider with the command: "Apply aider-1h-ttl."

Frequently Asked Questions about aider-1h-ttl

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I extend Aider's cache TTL to avoid expiration during long coding sessions?

To extend Aider's cache TTL, you can apply a configuration that increases the expiration window from 5 minutes to 1 hour. This prevents cache invalidation during prolonged human-in-the-loop pauses in coding sessions.

Why does the Anthropic prompt cache expire during extended human-in-the-loop tasks?

The Anthropic prompt cache expires because its default TTL is set to 5 minutes. When human-in-the-loop reasoning tasks exceed this window without keepalive pings, the cached data is cleared to optimize resource allocation.

Can I use Anthropic's extended cache TTL feature with Aider?

Yes, you can enable Anthropic's extended cache TTL feature within Aider. This modifies the cache management to sustain a 1-hour TTL, which is ideal for repetitive coding tasks that involve extended human delays.

What is the best way to reduce keepalive pings for AI coding cache management?

The best way to reduce keepalive pings is to enable a 1-hour cache TTL for Aider. This extends the cache expiration window, cutting down on unnecessary API requests and saving on billing costs during long sessions.

Does extending the cache TTL to 1 hour increase API costs?

Extending the cache TTL to 1 hour optimizes for Anthropic's extended cache feature, which applies a 2x write cost premium. However, it reduces overall billing by cutting down on unnecessary keepalive pings and cache rebuilds.

When should I not use a 1-hour cache TTL for AI coding sessions?

You should not use a 1-hour cache TTL for short, rapid-fire coding sessions where prompts are exchanged quickly. The 2x write cost premium for extended caching is only ideal for long, multi-hour sessions with extended human delays.