Remote Hermes API may not edit local VS Code files
Hermes is running on a VPS, while VS Code Copilot is running on a laptop. After enabling the Hermes API and adding it in VS Code as an , Copilot does not actually change files. The still shows that it planned to edit files and tried to edit them.
The likely issue is the workspace location. Hermes may be acting as if the files are inside the workspace on the VPS, but the real are on the laptop where Copilot is running.
Key points
- Hermes runs on a VPS, while VS Code Copilot on a laptop.
- Hermes was added to VS Code as an through the Hermes API.
- Copilot shows edit attempts in chat, but the files do not change.
- The suspected cause is a mismatch between the VPS workspace and the laptop workspace.
- Remote API access does not always include permission to edit local files.