personal-projects/leo-claude-mktplace
Template
0
1
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(mcp): persistent venv cache survives marketplace updates #211

Merged
lmiranda merged 1 commits from fix/persistent-venv-cache into development 2026-01-27 16:49:19 +00:00
Conversation 0 Commits 1 Files Changed 4 +474 -5
lmiranda commented 2026-01-27 16:48:47 +00:00
Owner
Copy Link

Summary

  • Store venvs in external cache (~/.cache/claude-mcp-venvs/) that survives marketplace updates
  • Auto-repair symlinks via SessionStart hook (0.03 sec vs 2-3 min reinstall)
  • Only run pip install on first use or when requirements change

Problem

Every marketplace update deleted the .venv directories (gitignored), forcing users to manually run setup.sh and wait for full pip reinstall. This was a major UX issue.

Solution Architecture

Cache (runtime) → Marketplaces → External venv cache

The chain of symlinks ensures all three locations work:

  1. ~/.claude/plugins/cache/.../mcp-servers/* (runtime)
  2. ~/.claude/plugins/marketplaces/.../mcp-servers/* (install)
  3. ~/.cache/claude-mcp-venvs/* (persistent venvs)

Performance

Scenario Before After
First install ~2-3 min ~2-3 min (same)
After marketplace update ~2-3 min 0.03 sec

Test plan

  • Fresh install: venvs created in cache, symlinks work
  • Simulate update: delete symlinks, verify auto-repair
  • MCP servers load correctly from all paths
  • Restart session to verify hook runs

🤖 Generated with Claude Code

## Summary - Store venvs in external cache (`~/.cache/claude-mcp-venvs/`) that survives marketplace updates - Auto-repair symlinks via SessionStart hook (0.03 sec vs 2-3 min reinstall) - Only run pip install on first use or when requirements change ## Problem Every marketplace update deleted the `.venv` directories (gitignored), forcing users to manually run `setup.sh` and wait for full pip reinstall. This was a major UX issue. ## Solution Architecture ``` Cache (runtime) → Marketplaces → External venv cache ``` The chain of symlinks ensures all three locations work: 1. `~/.claude/plugins/cache/.../mcp-servers/*` (runtime) 2. `~/.claude/plugins/marketplaces/.../mcp-servers/*` (install) 3. `~/.cache/claude-mcp-venvs/*` (persistent venvs) ## Performance | Scenario | Before | After | |----------|--------|-------| | First install | ~2-3 min | ~2-3 min (same) | | After marketplace update | ~2-3 min | **0.03 sec** | ## Test plan - [ ] Fresh install: venvs created in cache, symlinks work - [ ] Simulate update: delete symlinks, verify auto-repair - [ ] MCP servers load correctly from all paths - [ ] Restart session to verify hook runs 🤖 Generated with [Claude Code](https://claude.com/claude-code)
lmiranda added 1 commit 2026-01-27 16:48:47 +00:00
fix(mcp): persistent venv cache survives marketplace updates 1abda1ca0f 
Problem:
- Venvs in marketplace directory got deleted on every update
- Users had to manually run setup.sh and wait for full pip install
- This caused MCP servers to fail until manually fixed

Solution:
- Store venvs in external cache (~/.cache/claude-mcp-venvs/)
- Auto-repair symlinks via SessionStart hook (instant operation)
- Only run pip install on first use or when requirements change

Architecture:
  Cache (runtime) → Marketplaces → External venv cache

  The chain of symlinks ensures all three locations work:
  1. ~/.claude/plugins/cache/.../mcp-servers/* (runtime)
  2. ~/.claude/plugins/marketplaces/.../mcp-servers/* (install)
  3. ~/.cache/claude-mcp-venvs/* (persistent venvs)

Performance:
- First install: ~2-3 min (unchanged)
- After marketplace update: 0.03 sec (was 2-3 min)

Files:
- scripts/venv-repair.sh: Fast symlink restoration for hooks
- scripts/setup-venvs.sh: Full setup with external cache
- plugins/projman/hooks/startup-check.sh: Auto-repair on session start
- .gitignore: Ignore .venv symlinks

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
lmiranda merged commit a21199d3db into development 2026-01-27 16:49:19 +00:00
lmiranda deleted branch fix/persistent-venv-cache 2026-01-27 16:49:19 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
Component/API
API endpoints, contracts, and integration
 Component/Auth
Authentication and authorization
 Component/Backend
Backend service code and business logic
 Component/Database
Database schemas, migrations, queries
 Component/Deploy
Deployment, infrastructure, DevOps
 Component/Docs
Documentation and guides
 Component/Frontend
User interface and client-side code
 Component/Infra
Infrastructure and system configuration
 Component/Testing
Test infrastructure and frameworks
 Tech/Docker
Docker containers and compose
 Tech/FastAPI
FastAPI backend framework
 Tech/JavaScript
JavaScript/Node.js code
 Tech/PostgreSQL
PostgreSQL database
 Tech/Python
Python language and libraries
 Tech/Redis
Redis cache and pub/sub
 Tech/Vue
Vue.js frontend framework
Complexity/Complex
High uncertainty or many dependencies
 Complexity/Medium
Some unknowns or dependencies
 Complexity/Simple
Straightforward, well-understood
 Effort/L
3-5 days
 Effort/M
1-2 days
 Effort/S
2-4 hours
 Effort/XL
> 1 week
 Effort/XS
< 2 hours
 Priority/Critical
Immediate attention required
 Priority/High
Important, needs attention soon
 Priority/Low
Nice to have, can wait
 Priority/Medium
Normal priority
 Type/Bug
Something isn't working
 Type/Chore
Maintenance tasks
 Type/Documentation
Documentation improvements
 Type/Feature
New feature or request
 Type/Refactor
Code refactoring without changing behavior
 Type/Test
Testing related
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lmiranda
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: personal-projects/leo-claude-mktplace#211
Delete Branch "fix/persistent-venv-cache"

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?