VS Code Extension Installation
VS Code Extension installation provides HVE Core directly through the VS Code Marketplace. This is the simplest zero-configuration method that works across all environments.
When to Use This Method
✅ Use this when:
- You want the simplest possible setup
- You don't need to customize HVE Core components
- You work across different machines and environments
- You want automatic updates through VS Code
- You prefer marketplace-managed extensions
- You want a clean, zero-configuration setup
❌ Consider alternatives when:
- You need to customize custom agents, prompts, or instructions → Peer Clone or Git-Ignored
- Your team needs to version control HVE Core → Submodule
- You're contributing to HVE Core development → Peer Clone
- You need to test pre-release versions → Multi-Root Workspace
How It Works
The extension packages all HVE Core components (chat agents, prompts, instructions) as a standard VS Code extension. Once installed, all components are immediately available without any additional configuration.
VS Code Extension System
├── Extension installed via marketplace
│ ├── .github/agents/ # All chat agents
│ ├── .github/prompts/ # All prompt templates
│ ├── .github/instructions/ # All coding guidelines
│ └── .github/skills/ # All skill packages
└── Only optional workspace configuration needed!
Quick Start
Option 1: Install from Marketplace (Recommended)
- Open VS Code
- Go to Extensions view (
Ctrl+Shift+X) - Search for "HVE Core"
- Click Install
Or click here: Install HVE Core Extension
Option 2: Install from Command Line
code --install-extension ise-hve-essentials.hve-core
Option 3: Install Using VS Code Insiders
code-insiders --install-extension ise-hve-essentials.hve-core
Verification
After installation, verify everything works:
- Open GitHub Copilot Chat (
Ctrl+Alt+I) - Click the agent picker dropdown
- Verify HVE Core agents appear:
- task-planner
- task-researcher
- task-implementor
- pr-review
- adr-creation
Post-Installation (Optional)
These optional configurations enhance your HVE Core experience but are not required for basic functionality.
Update Your .gitignore
HVE Core agents create ephemeral workflow artifacts in a .copilot-tracking/ folder within your project. Add this line to your project's .gitignore:
.copilot-tracking/
This applies even when using the extension. The folder is created in your project directory when you use agents like task-researcher or pr-review. See the installation guide for details on what gets stored there.
What's Included
The extension provides all HVE Core components:
| Component | Examples |
|---|---|
| Chat Agents | task-planner, pr-review, adr-creation |
| Prompts | git-commit, pull-request, ado-create-pr |
| Instructions | markdown, python-script, commit-message |
| Skills | pr-reference, video-to-gif |
Updating
The extension updates automatically through VS Code's extension system:
- Extensions update automatically when new versions are released (default)
- Open Extensions view → find "HVE Core" → click Update for manual updates
- Right-click the extension → "Switch to Pre-Release Version" for pre-release access
Comparison with Other Methods
Pros ✅
| Advantage | Detail |
|---|---|
| Zero configuration | No workspace settings or file cloning required |
| Works everywhere | Local, devcontainers, Codespaces, any environment |
| Automatic updates | VS Code manages updates automatically |
| No repository pollution | Nothing added to your project |
| Instant availability | Works immediately after installation |
| No manual setup | No scripts to run or paths to configure |
| Marketplace managed | Centralized distribution and versioning |
Cons ❌
| Limitation | Detail |
|---|---|
| No customization | Can't modify custom agents, prompts, or instructions |
| Extension updates only | Testing development versions requires extra setup |
| No version pinning | Uses latest version (or opt into pre-release) |
| No team control | Can't enforce specific versions across team |
| Limited flexibility | Can't combine with custom local modifications |
Common Scenarios
Scenario 1: Quick Personal Use
Goal: Start using HVE Core immediately without setup
Solution: Install the extension from marketplace
Steps
- Install extension from marketplace
- Start using
task-plannerand other agents - That's it!
Scenario 2: Multi-Machine Developer
Goal: Use HVE Core consistently across laptop, desktop, and Codespaces
Solution: Install extension on all machines via Settings Sync
Steps
- Enable Settings Sync in VS Code
- Install extension on one machine
- Extensions automatically sync to other devices
Scenario 3: Team Adoption
Goal: Get entire team using HVE Core quickly
Solution: Share extension link and install instructions
Steps
- Share marketplace link with team
- Team members install extension
- Everyone has consistent experience immediately
Scenario 4: Want to Customize Later
Goal: Start with extension, add customization as needs grow
Solution: Layer in the installer skill for MCP, installation method guidance, and agent bundle selection; migrate to clone only for full artifact control
Steps
- Start with the HVE Core extension for the flagship RPI workflow
- When you need MCP configuration, a different installation method, or the complete artifact library, install the HVE Core Installer extension and ask any agent "help me customize hve-core installation"
- When you need to modify prompts, instructions, or skills directly, uninstall extensions and follow a clone-based method
Troubleshooting
Extension Not Appearing
Check extension is installed
- Open Extensions view (
Ctrl+Shift+X) - Search "HVE Core"
- Verify "Installed" badge appears
Reload VS Code
- Command Palette (
Ctrl+Shift+P) - "Developer: Reload Window"
Agents Not Showing in Copilot Chat
Verify GitHub Copilot is active
- Check Copilot icon in status bar
- Sign in if needed
Check extension status
- Extensions view → "HVE Core"
- Verify no errors shown
- Click "Show Extension Output" if issues
Conflicting Installation Methods
If you have both extension and manual installation (like Peer Clone):
Problem: Duplicate agents appearing
Solution: Choose one method:
- Keep extension: Remove manual installation (delete cloned folder, remove workspace settings)
- Keep manual: Uninstall extension
Update Not Appearing
Force check for updates
- Extensions view → ⋯ (More Actions)
- "Check for Extension Updates"
Manually update
- Extensions view → Find "HVE Core"
- Click "Update" button
Need MCP Configuration or Guided Setup?
The extension provides the flagship RPI workflow and core artifacts but does not include MCP server configuration or artifacts from other collections. If you need auto-configured MCP servers, the complete artifact library, or guided setup for any installation method, the HVE Core Installer extension provides the installer skill:
- Install the HVE Core Installer extension
- Ask any agent: "help me customize hve-core installation"
- The installer skill guides you through setup method selection and MCP configuration
| Capability | HVE Core Extension | Installer Skill |
|---|---|---|
| Flagship collection (RPI) | ✅ | ✅ (via clone) |
| All collections (hve-core-all) | ❌ | ✅ (via clone) |
| MCP auto-configuration | ❌ | ✅ 4 curated servers |
| Agent bundle selection | ❌ (flagship only) | ✅ (clone methods only) |
| Installation method guidance | ❌ | ✅ peer clone, submodule, etc. |
NOTE
The installer is a skill that works within any agent conversation. There is no separate "installer agent" in the agent picker. The installer extension packages the skill for VS Code distribution.
Migration Guide
From Manual Installation to Extension
If you're currently using manual methods like Peer Clone:
- Delete HVE Core paths from
.vscode/settings.json - Optionally remove the hve-core clone if no longer needed
- Install the extension following the Quick Start above
- Verify agents appear in Copilot Chat
From Extension to Manual Installation
If you need customization:
- Uninstall the extension from Extensions view
- Follow a manual method such as Peer Clone for local customization
- Customize agents, prompts, or instructions as needed
Limitations
| Aspect | Status |
|---|---|
| Customization | ❌ Cannot modify components |
| Version control | ⚠️ Extension updates only, no git control |
| Team enforcement | ⚠️ Each member installs independently |
| Dev/testing | ⚠️ Pre-release channel only, not custom branches |
| Portable paths | ✅ Works everywhere |
| Setup complexity | ✅ Simplest possible |
| Disk usage | ✅ Single installation across all projects |
Next Steps
- Your First Workflow - Try HVE Core with a real task
- Multi-Root Workspace - Combine extension with custom components
- Peer Clone - Switch to customizable installation
🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.