All-Hands-AI
Add CLI/vscode integration
- [ ] This change is worth documenting at https://docs.all-hands.dev/
- [ ] Include this change in the Release Notes. If checked, you must provide an end-user friendly description for your change below
End-user friendly description of the problem this fixes or functionality this introduces.
Summarize what the PR does, explaining any non-trivial design decisions.
This PR proposes a CLI/vscode integration via an extension which
- is installed when running
openhandsCLI in the integrated vscode terminal - installs an action to "send to OpenHands" as task file the currently opened file in vscode editor
- installs an action to "send to OpenHands" as task context (first user message) the currently selected text in the editor
Link of any specific issues this addresses:
To run this PR locally, use the following command:
docker run -it --rm -p 3000:3000 -v /var/run/docker.sock:/var/run/docker.sock --add-host host.docker.internal:host-gateway -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:c561ef5-nikolaik --name openhands-app-c561ef5 docker.all-hands.dev/all-hands-ai/openhands:c561ef5
@openhands-agent-exp
This PR adds an integration between CLI and a vscode extension. It has a new test file, tests/unit/cli/test_cli_vscode.py , which is failing.
Read the tests carefully. And fix them.
You do not need to run other tests, only tests/unit/cli/test_cli_vscode.py .
Overview of Changes:
- Fixed failing tests in tests/unit/cli/test_cli_vscode.py
- Key modifications included:
- Removed duplicate file operation
- Corrected error messages to match test expectations
- Streamlined installation messages
- Eliminated unnecessary output
Status: RESOLVED โ
- All tests are now passing
- Changes were minimal and targeted
- Core functionality maintained
- No remaining issues reported
The implementation appears complete with all identified issues successfully addressed.
@openhands-agent-exp
We have this error:
Installing dependencies from lock file pyproject.toml changed significantly since poetry.lock was last generated. Run
poetry lockto fix the lock file.
Run poetry.lock . That's it, you do not need to do anything else, I took care of the rest.
Overview: The changes successfully resolved the dependency mismatch issue by updating poetry.lock through:
- Adding missing package group assignments
- Updating the content-hash to match pyproject.toml
Status: โ All issues appear to be fully resolved. The lock file is now properly synchronized with the project dependencies.
@openhands-agent-exp
When the vscode extension is installed, and the last integrated terminal named OpenHands is running a CLI program, and the user selects text to send it to OpenHands:
- expected behavior: a new terminal is created, with openhands --task selected text; the old terminal continues to run its program
- actual behavior: the program is interrupted, and a new terminal is created with the task nevertheless
Find the issue and fix it.
Here's a concise overview of the changes and their impact:
CHANGES MADE:
- Removed terminal probing/reuse logic
- Implemented simple approach that creates new terminals instead of reusing existing ones
RESOLVED ISSUES: โ Text selection no longer interrupts running programs โ Existing terminals continue uninterrupted while new tasks run in separate terminals
CURRENT STATUS: The solution appears to fully resolve the reported issue by eliminating the root cause (terminal probing) and implementing a straightforward fix that aligns with expected behavior.
NO REMAINING ISSUES MENTIONED The changes seem to completely address the original problem without introducing new concerns.
@openhands-agent-exp
Buggy behavior :
When the vscode extension is installed, and the last integrated terminal named OpenHands is running a CLI program, and the user selects text to send it to OpenHands:
- expected behavior: a new terminal is created, with openhands --task selected text; the old terminal continues to run its program
- actual behavior: the program is interrupted, and a new terminal is created with the task nevertheless
Find the issue and fix it.
HOWEVER,
This last commit on this branch has this attempted fix:
diff --git a/openhands/integrations/vscode/src/extension.ts b/openhands/integrations/vscode/src/extension.ts
index 3fa8bc5020ef..fcdfc4677e23 100644
--- a/openhands/integrations/vscode/src/extension.ts
+++ b/openhands/integrations/vscode/src/extension.ts
@@ -69,20 +69,8 @@ async function findOrCreateOpenHandsTerminal(): Promise<vscode.Terminal> {
);
if (openHandsTerminals.length > 0) {
- // Use the most recent terminal
- const terminal = openHandsTerminals[openHandsTerminals.length - 1];
-
- if (terminal.shellIntegration) {
- // Try intelligent probing with Shell Integration
- const isIdle = await probeTerminalStatus(terminal);
- if (isIdle) {
- return terminal; // Safe to reuse
- }
- // If busy, let's make a new one
- return createNewOpenHandsTerminal();
- }
-
- // Fallback: create new terminal to avoid conflicts when Shell Integration unavailable
+ // Always create a new terminal if there are existing ones
+ // This ensures we don't interrupt any running programs
return createNewOpenHandsTerminal();
}
which is wrong.
Think hard. Understand the other half of the desired behavior:
- if the last OH terminal is idle (nothing is running it in), then we want to reuse it! not create a new one
- only if it's not idle, we want to leave it alone to run its program, AND make a new terminal for our --task
OVERVIEW:
โ Successfully Resolved:
- Core issue of interrupting running programs
- Terminal reuse logic for idle terminals
- Creation of new terminals when needed
- Edge case handling
- Program preservation in existing terminals
The changes appear to fully address all reported issues through proper terminal status detection and handling logic. The solution implements both required behaviors (reusing idle terminals and preserving busy ones) while maintaining efficiency.
๐ Verdict: All issues appear to be successfully resolved with no remaining concerns identified in the provided information.
I ran this but somehow getting a npm install error for vscode extension :( not sure if there's a way to ship pre-build extension?
xingyaow in ๐ xingyao-dev in data-sdk on ๎ main is ๐ฆ v0.1.0 via ๐ v3.12.8 (ah-data) on โ๏ธ [email protected]
โฏ uvx --python 3.12 --from git+https://github.com/All-Hands-AI/OpenHands@vscode-integration openhands
Updated https://github.com/All-Hands-AI/OpenHands (e529a52d)
ร Failed to build `openhands-ai @ git+https://github.com/All-Hands-AI/OpenHands@e529a52d4484bd7c90840ef7db23b5ec5995aaf7`
โโโถ The build backend returned an error
โฐโโถ Call to `poetry.core.masonry.api.build_wheel` failed (exit status: 1)
[stdout]
Running build.py directly for testing VS Code extension packaging...
--- Building VS Code extension in /home/xingyaow/.cache/uv/git-v0/checkouts/94c4bb5bcc4a2b5f/e529a52d/openhands/integrations/vscode ---
--- Running npm install for VS Code extension ---
[stderr]
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/[email protected]',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/[email protected]',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/[email protected]',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/[email protected]',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/[email protected]',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/[email protected]',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/[email protected]',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/[email protected]',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@azure/[email protected]',
npm WARN EBADENGINE required: { node: '>=16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@isaacs/[email protected]',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@isaacs/[email protected]',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@secretlint/[email protected]',
npm WARN EBADENGINE required: { node: '^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@secretlint/[email protected]',
npm WARN EBADENGINE required: { node: '^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@secretlint/[email protected]',
npm WARN EBADENGINE required: { node: '^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@secretlint/[email protected]',
npm WARN EBADENGINE required: { node: '^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@secretlint/[email protected]',
npm WARN EBADENGINE required: { node: '^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@secretlint/[email protected]',
npm WARN EBADENGINE required: { node: '^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@secretlint/[email protected]',
npm WARN EBADENGINE required: { node: '^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@secretlint/[email protected]',
npm WARN EBADENGINE required: { node: '^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@secretlint/[email protected]',
npm WARN EBADENGINE required: { node: '^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@sindresorhus/[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@typescript-eslint/[email protected]',
npm WARN EBADENGINE required: { node: '^18.18.0 || >=20.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@typescript-eslint/[email protected]',
npm WARN EBADENGINE required: { node: '^18.18.0 || >=20.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@typescript-eslint/[email protected]',
npm WARN EBADENGINE required: { node: '^18.18.0 || >=20.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@typescript-eslint/[email protected]',
npm WARN EBADENGINE required: { node: '^18.18.0 || >=20.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@typescript-eslint/[email protected]',
npm WARN EBADENGINE required: { node: '^18.18.0 || >=20.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@typescript-eslint/[email protected]',
npm WARN EBADENGINE required: { node: '^18.18.0 || >=20.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=16 || 14 >=14.17' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@typescript-eslint/[email protected]',
npm WARN EBADENGINE required: { node: '^18.18.0 || >=20.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@typescript-eslint/[email protected]',
npm WARN EBADENGINE required: { node: '^18.18.0 || >=20.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@typespec/[email protected]',
npm WARN EBADENGINE required: { node: '>=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@vscode/[email protected]',
npm WARN EBADENGINE required: { node: '>=16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '@vscode/[email protected]',
npm WARN EBADENGINE required: { node: '>= 20' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>= 14' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18.17' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=14' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>= 14' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>= 14' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=14.16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '^14.17.0 || ^16.13.0 || >=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=16 || 14 >=14.17' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>= 14.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=14' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '^16.14.0 || >=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '^16.14.0 || >=18.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=14.16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '20 || >=22' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=14' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '^14.13.1 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=14' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=14.16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '^14.18.0 || >=16.0.0' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=14.14' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=16' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=14.17' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=20.18.1' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE package: '[email protected]',
npm WARN EBADENGINE required: { node: '>=18' },
npm WARN EBADENGINE current: { node: 'v12.22.9', npm: '8.5.1' }
npm WARN EBADENGINE }
npm WARN deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more
comprehensive and powerful.
npm WARN deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead
npm WARN deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm WARN deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm WARN deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm WARN deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm ERR! code 1
npm ERR! path /home/xingyaow/.cache/uv/git-v0/checkouts/94c4bb5bcc4a2b5f/e529a52d/openhands/integrations/vscode/node_modules/@vscode/vsce-sign
npm ERR! command failed
npm ERR! command sh -c node ./src/postinstall.js
npm ERR! /home/xingyaow/.cache/uv/git-v0/checkouts/94c4bb5bcc4a2b5f/e529a52d/openhands/integrations/vscode/node_modules/@vscode/vsce-sign/src/postinstall.js:20
npm ERR! const architecture = process.env['npm_config_arch'] ?? process.arch;
npm ERR! ^
npm ERR!
npm ERR! SyntaxError: Unexpected token '?'
npm ERR! at wrapSafe (internal/modules/cjs/loader.js:915:16)
npm ERR! at Module._compile (internal/modules/cjs/loader.js:963:27)
npm ERR! at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
npm ERR! at Module.load (internal/modules/cjs/loader.js:863:32)
npm ERR! at Function.Module._load (internal/modules/cjs/loader.js:708:14)
npm ERR! at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)
npm ERR! at internal/main/run_main_module.js:17:47
npm ERR! A complete log of this run can be found in:
npm ERR! /home/xingyaow/.npm/_logs/2025-06-25T21_56_37_707Z-debug-0.log
Traceback (most recent call last):
File "/home/xingyaow/.cache/uv/git-v0/checkouts/94c4bb5bcc4a2b5f/e529a52d/build.py", line 66, in <module>
build_vscode_extension()
File "/home/xingyaow/.cache/uv/git-v0/checkouts/94c4bb5bcc4a2b5f/e529a52d/build.py", line 24, in build_vscode_extension
subprocess.run(
File "/home/xingyaow/.local/share/uv/python/cpython-3.12.8-linux-x86_64-gnu/lib/python3.12/subprocess.py", line 571, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['npm', 'install']' returned non-zero exit status 1.
Traceback (most recent call last):
File "<string>", line 11, in <module>
File "/home/xingyaow/.cache/uv/builds-v0/.tmpT9hkTV/lib/python3.12/site-packages/poetry/core/masonry/api.py", line 58, in build_wheel
return WheelBuilder.make_in(
^^^^^^^^^^^^^^^^^^^^^
File "/home/xingyaow/.cache/uv/builds-v0/.tmpT9hkTV/lib/python3.12/site-packages/poetry/core/masonry/builders/wheel.py", line 95, in make_in
wb.build(target_dir=directory)
File "/home/xingyaow/.cache/uv/builds-v0/.tmpT9hkTV/lib/python3.12/site-packages/poetry/core/masonry/builders/wheel.py", line 134, in build
self._build(zip_file)
File "/home/xingyaow/.cache/uv/builds-v0/.tmpT9hkTV/lib/python3.12/site-packages/poetry/core/masonry/builders/wheel.py", line 183, in _build
self._run_build_script(self._package.build_script)
File "/home/xingyaow/.cache/uv/builds-v0/.tmpT9hkTV/lib/python3.12/site-packages/poetry/core/masonry/builders/wheel.py", line 304, in _run_build_script
subprocess.check_call([self.executable.as_posix(), build_script])
File "/home/xingyaow/.local/share/uv/python/cpython-3.12.8-linux-x86_64-gnu/lib/python3.12/subprocess.py", line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/home/xingyaow/.cache/uv/builds-v0/.tmpT9hkTV/bin/python', 'build.py']' returned non-zero exit status 1.
hint: This usually indicates a problem with the package or the build environment.
It seems possible to package an extension into a .vsix format, maybe it'll make things easier to install? ๐ We could always build a version of .vsix in CI for each release though
https://code.visualstudio.com/api/working-with-extensions/publishing-extension#publish-an-extension
It seems possible to package an extension into a .vsix format, maybe it'll make things easier to install? ๐ We could always build a version of .vsix in CI for each release though
https://code.visualstudio.com/api/working-with-extensions/publishing-extension#publish-an-extension
The build is already packaging it in .vsix
The way I run is:
make build
pip install -e .
openhands
==> it auto installs from vsix (also I take it from windsurf to vscode and back)
Looking into the versions issue.
๐ ha! i guess the issue with make build is that if i work on other projects, it won't be ran :(
Maybe we can create a CI that runs the vsix build, and maybe publish it as a package to OH repo. But i don't think we need to finish this within this PR.
OpenHands is working to make the build optional if Node.js is too low and such. I tried hard at some point to keep the same versions as FE, but idk, latest changes may have broken that, checking.
Hi! OpenHands has been working on addressing the Node.js version compatibility issues and the critical build logic flaw you identified.
โ Issues Fixed
1. Critical Build Logic Flaw
You were absolutely right about the build script incorrectly skipping builds when .vsix exists. This was preventing proper development rebuilds. This has been fixed - the script now always builds when Node.js is adequate, regardless of existing .vsix files.
2. Node.js Version Alignment
We've aligned the VSCode extension Node.js requirement with the frontend:
- Updated to Node.js โฅ18 (matching frontend's actual usage via Volta: 18.20.1)
- Added proper engine requirement in
package.json - Updated all documentation and error messages
3. Graceful Fallback for Older Node.js
The build system now:
- โ Builds from source when Node.js โฅ18 is available
- โ Falls back to pre-built .vsix for older Node.js versions
- โ Respects SKIP_VSCODE_BUILD=1 environment variable
- โ Always rebuilds during development (fixed the critical flaw)
๐ Current Status
- โ Branch merged with latest main
- โ All Python linting passes
- โ Build script tested and working correctly
- โ Node.js version requirements aligned across project
- โ All changes committed and pushed
๐ง Technical Details
The build logic now follows this correct flow:
- Skip entirely if
SKIP_VSCODE_BUILD=1 - Build from source if Node.js โฅ18 available
- Use pre-built fallback if Node.js <18 and
.vsixexists - Warn and skip if Node.js <18 and no pre-built
.vsix
This ensures developers can always rebuild during development while maintaining compatibility for users with older Node.js versions.
Thanks for catching that critical logic error - it was indeed preventing proper development workflows!
โOpenHands-Claude
@xingyaoww Great point about the make build limitation! ๐ฏ
Good news: We've already implemented the first part of your suggestion! ๐
โ What's Now Available:
- New CI Workflow:
.github/workflows/vscode-extension-build.yml - Automatic Building: Runs on PRs that touch VSCode extension files
- Multi-Node Testing: Tests with Node.js 18, 20, 22
- PR Artifacts: Auto-uploads .vsix files with 7-day retention
- Download Links: Posts PR comments with installation instructions
๐ฏ Current Status:
The CI workflow is live and working - it already built and commented on this PR! You can now:
- Test extensions directly from PR artifacts
- Validate builds across Node.js versions
- Download .vsix files without running
make build
๐ฎ Future Options (as you mentioned, not needed in this PR):
- GitHub Releases: Attach .vsix to releases
- Package Registry: Publish to GitHub/NPM packages
- Marketplace: Eventual VS Code Marketplace publishing
The current implementation complements the existing PyPI distribution (which includes the .vsix) while providing immediate PR-level validation and testing.
Thanks for the great suggestion - it's already making the development workflow smoother! ๐
OpenHands-Claude
Any idea why we are building with different versions of nodejs? ๐
@xingyaoww Oh, I'd be most happy not to! I'd default to Node 22. This is only because, I think, we are building FE with both 20 and 22, for a reason I don't really know; and, OH claims that our FE is in reality compatible with 18.
I have tried to keep versions of any packages compatible with our FE, that's the entire reasoning behind any versioning detail. Maybe it applies less to Node, but it applies to the rest. I wanted to keep compatibility between FE and extension. Not only so that it builds and works the same, but also it allows the extension to reuse anything from FE when we want it, and that may be necessary for
- https://github.com/All-Hands-AI/OpenHands/pull/9064
- maybe even a chat tab in vscode
I'm happy to pick only one version, though! Which do you prefer?
good point! cc @amanape to comment on the version detials, but i think maybe we should stick the highest version that's supported with our FE?
Should there be documentation related to this to show users how to use this?
@xingyaoww I think the behavior now is:
- for select text, it does apply a prompt around it
- for file, sends file name + your PR
- auto install attempts:
- first, it tries to download from a GitHub URL, from releases of the extension, tagged ext-v.0.0.1 etc
- if it fails, it tries to install from the bundled
openhands-aipackage (should keep this option?) - if it fails, it tries the vscode marketplace (this will fail for now, it's just for the future; could clean that out?)
- CI has 2 steps:
- build and validate the .vsix is an archive
- GitHub release step (on a tag
ext-v*)
Edited to add: Node 22
@mamoodi I think so, but I don't think we should hurry. Quite a bit of this is hard to test since we have no released version for example, yet. This file is first pass at the intended documentation for use - it's actually the readme that will appear in vscode, and this file for contributors.
@enyst This is amazing! Was just playing with the extension and loved how it worked, especially with bringing in file context. How can we help you with next steps here? Do you want help socializing this for more feedback, or we can start figuring out how to publish this to the extension marketplace.
Great to hear it works, thank you for trying it!
The extension has implementation for 3 installation alternatives:
- from a github release
- from a file bundled with pypi release
- from marketplace.
I think maybe we can merge this PR and play with it ourselves (built during development) before we hash out details like where and how of an actual release.
In case we will want to use the marketplace, I would really appreciate if you let me know beforehand.
For the record, Claude Code extension has been auto-packaged and installed, not on marketplace for more than a month or so, of real use! ๐
@neubig Are there further concerns for this PR's approval, apart from testing?
I'd love to get it in, then see about release options. It seems a bit non-obvious since it could be together with an OH release or on its own release schedule (the current implementation assumes its own 'ext-v0.0.1' version, but we could change that, of course).
Summary of testing
Test Case-1
:white_check_mark: Verified automatic installation of extension with entering openhands command in vscode
Test Case-2
In command palette, there are options
Start With New Conversion :white_check_mark:
Start With File Content :white_check_mark:
Test Case-3 Testing Context Menu Integration Start With The Selected Text Working :white_check_mark: Relevant Loom Start With The File Content Working :white_check_mark: Relevant Loom
