claude-code - 💡(How to fix) Fix Feature request: platform-level shared package caching for Cowork sessions [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#46101Fetched 2026-04-11 06:29:00
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
labeled ×2commented ×1

Fix Action

Fix / Workaround

Currently using the persistent data directory workaround (persisting node_modules in a plugin's persistent dir and only reinstalling when package.json changes). This helps per-plugin but doesn't address duplication across sessions. The other option is just hitting "clean up" on the disk warning regularly, which triggers the reinstall loop.

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing requests and this feature hasn't been requested yet
  • This is a single feature request (not multiple features)

Problem Statement

Running 3-4 concurrent Cowork sessions (deal pipelines, health dashboards, scheduled tasks) fills the 9.7 GB workspace disk regularly. Each session independently installs the same base packages (Node, Python, common npm/pip libraries), eating ~381 MB per session -- mostly in dependencies, not data.

The "clean up" option works short-term but triggers a reinstall loop: clean up → reopen session → reinstall same packages → disk fills again within days. Power users running persistent workflows hit this ceiling constantly.

Proposed Solution

Platform-level shared package caching -- common base packages (Node, Python, popular npm/pip libraries) cached once and shared across all Cowork sessions instead of installed fresh per session.

This would significantly cut per-session disk footprint and eliminate the clean up → reinstall → clean up loop that power users hit constantly. If the shared runtime took care of the common stuff, each session would only need to install its unique dependencies.

Alternative Solutions

Currently using the persistent data directory workaround (persisting node_modules in a plugin's persistent dir and only reinstalling when package.json changes). This helps per-plugin but doesn't address duplication across sessions. The other option is just hitting "clean up" on the disk warning regularly, which triggers the reinstall loop.

Priority

High - Significant impact on productivity

Feature Category

Configuration and settings

Use Case Example

  1. I open Cowork and start a session for my AXOL deal pipeline (scraping + data processing)
  2. I open a second session for a health dashboard (chart/visualization libraries)
  3. I open a third session for scheduled tasks (various npm/pip deps)
  4. Each session independently installs Node, Python, and overlapping npm/pip packages -- ~381 MB each
  5. Within a few days the 9.7 GB disk is full and I get a "workspace disk nearly full" warning
  6. I hit "clean up" which wipes working files from inactive sessions
  7. Next time I open those sessions, they reinstall all the same packages from scratch
  8. Repeat every few days

With shared package caching, steps 4-8 would be eliminated. Common packages would already be available and each session would only install its unique deps.

Additional Context

This is specifically about Cowork mode in the Claude Desktop app, not Claude Code CLI. The 9.7 GB workspace disk quota is shared across all active Cowork sessions. Power users running multiple persistent workflows (deal pipelines, dashboards, scheduled tasks) hit the ceiling regularly.

Anthropic support confirmed this should be filed as a feature request and directed me here.

extent analysis

TL;DR

Implementing a platform-level shared package caching mechanism can help reduce the disk footprint of concurrent Cowork sessions by eliminating duplicate installations of common base packages.

Guidance

  • Identify the most commonly used packages across Cowork sessions to determine the optimal set of packages to cache.
  • Consider implementing a caching mechanism that stores packages in a centralized location, accessible by all sessions, to avoid duplication.
  • Evaluate the feasibility of integrating the proposed solution with the existing "clean up" option to prevent the reinstall loop.
  • Assess the potential impact of shared package caching on session startup times and overall system performance.

Example

No code snippet is provided as the issue focuses on a high-level feature request rather than a specific implementation detail.

Notes

The proposed solution assumes that the Claude Desktop app has the necessary infrastructure to support shared package caching. Additionally, the implementation details of the caching mechanism are not specified, and further investigation is required to determine the best approach.

Recommendation

Apply a workaround, such as the persistent data directory workaround, until a shared package caching mechanism can be implemented, as it can help mitigate the issue for individual plugins, but not across sessions.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING