The latest Node SDK is too old for the latest k8s images
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- docker, javascript, nodejs, rust
Research direction
Start with the generated Node SDK proto and client.js around line 294, then compare them with PR #3245 and openshell-server/src/auth/workspace_authz.rs:122. Reproduce sandbox creation using @nvidia/openshell-sdk@0.0.116 against the latest image. Done means the SDK can provide workspace_scope/workspaceScope and sandbox creation succeeds with recent OpenShell images.
Written by the indexing model from the issue text.
Description
User Story
The latest Node SDK is too old for the latest k8s images
Problem Statement
OpenShell gateway ran the ghcr.io :latest image, which had advanced past PR #3245 "typed workspace selectors" (2026-09-10, commit 90dbe545). That PR made workspace_scope a required field on CreateSandbox (enforced at openshell-server/src/auth/workspace_authz.rs:122). But the published @nvidia/openshell-sdk@0.0.116 (2026-08-28), whose generated proto has no workspaceScope field at all — its sandbox.create() only sends { name, labels, spec } (client.js:294). The client physically cannot send the field the newer gateway demands, so every create failed with [invalid_argument] workspace_scope is required.
Impact / Why This Matters
unable use nodejs with latest openshell docker images
Acceptance Criteria
node sdk must be compatibility to recent docker images
Reproduction Steps
create sandbox with recent sdk
Environment
:latest image of openshell
Logs
- Dominant language
- Rust
- Stars
- 8.7k
- Forks
- 1.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 271
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from NVIDIA/OpenShell
-
area:docs
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
state:triage-needed
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:cli state:validated
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
state:triage-needed
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
area:build spike state:review-ready state:stale
Difficulty 2/5 Half a day Newbie friendliness 68/100
All issues in NVIDIA/OpenShell
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
bug rules
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
app bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
IronCoreLabs/ironcore-alloy#346 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 65/100