Skip to main content

Troubleshooting

This page covers common installation problems and answers frequently asked questions about HVE Core extensions and collections.

Common Installation Problems​

Extension Not Loading After Install​

The extension appears in the Extensions sidebar but HVE Core agents and prompts are not available in Copilot Chat.

Solutions​

  1. Run the Developer: Reload Window command from the Command Palette (Ctrl+Shift+P / Cmd+Shift+P).
  2. Verify that GitHub Copilot Chat is installed and active in the Extensions sidebar. HVE Core requires it.
  3. Open the Output panel (Ctrl+Shift+U) and select the HVE Core channel. Look for error messages during extension activation.
  4. Confirm your VS Code version is 1.99 or later under Help > About.

Agent or Prompt Not Appearing in Copilot​

Some agents or prompts are missing from the @ mention list or / command list in Copilot Chat.

Solutions​

  1. Agents and prompts load from .github/ directories in the open workspace. Verify that .github/agents/ and .github/prompts/ folders exist and contain .agent.md or .prompt.md files.
  2. Copilot Chat loads workspace-scoped agents only when a folder or workspace is open. Opening a single file does not activate workspace agents.
  3. If you used the HVE Installer, confirm that the selected collections were deployed. Run the installer agent again to verify the installed artifact list.
  4. Ensure your .gitignore does not exclude .github/agents/ or .github/prompts/ directories.

Collection Conflicts Between HVE Core All and HVE Installer​

Duplicate agents appear in Copilot Chat, or agents behave unexpectedly after installing both extensions.

Solutions​

  1. The HVE Core All extension installs the full hve-core-all collection containing every artifact. The HVE Installer deploys individual collections selectively. Using both can produce duplicate artifacts. Choose one extension.
  2. If you want all artifacts, keep HVE Core All and uninstall HVE Installer. If you want selective collections, keep HVE Installer and uninstall HVE Core All.
  3. After uninstalling, delete any leftover .github/agents/, .github/prompts/, .github/instructions/, and .github/skills/ directories that were deployed by the removed extension. Then reinstall with your preferred method.

Version Compatibility Issues​

Errors appear after updating VS Code or one of the HVE extensions, or agents reference features that do not exist.

Solutions​

  1. When updating VS Code, also update GitHub Copilot, GitHub Copilot Chat, and the HVE extension to their latest versions.
  2. Review the CHANGELOG for breaking changes between versions.
  3. If artifacts are out of sync, remove the existing .github/ HVE Core artifacts and reinstall using your preferred method.

Collection FAQ​

Which Extension Should I Install?​

ScenarioRecommended Extension
You want everything HVE Core offersHVE Core All (Full)
You want only specific domains (ADO, Design Thinking, etc.)HVE Installer (Selective)
You plan to contribute to HVE CoreClone the repository directly, see Developer Setup

How Do I Switch from HVE Core All to HVE Installer?​

  1. Uninstall the HVE Core All extension from the VS Code Extensions sidebar.
  2. Delete the .github/ HVE Core artifacts that the extension deployed to your workspace.
  3. Install the HVE Installer extension.
  4. Open Copilot Chat and ask any agent: "help me customize hve-core installation".
  5. Select the collections you need.

Can I Use Both Extensions Simultaneously?​

Using both extensions in the same workspace is not recommended. Both deploy artifacts to .github/ directories, which can result in duplicate agents and prompts. Choose one extension based on whether you need the full collection or selective deployment. See Collection Conflicts above for details.

How Do I Update to the Latest Collection Version?​

Marketplace extensions update automatically. When a new version is published, VS Code downloads and installs it. You can also manually check for updates in the Extensions sidebar.

For clone-based setups, pull the latest changes from the upstream repository:

git pull upstream main

Then reinstall dependencies with npm ci if package.json changed.

🤖 Crafted with precision by ✨Copilot following brilliant human instruction, then carefully refined by our team of discerning human reviewers.