codesandbox / codesandbox/codesandbox-client
Unable to run codesandbox.io workspace on local VSCode with extension
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🐛 bug report
Preflight Checklist
- I have read the Contributing Guidelines for this project.
- I agree to follow the Code of Conduct that this project
adheres to. - I have searched the issue tracker for an issue that matches the one I want
to file, without success.
Description of the problem
Unable to run codesandbox.io cloud workspace on my local machine via vscode. I've got the VSCode Codesandbox extension installed and logged in but it gets stuck at the following output whenever I try creating a sandbox locally or via cloud.
Opening sandbox in VSCode, sandbox 6vzdsm
Fetching sandbox...
Installing SSH keys...
There is no output after this line in codesandbox terminal.
I can see ssh keys at ~/.ssh/csb/* and the same included as the following in my ~/.ssh/config.
# CodeSandbox SSH Integration
Include "csb/config"
# End of CodeSandbox SSH Integration
How has this issue affected you? What are you trying to accomplish?
I'm trying to run the cloud ( web ) codesandbox.io workspace on my local mac laptop using vscode so that I can install recommended extensions and work natively as I'm used to developing in vscode. Due to the issue, I'm unable to use vscode and am forced to use the web version of codesandbox while working.
Platform Details:
VSCode: 1.84.2
In case the following helps:
~/.ssh/config - 600 permission
~/.ssh/csb/config - 644 permission
~/.ssh/csb - 755 permission
To Reproduce
Link to sandbox: link (optional)
Your Environment
| Software | Name/Version |
|---|---|
| Сodesandbox | v0.2.105 |
| Browser | Chrome Version 119.0.6045.159 (Official Build) (x86_64) |
| Operating System | Mac 12.4 (Intel) |
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.
Research direction
No repository file or test is named. Start by reproducing the linked sandbox through the VSCode Codesandbox extension on the reported macOS and inspect the SSH setup around ~/.ssh/csb/config; done means the workspace proceeds past “Installing SSH keys” and opens locally.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, vscode
- Domain
- desktop-dev, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100