This issue is AI generated.
Problem
NeoAgent has a Chrome browser extension and a desktop companion but no integration with developer IDEs. Hermes Agent ships VS Code and JetBrains plugins that let developers invoke the agent from within their editor — sending selected code, the current file, or the active diff as context, and receiving the result inline or in a side panel. This is a significant workflow gap for developer users.
Required change
Implement IDE extensions (starting with VS Code as the higher-priority target) that:
- Connect to a running NeoAgent backend (local or remote) via the existing REST/WebSocket API.
- Let the user send a prompt with optional context (selected text, current file, git diff) to the agent.
- Stream the agent's response into a VS Code webview panel or inline editor decoration.
- Support the existing tool approval flow (forwarding approval prompts to the IDE notification system).
JetBrains support can follow using the IntelliJ Platform Plugin SDK with the same backend protocol.
Acceptance criteria
- A VS Code extension is installable and connects to NeoAgent.
- Users can send a chat message with editor context attached.
- Agent responses stream into the extension panel.
- The extension is published to the VS Code Marketplace or documented for local install.
This issue is AI generated.
Problem
NeoAgent has a Chrome browser extension and a desktop companion but no integration with developer IDEs. Hermes Agent ships VS Code and JetBrains plugins that let developers invoke the agent from within their editor — sending selected code, the current file, or the active diff as context, and receiving the result inline or in a side panel. This is a significant workflow gap for developer users.
Required change
Implement IDE extensions (starting with VS Code as the higher-priority target) that:
JetBrains support can follow using the IntelliJ Platform Plugin SDK with the same backend protocol.
Acceptance criteria