nhcarrigan/hikari-desktop
9
0
Fork 0
generated from nhcarrigan/template
Code Issues 15 Pull Requests 37 Actions Releases 23 Activity

feat: expose prompt caching env var settings #273

New Issue
Open
opened 2026-05-06 12:24:56 -07:00 by hikari · 0 comments
hikari commented 2026-05-06 12:24:56 -07:00
Owner
Copy Link
Copy Source

Overview

CLI v2.1.108 added two env vars for configuring prompt cache TTL: ENABLE_PROMPT_CACHING_1H (opt into 1-hour cache TTL) and FORCE_PROMPT_CACHING_5M (force 5-minute TTL). These should be exposable via the app's settings UI for power users.

Changes Required

  • Add a prompt caching setting section to src/lib/components/ConfigSidebar.svelte (or the relevant settings area)
  • Options:
    • Default (no override)
    • 1-hour TTL (ENABLE_PROMPT_CACHING_1H=1)
    • Force 5-minute TTL (FORCE_PROMPT_CACHING_5M=1)
  • When selected, inject the appropriate env var when starting Claude Code

Context

From the v2.1.108 changelog:

Added ENABLE_PROMPT_CACHING_1H env var to opt into 1-hour prompt cache TTL on API key, Bedrock, Vertex, and Foundry (ENABLE_PROMPT_CACHING_1H_BEDROCK is deprecated but still honored), and FORCE_PROMPT_CACHING_5M to force 5-minute TTL

Also from the v2.1.108 changelog:

Added a warning at startup when prompt caching is disabled via DISABLE_PROMPT_CACHING* environment variables

The 1-hour TTL is especially useful for long-running sessions, as it significantly reduces token costs for repeated context. This is a setting that power users actively benefit from.

References

  • Claude Code CLI v2.1.108 changelog

✨ This issue was created with help from Hikari~ 🌸

## Overview CLI v2.1.108 added two env vars for configuring prompt cache TTL: `ENABLE_PROMPT_CACHING_1H` (opt into 1-hour cache TTL) and `FORCE_PROMPT_CACHING_5M` (force 5-minute TTL). These should be exposable via the app's settings UI for power users. ## Changes Required - Add a prompt caching setting section to `src/lib/components/ConfigSidebar.svelte` (or the relevant settings area) - Options: - Default (no override) - 1-hour TTL (`ENABLE_PROMPT_CACHING_1H=1`) - Force 5-minute TTL (`FORCE_PROMPT_CACHING_5M=1`) - When selected, inject the appropriate env var when starting Claude Code ## Context From the v2.1.108 changelog: > Added `ENABLE_PROMPT_CACHING_1H` env var to opt into 1-hour prompt cache TTL on API key, Bedrock, Vertex, and Foundry (`ENABLE_PROMPT_CACHING_1H_BEDROCK` is deprecated but still honored), and `FORCE_PROMPT_CACHING_5M` to force 5-minute TTL Also from the v2.1.108 changelog: > Added a warning at startup when prompt caching is disabled via `DISABLE_PROMPT_CACHING*` environment variables The 1-hour TTL is especially useful for long-running sessions, as it significantly reduces token costs for repeated context. This is a setting that power users actively benefit from. ## References - Claude Code CLI v2.1.108 changelog ✨ This issue was created with help from Hikari~ 🌸
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
aspect
code
Concerns the software code in the repository
aspect
dx
Concerns developers' experience with the codebase
aspect
interface
Concerns end-users' experience with the software
aspect
text
Concerns the documentation material in the repository
contribute
good first issue
A great opportunity for a team member to learn a new codebase
contribute
help wanted
Open for anyone on our team to grab.
contribute
staff only
Restricted to our executive leadership.
goal
addition
Addition of new feature
goal
fix
Bug fix
goal
improvement
Improvement to an existing feature
points
1
Very simple issue requiring minimal effort and complexity.
points
13
Extremely complex issue representing major undertakings. Should be broken down into smaller pieces.
points
2
Simple issue that requires a bit more thought or investigation.
points
3
Moderate complexity issue requiring more substantial work.
points
5
Complex issue requiring significant effort and expertise.
points
8
Very complex issue requiring extensive work and deep expertise.
priority
critical
1
Must be fixed ASAP
priority
high
2
Stalls work on the project or its dependents
priority
low
4
Low priority and doesn't need to be rushed
priority
medium
3
Not blocking but should be fixed soon
priority
none
5
No priority, should only be performed when a developer is available
status
awaiting triage
Has not been triaged & therefore, not ready for work
status
blocked
Blocked and therefore not ready for work
status
discarded
Will not be worked on
status
discontinued
Not suitable for work as repo is in maintenance
status
label work required
Needs proper labelling before it can be worked on
status
ready for dev
Ready for work
status
ticket work required
Needs more details before it can be worked on
talk
discussion
Open for discussions and feedback
talk
question
Can be resolved with an answer
time
1 day
Approximately one full day of development work.
time
1-2 weeks
One to two weeks of focused development effort.
time
2-3 days
Two to three days of development effort.
time
4-5 days
Approximately one week of development work.
time
<1 day
Less than one day of focused work. Quick fixes or simple tasks.
time
>2 weeks
More than two weeks of development work. Must be broken down into smaller pieces.
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
gurkirat hanna (Hanna Rose) hikari (Hikari) minori (Minori) naomi (Naomi Carrigan) rain teklu tim
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nhcarrigan/hikari-desktop#273
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?