Improve project state caching with regular refresh and Claude hook integration #336

New issue

Open

opened 2026-04-07 19:02:54 +00:00 by mprihoda · 0 comments

mprihoda commented

2026-04-07 19:02:54 +00:00

(Migrated from github.com)

Problem

Project state caching is flawed — cached data can become stale without the user noticing, leading to incorrect state being displayed or acted upon.

Proposed Solution

Two-pronged approach:

1. Regular refresh

Implement periodic cache invalidation/refresh on a configurable interval
Ensure stale data is detected and refreshed transparently

2. Claude hooks for cache updates

Add Claude Code hooks that nudge iw dashboard to update the cache
When Claude performs actions that change project state (e.g., completing tasks, updating issues), a hook should trigger a cache refresh
This keeps the dashboard in sync with reality without requiring manual refresh

Context

Currently the cache can drift from actual state, especially during active work sessions where state changes frequently via Claude Code interactions.

## Problem Project state caching is flawed — cached data can become stale without the user noticing, leading to incorrect state being displayed or acted upon. ## Proposed Solution Two-pronged approach: ### 1. Regular refresh - Implement periodic cache invalidation/refresh on a configurable interval - Ensure stale data is detected and refreshed transparently ### 2. Claude hooks for cache updates - Add Claude Code hooks that nudge `iw dashboard` to update the cache - When Claude performs actions that change project state (e.g., completing tasks, updating issues), a hook should trigger a cache refresh - This keeps the dashboard in sync with reality without requiring manual refresh ## Context Currently the cache can drift from actual state, especially during active work sessions where state changes frequently via Claude Code interactions.