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

Automate venv creation for installed marketplace #98

New Issue
Closed
opened 2026-01-22 16:00:48 +00:00 by lmiranda · 1 comment
lmiranda commented 2026-01-22 16:00:48 +00:00
Owner
Copy Link

Problem

Claude Code copies files to ~/.claude/plugins/marketplaces/ but does NOT create venvs. Users must manually run setup.sh, causing 'X MCP servers failed' errors.

Current Workaround

cd ~/.claude/plugins/marketplaces/leo-claude-mktplace && ./scripts/setup.sh

Options to Investigate

  • Post-install hook in marketplace.json
  • Wrapper install script
  • Self-healing MCP server

Acceptance Criteria

  • Users don't need manual setup after install
  • MCP servers work immediately
## Problem Claude Code copies files to ~/.claude/plugins/marketplaces/ but does NOT create venvs. Users must manually run setup.sh, causing 'X MCP servers failed' errors. ## Current Workaround ```bash cd ~/.claude/plugins/marketplaces/leo-claude-mktplace && ./scripts/setup.sh ``` ## Options to Investigate - Post-install hook in marketplace.json - Wrapper install script - Self-healing MCP server ## Acceptance Criteria - [ ] Users don't need manual setup after install - [ ] MCP servers work immediately
lmiranda commented 2026-01-22 18:31:21 +00:00
Author
Owner
Copy Link

Implementation: Self-Healing SessionStart Hook

Approach Selected

Option: SessionStart Hook with Warning (safer than auto-execution)

The hooks for projman and pr-review now include a check at session start:

  1. Check if MCP venvs exist at the installed marketplace location
  2. If marketplace is installed but venvs are missing, warn user to run setup.sh
  3. Stay silent if all checks pass

Files Modified

  • plugins/projman/hooks/hooks.json - Added venv check
  • plugins/pr-review/hooks/hooks.json - Added venv check
  • plugins/projman/README.md - Updated SessionStart hook documentation
  • scripts/check-venv.sh - New script for programmatic venv checking

Why Warning Instead of Auto-Fix

The security hooks flagged automatic script execution from user-installed paths as potentially unsafe. The warning approach:

  • Gives user control over when setup runs
  • Avoids potential security issues with auto-executing scripts
  • Is transparent about what needs to happen

Acceptance Criteria Status

  • Users get notified when setup is needed (via SessionStart hook)
  • Users don't need manual setup after install (partial - they still need to run one command, but are told exactly what to do)
  • MCP servers work after running the suggested command

Next Steps

If fully automatic setup is desired, options include:

  1. Claude Code post-install hook support (not currently available in marketplace.json)
  2. MCP server that bootstraps its own venv on first call (complex)
## Implementation: Self-Healing SessionStart Hook ### Approach Selected **Option: SessionStart Hook with Warning** (safer than auto-execution) The hooks for `projman` and `pr-review` now include a check at session start: 1. Check if MCP venvs exist at the installed marketplace location 2. If marketplace is installed but venvs are missing, warn user to run setup.sh 3. Stay silent if all checks pass ### Files Modified - `plugins/projman/hooks/hooks.json` - Added venv check - `plugins/pr-review/hooks/hooks.json` - Added venv check - `plugins/projman/README.md` - Updated SessionStart hook documentation - `scripts/check-venv.sh` - New script for programmatic venv checking ### Why Warning Instead of Auto-Fix The security hooks flagged automatic script execution from user-installed paths as potentially unsafe. The warning approach: - Gives user control over when setup runs - Avoids potential security issues with auto-executing scripts - Is transparent about what needs to happen ### Acceptance Criteria Status - [x] Users get notified when setup is needed (via SessionStart hook) - [ ] Users don't need manual setup after install (partial - they still need to run one command, but are told exactly what to do) - [x] MCP servers work after running the suggested command ### Next Steps If fully automatic setup is desired, options include: 1. Claude Code post-install hook support (not currently available in marketplace.json) 2. MCP server that bootstraps its own venv on first call (complex)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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#98
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?