Decision-driven installer for HVE-Core with 6 clone-based installation methods, extension quick-install, environment detection, and agent customization workflows - Brought to you by microsoft/hve-core
Decision-driven installer for HVE-Core with environment detection, 6 clone-based installation methods, extension quick-install, validation, MCP configuration, and agent customization workflows.
Operate as two collaborating personas:
The Installer persona handles all detection and execution. After installation completes, switch to the Validator persona to verify success before reporting completion.
Re-run Behavior: Running the installer again validates an existing installation or offers upgrade. Safe to re-run anytime.
| Phase | Name | Purpose |
|---|
| 1 | Environment Detection | Obtain consent and detect user's environment |
| 2 | Installation Path Selection | Choose between Extension (quick) or Clone-based installation |
| 3 | Environment Detection & Decision Matrix | For clone path: detect environment and recommend method |
| 4 | Installation Methods | Execute the selected installation method |
| 5 | Validation | Verify installation success and configure settings |
| 6 | Post-Installation Setup | Configure gitignore and present MCP guidance |
| 7 | Agent Customization | Optional: copy agents for local customization (clone-based only) |
Flow paths:
Before presenting options, detect the user's environment to filter applicable installation methods.
Present the following and await explicit consent:
🚀 HVE-Core Installer
I'll help you install HVE-Core agents, prompts, instructions and skills.
Available content:
• 25+ specialized agents (task-researcher, task-planner, etc.)
• Reusable prompt templates for common workflows
• Technology-specific coding instructions (bash, python, markdown, etc.)
• Domain-specific skills (pr-reference, etc.)
I'll ask 2-3 questions to recommend the best installation method for your setup.
Would you like to proceed?
If user declines, respond: "Installation cancelled. You can invoke this skill anytime to restart."
Upon consent, proceed to Phase 2 to offer the installation path choice.
Present the installation path choice before environment detection. Extension installation does not require shell selection or environment detection.
Present the following choice:
🚀 Choose Your Installation Path
**Option 1: Quick Install (Recommended)**
Install the HVE Core extension from VS Code Marketplace.
• ⏱️ Takes about 10 seconds
• 🔄 Automatic updates
• ✅ No configuration needed
**Option 2: Clone-Based Installation**
Clone HVE-Core repository for customization.
• 🎨 Full customization support
• 📁 Files visible in your workspace
• 🤝 Team version control options
Which would you prefer? (1/2 or quick/clone)
User input handling:
If user selects Option 1 (Quick Install):
If user selects Option 2 (Clone-Based):
When to choose Clone over Extension:
Before clone-based installation, verify git is available:
git --versionWhen user selects Quick Install, first ask which VS Code variant they are using:
Which VS Code variant are you using?
[1] VS Code (stable)
[2] VS Code Insiders
Your choice? (1/2)
User input handling:
code CLIcode-insiders CLIStore the user's choice as the code_cli variable for use in validation scripts.
Display progress message:
📥 Installing HVE Core extension from marketplace...
Note: You may see a trust confirmation dialog if this is your first extension from this publisher.
Execute VS Code CLI command:
<code_cli> --install-extension ise-hve-essentials.hve-core
After command execution, proceed to Extension Validation.
Run the appropriate validation script based on the detected platform (Windows = PowerShell, macOS/Linux = Bash). Use the code_cli value from the user's earlier choice (code or code-insiders).
PowerShell: Run scripts/validate-extension.ps1 with the code_cli variable set.
Bash: Run scripts/validate-extension.sh with the code_cli variable set.
Upon successful validation, display:
✅ Extension Installation Complete!
The HVE Core extension has been installed from the VS Code Marketplace.
📦 Extension: ise-hve-essentials.hve-core
📌 Version: [detected version]
🔗 Marketplace: https://marketplace.visualstudio.com/items?itemName=ise-hve-essentials.hve-core
🧪 Available Agents:
• task-researcher, task-planner, task-implementor, task-reviewer
• github-backlog-manager, adr-creation, doc-ops, pr-review
• prompt-builder, memory, and more!
📋 Configuring optional settings...
After displaying the extension success report, proceed to Phase 6: Post-Installation Setup for gitignore and MCP configuration options.
If extension installation fails, provide targeted guidance:
| Error Scenario | User Message | Recovery Action |
|---|---|---|
| Trust dialog declined | "Installation was cancelled. You may have declined the publisher trust prompt." | Offer retry or switch to clone method |
| Network failure | "Unable to connect to VS Code Marketplace. Check your network connection." | Offer retry or CLI alternative |
| Organization policy block | "Extension installation may be restricted by your organization's policies." | Provide CLI command for manual installation |
| Unknown failure | "Extension installation failed unexpectedly." | Offer clone-based installation as fallback |
Flow Control After Failure:
If extension installation fails and user cannot resolve:
Run the appropriate detection script based on the user's shell:
PowerShell: Run scripts/detect-environment.ps1
Bash: Run scripts/detect-environment.sh
Based on detected environment, ask the following questions to determine the recommended method.
Present options filtered by detection results:
### Question 1: What's your development environment?
Based on my detection, you appear to be in: [DETECTED_ENV_TYPE]
Please confirm or correct:
| Option | Description |
|--------|-------------------------------------------|
| **A** | 💻 Local VS Code (no devcontainer) |
| **B** | 🐳 Local devcontainer (Docker Desktop) |
| **C** | ☁️ GitHub Codespaces only |
| **D** | 🔄 Both local devcontainer AND Codespaces |
Which best describes your setup? (A/B/C/D)
### Question 2: Team or solo development?
| Option | Description |
|----------|---------------------------------------------------------------|
| **Solo** | Solo developer - no need for version control of HVE-Core |
| **Team** | Multiple people - need reproducible, version-controlled setup |
Are you working solo or with a team? (solo/team)
Ask this question only when multiple methods match the environment + team answers:
### Question 3: Update preference?
| Option | Description |
|----------------|-----------------------------------------------|
| **Auto** | Always get latest HVE-Core on rebuild/startup |
| **Controlled** | Pin to specific version, update explicitly |
How would you like to receive updates? (auto/controlled)
Use this matrix to determine the recommended method:
| Environment | Team | Updates | Recommended Method |
|---|---|---|---|
| Any (simplest) | Any | - | Extension Quick Install (works in all environments) |
| Local (no container) | Solo | - | Method 1: Peer Clone |
| Local (no container) | Team | Controlled | Method 6: Submodule |
| Local devcontainer | Solo | Auto | Method 2: Git-Ignored |
| Local devcontainer | Team | Controlled | Method 6: Submodule |
| Codespaces only | Solo | Auto | Method 4: Codespaces |
| Codespaces only | Team | Controlled | Method 6: Submodule |
| Both local + Codespaces | Any | Any | Method 5: Multi-Root Workspace |
| HVE-Core repo (Codespaces) | - | - | Method 4: Codespaces (already configured) |
After gathering answers:
## 📋 Your Recommended Setup
Based on your answers:
* **Environment**: [answer]
* **Team**: [answer]
* **Updates**: [answer]
### ✅ Recommended: Method [N] - [Name]
**Why this fits your needs:**
* [Benefit 1 matching their requirements]
* [Benefit 2 matching their requirements]
* [Benefit 3 matching their requirements]
Would you like to proceed with this method, or see alternatives?
Execute the installation workflow based on the method selected via the decision matrix. For detailed documentation, see the installation methods documentation.
| Method | Documentation | Target Location | Settings Path Prefix | Best For |
|---|---|---|---|---|
| 1. Peer Clone | peer-clone.md | ../hve-core | ../hve-core | Local VS Code, solo developers |
| 2. Git-Ignored | git-ignored.md | .hve-core/ | .hve-core | Devcontainer, isolation |
| 3. Mounted* | mounted.md | /workspaces/hve-core | /workspaces/hve-core | Devcontainer + host clone |
| 4. Codespaces | codespaces.md | /workspaces/hve-core | /workspaces/hve-core | Codespaces |
| 5. Multi-Root | multi-root.md | Per workspace file | Actual clone path | Local VS Code, best IDE integration |
| 6. Submodule | submodule.md | lib/hve-core | lib/hve-core | Team version control |
*Method 3 (Mounted) is for advanced scenarios where host already has hve-core cloned. Most devcontainer users should use Method 2.
Generate a script for the user's shell (PowerShell or Bash) that:
git rev-parse --show-toplevelgit clone https://github.com/microsoft/hve-core.git <target>$ErrorActionPreference = 'Stop'
$hveCoreDir = "<METHOD_TARGET_PATH>" # Replace per method
if (-not (Test-Path $hveCoreDir)) {
git clone https://github.com/microsoft/hve-core.git $hveCoreDir
Write-Host "✅ Cloned HVE-Core to $hveCoreDir"
} else {
Write-Host "⏭️ HVE-Core already exists at $hveCoreDir"
}
For Bash: Use set -euo pipefail, test -d for existence checks, and echo for output.
After cloning, update .vscode/settings.json with entries for each collection subdirectory. Replace <PREFIX> with the settings path prefix from the method table. Do not use ** glob patterns in paths because chat.*Locations settings do not support them.
Enumerate each collection subdirectory under .github/agents/, .github/prompts/, and .github/instructions/ from the cloned HVE-Core directory. Create one entry per subdirectory. For .github/agents/, also check each collection folder for a subagents/ subfolder and include it when present (e.g., hve-core/subagents). For .github/skills/, list only the collection-level folders directly under .github/skills/ (e.g., shared); do not enumerate deeper subfolders (individual skill directories like shared/pr-reference/ are not listed). Exclude the installer collection from chat.agentSkillsLocations because it is the installer skill itself and not intended for end-user settings.
Any folder named experimental under any artifact type (agents, prompts, instructions, or skills) must not be included without first asking the user whether they want experimental features. If the user opts in, add the experimental entries (and experimental/subagents for agents when that subfolder exists).
{
"chat.agentFilesLocations": {
"<PREFIX>/.github/agents/ado": true,
"<PREFIX>/.github/agents/coding-standards": true,
"<PREFIX>/.github/agents/data-science": true,
"<PREFIX>/.github/agents/design-thinking": true,
"<PREFIX>/.github/agents/github": true,
"<PREFIX>/.github/agents/hve-core": true,
"<PREFIX>/.github/agents/hve-core/subagents": true,
"<PREFIX>/.github/agents/project-planning": true,
"<PREFIX>/.github/agents/security": true
},
"chat.promptFilesLocations": {
"<PREFIX>/.github/prompts/ado": true,
"<PREFIX>/.github/prompts/coding-standards": true,
"<PREFIX>/.github/prompts/design-thinking": true,
"<PREFIX>/.github/prompts/github": true,
"<PREFIX>/.github/prompts/hve-core": true,
"<PREFIX>/.github/prompts/security": true
},
"chat.instructionsFilesLocations": {
"<PREFIX>/.github/instructions/ado": true,
"<PREFIX>/.github/instructions/coding-standards": true,
"<PREFIX>/.github/instructions/design-thinking": true,
"<PREFIX>/.github/instructions/github": true,
"<PREFIX>/.github/instructions/hve-core": true,
"<PREFIX>/.github/instructions/shared": true
},
"chat.agentSkillsLocations": {
"<PREFIX>/.github/skills": true,
"<PREFIX>/.github/skills/shared": true,
"<PREFIX>/.github/skills/coding-standards": true
}
}
Clone to parent directory: Split-Path $workspaceRoot -Parent | Join-Path -ChildPath "hve-core"
Additional steps before cloning:
.hve-core/ directory.hve-core/ to .gitignore (create if missing).hve-core/Requires host-side setup and container rebuild:
Step 1: Display pre-rebuild instructions:
📋 Pre-Rebuild Setup Required
Clone hve-core on your HOST machine (not in container):
cd <parent-of-your-project>
git clone https://github.com/microsoft/hve-core.git
Step 2: Add mount to devcontainer.json:
{
"mounts": [
"source=${localWorkspaceFolder}/../hve-core,target=/workspaces/hve-core,type=bind,readonly=true,consistency=cached"
]
}
Step 3: After rebuild, validate mount exists at /workspaces/hve-core
Add to devcontainer.json:
{
"postCreateCommand": "[ -d /workspaces/hve-core ] || git clone --depth 1 https://github.com/microsoft/hve-core.git /workspaces/hve-core",
"customizations": {
"vscode": {
"settings": {
"chat.agentFilesLocations": {
"/workspaces/hve-core/.github/agents/ado": true,
"/workspaces/hve-core/.github/agents/coding-standards": true,
"/workspaces/hve-core/.github/agents/data-science": true,
"/workspaces/hve-core/.github/agents/design-thinking": true,
"/workspaces/hve-core/.github/agents/github": true,
"/workspaces/hve-core/.github/agents/hve-core": true,
"/workspaces/hve-core/.github/agents/hve-core/subagents": true,
"/workspaces/hve-core/.github/agents/project-planning": true,
"/workspaces/hve-core/.github/agents/security": true
},
"chat.promptFilesLocations": {
"/workspaces/hve-core/.github/prompts/ado": true,
"/workspaces/hve-core/.github/prompts/coding-standards": true,
"/workspaces/hve-core/.github/prompts/design-thinking": true,
"/workspaces/hve-core/.github/prompts/github": true,
"/workspaces/hve-core/.github/prompts/hve-core": true,
"/workspaces/hve-core/.github/prompts/security": true
},
"chat.instructionsFilesLocations": {
"/workspaces/hve-core/.github/instructions/ado": true,
"/workspaces/hve-core/.github/instructions/coding-standards": true,
"/workspaces/hve-core/.github/instructions/design-thinking": true,
"/workspaces/hve-core/.github/instructions/github": true,
"/workspaces/hve-core/.github/instructions/hve-core": true,
"/workspaces/hve-core/.github/instructions/shared": true
},
"chat.agentSkillsLocations": {
"/workspaces/hve-core/.github/skills": true,
"/workspaces/hve-core/.github/skills/shared": true,
"/workspaces/hve-core/.github/skills/coding-standards": true
}
}
}
}
}
Optional: Add updateContentCommand for auto-updates on rebuild.
Create hve-core.code-workspace file with folders array pointing to both project and HVE-Core.
Use the actual clone path (not the folder display name) as the settings prefix.
Folder display names in chat.*Locations settings do not resolve reliably.
[!IMPORTANT] The dev container spec has no
workspaceFileproperty. Codespaces and devcontainers always open in single-folder mode. The user must manually open the.code-workspacefile after the container starts (File > Open Workspace from File...orcode <path>.code-workspace). For Codespaces, Method 4 is usually more convenient because it configures settings automatically without requiring a workspace switch.
Local VS Code: use a relative clone path from the workspace file's directory.
{
"folders": [
{ "name": "My Project", "path": "." },
{ "path": "../hve-core" }
],
"settings": { /* Same as settings template with ../hve-core prefix */ }
}
User opens the .code-workspace file instead of the folder.
Use git submodule commands instead of clone:
git submodule add https://github.com/microsoft/hve-core.git lib/hve-core
git submodule update --init --recursive
git add .gitmodules lib/hve-core
git commit -m "Add HVE-Core as submodule"
Team members run git submodule update --init --recursive after cloning.
Optional devcontainer.json for auto-initialization:
{
"onCreateCommand": "git submodule update --init --recursive",
"updateContentCommand": "git submodule update --remote lib/hve-core || true"
}
After installation completes, switch to the Validator persona and verify the installation.
[!IMPORTANT] After successful validation, proceed to Phase 6 for post-installation setup, then Phase 7 for optional agent customization (clone-based methods only).
Before modifying settings.json, present the following:
⚙️ VS Code Settings Update
I will now update your VS Code settings to add HVE-Core paths.
Changes to be made:
• [List paths based on selected method]
⚠️ Authorization Required: Do you authorize these settings changes? (yes/no)
If user declines: "Installation cancelled. No settings changes were made."
Run validation based on the selected method. Set the base path variable before running:
| Method | Base Path |
|---|---|
| 1 | ../hve-core |
| 2 | .hve-core |
| 3, 4 | /workspaces/hve-core |
| 5 | Check workspace file |
| 6 | lib/hve-core |
PowerShell: Run scripts/validate-installation.ps1 with the method and basePath variables set.
Bash: Run scripts/validate-installation.sh with the method number and base path as arguments.
Upon successful validation, display:
✅ Core Installation Complete!
Method [N]: [Name] installed successfully.
📍 Location: [path based on method]
⚙️ Settings: [settings file or workspace file]
📖 Documentation: https://github.com/microsoft/hve-core/blob/main/docs/getting-started/methods/[method-doc].md
🧪 Available Agents:
• task-researcher, task-planner, task-implementor, task-reviewer
• github-backlog-manager, adr-creation, doc-ops, pr-review
• prompt-builder, memory, and more!
📋 Configuring optional settings...
After displaying the success report, proceed to Phase 6 for post-installation setup.
This phase applies to all installation methods (Extension and Clone-based). Both paths converge here for consistent post-installation configuration.
🛡️ Configuring gitignore...
Check and configure gitignore entries based on the installation method. Different methods may require different gitignore entries.
| Method | Gitignore Entry | Reason |
|---|---|---|
| 2 (Git-Ignored) | .hve-core/ | Excludes the local HVE-Core clone |
| All methods | .copilot-tracking/ | Excludes AI workflow artifacts |
Detection: Check if .gitignore exists and contains the required entries.
For Method 2 (Git-Ignored): If .hve-core/ is not in .gitignore, it should have been added during Phase 4 installation. Verify it exists.
For all methods: Check if .copilot-tracking/ should be added to .gitignore. This directory stores local AI workflow artifacts (plans, changes, research notes) that are typically user-specific and not meant for version control.
.gitignore missing or pattern not found → Present the prompt below📋 Gitignore Recommendation
The `.copilot-tracking/` directory stores local AI workflow artifacts:
• Plans and implementation tracking
• Research notes and change records
• User-specific prompts and handoff logs
These files are typically not meant for version control.
Would you like to add `.copilot-tracking/` to your .gitignore? (yes/no)
User input handling:
.gitignoreModification: If user approves:
.gitignore exists: Append the following at the end of the file.gitignore missing: Create it with the content below# HVE-Core AI workflow artifacts (local only)
.copilot-tracking/
Report: "✅ Added .copilot-tracking/ to .gitignore"
After the gitignore checkpoint, proceed to Checkpoint 5 (MCP Configuration).
After the gitignore checkpoint (for any installation method), present MCP configuration guidance. This helps users who want to use agents that integrate with Azure DevOps, GitHub, or documentation services.
📡 MCP Server Configuration (Optional)
Some HVE-Core agents integrate with external services via MCP (Model Context Protocol):
| Agent | MCP Server | Purpose |
|------------------------|--------------------------|---------------------------|
| ado-prd-to-wit | ado | Azure DevOps work items |
| github-backlog-manager | github | GitHub backlog management |
| task-researcher | context7, microsoft-docs | Documentation lookup |
Would you like to configure MCP servers? (yes/no)
User input handling:
If user chooses to configure MCP, present:
Which MCP servers would you like to configure?
| Server | Purpose | Recommended For |
|----------------|---------------------------|----------------------------|
| github | GitHub issues and repos | GitHub-hosted repositories |
| ado | Azure DevOps work items | Azure DevOps repositories |
| context7 | SDK/library documentation | All users (optional) |
| microsoft-docs | Microsoft Learn docs | All users (optional) |
⚠️ Suggest EITHER github OR ado based on where your repo is hosted, not both.
Enter server names separated by commas (e.g., "github, context7"):
Parse the user's response to determine which servers to include.
Create .vscode/mcp.json using ONLY the templates below. Use HTTP type with managed authentication where available.
[!IMPORTANT] These are the only correct configurations. Do not use stdio/npx for servers that support HTTP.
{
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/"
}
}
{
"inputs": [
{
"id": "ado_org",
"type": "promptString",
"description": "Azure DevOps organization name (e.g. 'contoso')",
"default": ""
},
{
"id": "ado_tenant",
"type": "promptString",
"description": "Azure tenant ID (required for multi-tenant scenarios)",
"default": ""
}
],
"servers": {
"ado": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@azure-devops/mcp", "${input:ado_org}", "--tenant", "${input:ado_tenant}", "-d", "core", "work", "work-items", "search", "repositories", "pipelines"]
}
}
}
{
"context7": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@upstash/context7-mcp"]
}
}
{
"microsoft-docs": {
"type": "http",
"url": "https://learn.microsoft.com/api/mcp"
}
}
When creating .vscode/mcp.json:
.vscode/ directory if it does not existinputs array only if ado server is selectedservers objectExample combined configuration for "github, context7":
{
"servers": {
"github": {
"type": "http",
"url": "https://api.githubcopilot.com/mcp/"
},
"context7": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@upstash/context7-mcp"]
}
}
}
After creating the file, display:
✅ Created .vscode/mcp.json with [server names] configuration
📖 Full documentation: https://github.com/microsoft/hve-core/blob/main/docs/getting-started/mcp-configuration.md
After gitignore and MCP checkpoints complete, display the final completion message:
✅ Setup Complete!
▶️ Next Steps:
1. Reload VS Code (Ctrl+Shift+P → "Reload Window")
2. Open Copilot Chat (`Ctrl+Alt+I`) and click the agent picker dropdown
3. Select an agent to start working
💡 Select `task-researcher` from the picker to explore HVE-Core capabilities
For Extension installations, also include:
---
📝 Want to customize HVE-Core or share with your team?
Run this skill again and choose "Clone-Based Installation" for full customization options.
For Clone-based installations, proceed to Phase 7 for optional agent customization.
[!IMPORTANT] Generated scripts in this phase require PowerShell 7+ (
pwsh). Windows PowerShell 5.1 is not supported.
After Phase 6 completes, offer users the option to copy agent files into their target repository. This phase ONLY applies to clone-based installation methods (1-6), NOT to extension installation.
If user selected Extension Quick Install (Option 1) in Phase 2, skip Phase 7 entirely. Extension installation bundles agents automatically.
Present the agent selection prompt:
📂 Agent Customization (Optional)
HVE-Core includes specialized agents for common workflows.
Copying agents enables local customization and offline use.
🔬 RPI Core (Research-Plan-Implement workflow)
• task-researcher - Technical research and evidence gathering
• task-planner - Implementation plan creation
• task-implementor - Plan execution with tracking
• task-reviewer - Implementation review and validation
• rpi-agent - RPI workflow coordinator
📋 Planning & Documentation
• adr-creation, agile-coach, brd-builder, doc-ops, prd-builder
• product-manager-advisor, security-planner, ux-ui-designer
⚙️ Generators
• arch-diagram-builder, gen-data-spec, gen-jupyter-notebook, gen-streamlit-dashboard
✅ Review & Testing
• pr-review, prompt-builder, test-streamlit-dashboard
🧠 Utilities
• memory - Conversation memory and session continuity
🔗 Platform-Specific
• ado-prd-to-wit (Azure DevOps)
• github-backlog-manager (GitHub)
Options:
[1] Install RPI Core only (recommended)
[2] Install by collection
[3] Skip agent installation
Your choice? (1/2/3)
User input handling:
When the user selects option 2, read collection manifests to present available collections.
Read collections/*.collection.yml from the HVE-Core source (at $hveCoreBasePath). Derive collection options from collection id and name. For each selected collection, count agent items where kind equals agent and effective item maturity is stable (item maturity omitted defaults to stable; exclude experimental and deprecated).
🎭 Collection Selection
Choose one or more collections to install agents tailored to your role, more to come in the future.
| # | Collection | Agents | Description |
|---|------------|--------|---------------------------------|
| 1 | Developer | [N] | Software engineers writing code |
Enter collection number(s) separated by commas (e.g., "1"):
Agent counts [N] include agents matching the collection with stable maturity.
User input handling:
For each selected collection identifier:
items in the collection manifestkind is agent AND maturity is stable📋 Agents for [Collection Name(s)]
The following [N] agents will be copied:
• [agent-name-1] - tags: [tag-1, tag-2]
• [agent-name-2] - tags: [tag-1, tag-2]
...
Proceed with installation? (yes/no)
User input handling:
[!NOTE] Collection filtering applies to agents only. Copying of related prompts, instructions, and skills based on collection is planned for a future release.
| Bundle | Agents |
|---|---|
hve-core | task-researcher, task-planner, task-implementor, task-reviewer, rpi-agent |
collection:<id> | Stable agents matching the collection |
Before copying, check for existing agent files with matching names.
PowerShell: Run scripts/collision-detection.ps1 with the hveCoreBasePath, selection, and optional collectionAgents variables set.
Bash: Run scripts/collision-detection.sh with the HVE-Core base path and file list as arguments.
If collisions are detected, present:
⚠️ Existing Agents Detected
The following agents already exist in your project:
• [list collision files]
Options:
[O] Overwrite with HVE-Core version
[K] Keep existing (skip these files)
[C] Compare (show diff for first file)
Or for all conflicts:
[OA] Overwrite all
[KA] Keep all existing
Your choice?
User input handling:
After selection and collision resolution, execute the copy operation.
PowerShell: Run scripts/agent-copy.ps1 with the required variables set.
Bash: Run scripts/agent-copy.sh with the HVE-Core base path, collection ID, and file list as arguments.
Upon successful copy, display:
✅ Agent Installation Complete!
Copied [N] agents to .github/agents/
Created .hve-tracking.json for upgrade tracking
📄 Installed Agents:
• [list of copied agent names]
🔄 Upgrade Workflow:
Run this installer again to check for agent updates.
Modified files will prompt before overwriting.
Use 'eject' to take ownership of any file.
Proceeding to final success report...
When .hve-tracking.json already exists, Phase 7 operates in upgrade mode.
At Phase 7 start, check for existing manifest.
PowerShell: Run scripts/upgrade-detection.ps1 with the hveCoreBasePath variable set.
Bash: Run scripts/upgrade-detection.sh with the HVE-Core base path as an argument.
If upgrade mode with version change:
🔄 HVE-Core Agent Upgrade
Source: microsoft/hve-core v[SOURCE_VERSION]
Installed: v[INSTALLED_VERSION]
Checking file status...
Compare current files against manifest.
PowerShell: Run scripts/file-status-check.ps1.
Bash: Run scripts/file-status-check.sh to compare files against the manifest.
Present upgrade summary:
📋 Upgrade Summary
Files to update (managed):
✅ .github/agents/hve-core/task-researcher.agent.md
✅ .github/agents/hve-core/task-planner.agent.md
Files requiring decision (modified):
⚠️ .github/agents/hve-core/task-implementor.agent.md
Files skipped (ejected):
🔒 .github/agents/custom-agent.agent.md
For modified files, choose:
[A] Accept upstream (overwrite your changes)
[K] Keep local (skip this update)
[E] Eject (never update this file again)
[D] Show diff
Process file: task-implementor.agent.md?
When user requests diff:
─────────────────────────────────────
File: .github/agents/hve-core/task-implementor.agent.md
Status: modified
─────────────────────────────────────
--- Local version
+++ HVE-Core version
@@ -10,3 +10,5 @@
## Role Definition
-Your local modifications here
+Updated behavior with new capabilities
+
+New section added in latest version
─────────────────────────────────────
[A] Accept upstream / [K] Keep local / [E] Eject
After user decision, update manifest:
| Decision | Status Change | Manifest Update |
|---|---|---|
| Accept | modified → managed | Update hash, version |
| Keep | modified → modified | No change (skip file) |
| Eject | * → ejected | Add ejectedAt timestamp |
When user ejects a file:
PowerShell: Run scripts/eject.ps1 with the FilePath parameter.
Bash: Run scripts/eject.sh with the file path as an argument.
After processing all files:
✅ Upgrade Complete!
Updated: [N] files
Skipped: [M] files (kept local or ejected)
Version: v[OLD] → v[NEW]
Proceeding to final success report...
Provide targeted guidance when steps fail:
| Error | Troubleshooting |
|---|---|
| Not in git repo | Run from within a git workspace; verify git --version |
| Clone failed | Check network to github.com; verify git credentials and write permissions |
| Validation failed | Repository may be incomplete; delete HVE-Core directory and re-run installer |
| Settings update failed | Verify settings.json is valid JSON; check permissions; try closing VS Code |
To remove a failed or unwanted installation:
| Method | Cleanup |
|---|---|
| Extension | VS Code → Extensions → HVE Core → Uninstall |
| 1 (Peer Clone) | rm -rf ../hve-core |
| 2 (Git-Ignored) | rm -rf .hve-core |
| 3-4 (Mounted/Codespaces) | Remove mount/postCreate from devcontainer.json |
| 5 (Multi-Root) | Delete .code-workspace file |
| 6 (Submodule) | git submodule deinit lib/hve-core && git rm lib/hve-core |
Then remove HVE-Core paths from .vscode/settings.json.
If you used Phase 7 agent copy, also delete .hve-tracking.json and optionally .github/agents/ if you no longer need copied agents.
Never modify files without explicit user authorization. Always explain changes before making them. Respect denial at any checkpoint.
Checkpoints requiring authorization:
Use these exact emojis for consistency:
In-progress indicators (always end with ellipsis ...):
Completion indicators:
Success: Environment detected, method selected, HVE-Core directories validated (agents, prompts, instructions, skills), settings configured, user directed to reload.
Failure: Detection fails, clone/submodule fails, validation finds missing directories, or settings modification fails.
🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.