microsoft/hve-core

Public

mirrored fromhttps://github.com/microsoft/hve-coreAvailable

CodeCommitsIssuesPull requestsActionsInsightsSecurity
hve-core-v2.3.6

Branches

Tags

  • No tags available.
0Branches0Tags
Go to file
Add file
Code

Clone

HTTPS

Download ZIP

docs/getting-started/methods/peer-clone.md

183lines · modecode

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