Cache & Offline
Revalidation and warm offline reuse behavior.
Fuzit's GitHub design relies on a local cache rather than hosted indexing.
Remote Caching
When you acquire remote state (such as a PR or issue), Fuzit fetches only the required Git refs/revisions, creates a disposable detached worktree, runs the analysis pipeline, and then removes the temporary state.
It retains only the allowed Fuzit-owned cache and provider data. The cache respects provider-aware concepts such as pagination, rate limits, and HTTP revalidation (ETag/Last-Modified).
Warm Offline Reuse
Previously acquired remote state may be reused offline. However, Fuzit is explicit about staleness; cached data is never silently presented as current when the network is unreachable.