microsoft/hve-core
Publicmirrored fromhttps://github.com/microsoft/hve-coreAvailable
docs/getting-started/methods/peer-clone.md
205lines · modecode
| 1 | --- |
| 2 | title: Peer Directory Clone Installation |
| 3 | description: Install HVE Core as a sibling directory for local VS Code development |
| 4 | sidebar_position: 4 |
| 5 | author: Microsoft |
| 6 | ms.date: 2026-03-10 |
| 7 | ms.topic: how-to |
| 8 | keywords: |
| 9 | - peer directory |
| 10 | - installation |
| 11 | - github copilot |
| 12 | - local development |
| 13 | estimated_reading_time: 5 |
| 14 | --- |
| 15 | |
| 16 | Peer Directory Clone places HVE Core as a sibling folder next to your project. This is the simplest method for developers working with local VS Code without devcontainers. |
| 17 | |
| 18 | ## When to Use This Method |
| 19 | |
| 20 | ✅ **Use this when:** |
| 21 | |
| 22 | * You're using local VS Code (no devcontainer) |
| 23 | * You're working solo on a project |
| 24 | * You want the simplest possible setup |
| 25 | * You're developing or testing HVE Core itself |
| 26 | |
| 27 | ❌ **Consider alternatives when:** |
| 28 | |
| 29 | * You use devcontainers → [Git-Ignored Folder](git-ignored.md) or [Mounted Directory](mounted.md) |
| 30 | * You use Codespaces → [GitHub Codespaces](codespaces.md) |
| 31 | * Your team needs version control → [Submodule](submodule.md) |
| 32 | * You need paths that work everywhere → [Multi-Root Workspace](multi-root.md) |
| 33 | |
| 34 | ## How It Works |
| 35 | |
| 36 | HVE Core is cloned into a sibling directory. Your project's VS Code settings reference it using relative paths. |
| 37 | |
| 38 | ```text |
| 39 | projects/ |
| 40 | ├── my-project/ # Your project |
| 41 | │ └── .vscode/ |
| 42 | │ └── settings.json # Points to ../hve-core |
| 43 | │ |
| 44 | └── hve-core/ # Sibling directory |
| 45 | └── .github/ |
| 46 | ├── agents/ |
| 47 | ├── prompts/ |
| 48 | └── instructions/ |
| 49 | ``` |
| 50 | |
| 51 | ## Quick Start |
| 52 | |
| 53 | Install the flagship HVE Core [VS Code extension](https://marketplace.visualstudio.com/items?itemName=ise-hve-essentials.hve-core) for the fastest setup. For guided setup with installation method selection and MCP configuration, install the [HVE Core Installer](https://marketplace.visualstudio.com/items?itemName=ise-hve-essentials.hve-installer) extension and ask any agent "help me customize hve-core installation". Use the manual steps below for direct configuration. |
| 54 | |
| 55 | ## Manual Setup |
| 56 | |
| 57 | ### Step 1: Clone HVE Core |
| 58 | |
| 59 | Open a terminal in your project's parent directory: |
| 60 | |
| 61 | ```bash |
| 62 | # Navigate to parent of your project |
| 63 | cd /path/to/projects |
| 64 | |
| 65 | # Clone HVE Core as a sibling |
| 66 | git clone https://github.com/microsoft/hve-core.git |
| 67 | ``` |
| 68 | |
| 69 | Your directory structure should now look like: |
| 70 | |
| 71 | ```text |
| 72 | projects/ |
| 73 | ├── my-project/ |
| 74 | └── hve-core/ |
| 75 | ``` |
| 76 | |
| 77 | ### Step 2: Update VS Code Settings |
| 78 | |
| 79 | Create or update `.vscode/settings.json` in your project: |
| 80 | |
| 81 | ```json |
| 82 | { |
| 83 | "chat.agentFilesLocations": { |
| 84 | "../hve-core/.github/agents/ado": true, |
| 85 | "../hve-core/.github/agents/data-science": true, |
| 86 | "../hve-core/.github/agents/design-thinking": true, |
| 87 | "../hve-core/.github/agents/github": true, |
| 88 | "../hve-core/.github/agents/project-planning": true, |
| 89 | "../hve-core/.github/agents/hve-core": true, |
| 90 | "../hve-core/.github/agents/hve-core/subagents": true, |
| 91 | "../hve-core/.github/agents/security": true |
| 92 | }, |
| 93 | "chat.promptFilesLocations": { |
| 94 | "../hve-core/.github/prompts/ado": true, |
| 95 | "../hve-core/.github/prompts/design-thinking": true, |
| 96 | "../hve-core/.github/prompts/github": true, |
| 97 | "../hve-core/.github/prompts/hve-core": true, |
| 98 | "../hve-core/.github/prompts/security": true |
| 99 | }, |
| 100 | "chat.instructionsFilesLocations": { |
| 101 | "../hve-core/.github/instructions/ado": true, |
| 102 | "../hve-core/.github/instructions/coding-standards": true, |
| 103 | "../hve-core/.github/instructions/design-thinking": true, |
| 104 | "../hve-core/.github/instructions/github": true, |
| 105 | "../hve-core/.github/instructions/hve-core": true, |
| 106 | "../hve-core/.github/instructions/shared": true |
| 107 | }, |
| 108 | "chat.agentSkillsLocations": { |
| 109 | "../hve-core/.github/skills": true, |
| 110 | "../hve-core/.github/skills/shared": true |
| 111 | } |
| 112 | } |
| 113 | ``` |
| 114 | |
| 115 | ### Step 3: Validate Installation |
| 116 | |
| 117 | Verify HVE Core directories are accessible: |
| 118 | |
| 119 | ```bash |
| 120 | ls ../hve-core/.github/agents |
| 121 | ``` |
| 122 | |
| 123 | You should see `.agent.md` files. Then validate in VS Code: |
| 124 | |
| 125 | 1. Reload VS Code window (`Ctrl+Shift+P` → "Developer: Reload Window") |
| 126 | 2. Open GitHub Copilot Chat (`Ctrl+Alt+I`) |
| 127 | 3. Click the agent picker dropdown |
| 128 | 4. Verify HVE Core agents appear (task-planner, task-researcher, prompt-builder) |
| 129 | |
| 130 | ## Updating HVE Core |
| 131 | |
| 132 | To get the latest version: |
| 133 | |
| 134 | ```bash |
| 135 | cd ../hve-core |
| 136 | git pull |
| 137 | ``` |
| 138 | |
| 139 | No VS Code restart required. Changes take effect immediately. |
| 140 | |
| 141 | ## Troubleshooting |
| 142 | |
| 143 | ### Agents Not Appearing |
| 144 | |
| 145 | #### Check the relative path |
| 146 | |
| 147 | ```bash |
| 148 | # From your project directory |
| 149 | ls ../hve-core/.github/agents |
| 150 | ``` |
| 151 | |
| 152 | If the path doesn't resolve, verify: |
| 153 | |
| 154 | 1. HVE Core is cloned at the correct location |
| 155 | 2. Your terminal is in your project directory |
| 156 | 3. The relative path in settings.json is correct |
| 157 | |
| 158 | #### Check VS Code settings |
| 159 | |
| 160 | 1. Open Command Palette (`Ctrl+Shift+P`) |
| 161 | 2. Type "Preferences: Open User Settings (JSON)" |
| 162 | 3. Verify no conflicting settings override your workspace settings |
| 163 | |
| 164 | ### Path Breaks After Moving Project |
| 165 | |
| 166 | Relative paths break if your project moves. Options: |
| 167 | |
| 168 | 1. Re-clone HVE Core next to the new location |
| 169 | 2. Update settings.json with the new relative path |
| 170 | 3. Switch to [Multi-Root Workspace](multi-root.md) for portable paths |
| 171 | |
| 172 | ### Doesn't Work in Devcontainer |
| 173 | |
| 174 | Peer directory clone doesn't work in devcontainers because the container can't access files outside the mounted workspace. |
| 175 | |
| 176 | #### Solutions |
| 177 | |
| 178 | * Use [Git-Ignored Folder](git-ignored.md) for self-contained installation |
| 179 | * Use [Mounted Directory](mounted.md) to share HVE Core across projects |
| 180 | * Use [Multi-Root Workspace](multi-root.md) for the most portable solution |
| 181 | |
| 182 | ## Limitations |
| 183 | |
| 184 | | Aspect | Status | |
| 185 | |------------------|--------------------------------------| |
| 186 | | Devcontainers | ❌ Not supported | |
| 187 | | Codespaces | ❌ Not supported | |
| 188 | | Team sharing | ⚠️ Each developer clones separately | |
| 189 | | Portable paths | ⚠️ Breaks if project moves | |
| 190 | | Version pinning | ⚠️ Manual (use git checkout) | |
| 191 | | Setup complexity | ✅ Very simple | |
| 192 | | Update process | ✅ Just git pull | |
| 193 | |
| 194 | ## Next Steps |
| 195 | |
| 196 | * [Your First Workflow](../first-workflow.md) - Try HVE Core with a real task |
| 197 | * [Multi-Root Workspace](multi-root.md) - Upgrade to portable paths |
| 198 | * [Submodule](submodule.md) - Add version control for teams |
| 199 | |
| 200 | --- |
| 201 | |
| 202 | <!-- markdownlint-disable MD036 --> |
| 203 | *🤖 Crafted with precision by ✨Copilot following brilliant human instruction, |
| 204 | then carefully refined by our team of discerning human reviewers.* |
| 205 | <!-- markdownlint-enable MD036 --> |
| 206 | |