In this article
Setup Methods
HVE Core installs several ways. The Copilot Plugin is the starting point: it carries every agent, skill, and instruction and works in VS Code and Copilot CLI. The other methods suit teams that pin a version, customize components, or work in containers. For MCP setup or a repository copy, ask an agent to use the included hve-core-installer skill.
Available Methods
| Method | Best For | How Copilot Loads It | Complexity |
|---|---|---|---|
| Copilot Plugin | Most people, in VS Code or Copilot CLI | Plugin | Low |
| VS Code Extension | Marketplace installs with release channels | VS Code extension forwarding | Low |
| Git Submodule | Pinned versions for a team | Repository settings | Medium |
| Git-Ignored Clone | Local-only customization | Plugin from source or repository settings | Low |
| Peer Clone | Side-by-side development and contribution | Plugin from source | Medium |
| Multi-Root Workspace | Editing HVE Core next to your project | Plugin from source | Medium |
| Mounted Workspace | Sharing one host copy with containers | Repository settings | Medium |
| Codespaces | Cloud-based development | Repository default or settings | Low |
To offer HVE Core to everyone who opens a repository without copying any files, commit the plugin defaults described in Offer the Plugin to Your Team.
Which Method Should You Choose?
Start with the Copilot Plugin. Move to a Git Submodule when your team needs a pinned, version-controlled copy, or copy HVE Core into your repository when it should own and customize the files. Use one method at a time: Copilot keeps copies that arrive by different routes, and each agent then appears more than once.
Comparing Setup Methods puts every method side by side. See the Getting Started guide for the recommended onboarding sequence.
🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.