Repository navigation
Feature request: provide seamless VSCode Remote support #928
Description
I don't trust VSCode "devcontainers" to properly contain an LLM working on a codebase. I would really like to use LXD containers as devcontainers instead of regular Docker containers.
Workshop seems like the right tool to do this with, but it doesn't actually integrate with devcontainers.
Currently, I might be able to "hack" it by simply starting an environment and using the "Remote - SSH" extension to connect to it. But that requires a lot of manual work, and I still need to manually install the project-specific tools if there's no SDK config for this project.
I see two possible approaches:
- Create a devcontainer-like feature that uses the workshop config file instead of a devcontainer config file. This feature is part of a vscode extension and hooks into the Remote feature to the remote into the workshop environment. The downside is that the user needs to recreate the devcontainer setup scripts to configure a workshop environment instead.
- Create an integration between devcontainers and workshop that runs the devcontainer inside of the workshop environment. This would be the most seamless experience, but might be a bit more complicated/convoluted.
What do you think?
Activity
jonathan-conder commentedon Jul 8, 2026
We have a vscode extension in the works.
In the meantime, the Remote SSH workflow is actually quite simple in the latest release. Make sure your workshop has been launched recently to enable these features.
~/.ssh/config:(replace⚠️ This is currently undocumented and might be subject to change in future.
<UID>with your user ID, i.e.id -u).$ code --folder-uri vscode-remote://ssh-remote+dev.myproject.wp/project(replace
dev.myproject.wpwith the actual hostname).You're welcome to run a devcontainer inside a workshop if that's something you want to do, but our main focus is to support SDKs as the mechanism of setting up the container environment. The quickest way to convert your devcontainer setup into this language is probably to sketch an SDK.
jonathan-conder commentedon Jul 8, 2026
Since you mentioned LLMs, I think we want to explore that area to make authoring SDKs easier; a skill or something to convert an existing devcontainer into a workshop or SDK might be useful.
jonathan-conder commentedon Nov 3, 2026
@merlijn-sebrechts The VS code extension has been released: https://marketplace.visualstudio.com/items?itemName=Canonical.workshop. Reckon we can close this one?
astrojuanlu commentedon Nov 4, 2026
Waiting for @merlijn-sebrechts to chime in, but one could say this partially addresses the original request? (Emphasis mine)
IIUC, the idea was to ease migration from devcontainers.
[-]Feature request: provide seamless devcontainer support[/-][+]Feature request: provide seamless VSCode Remote support[/+]merlijn-sebrechts commentedon Nov 4, 2026
I think this extension solves my issue, indeed. This implements the first of my two proposals.
Migration from devcontainers would be even better (or support for running a devcontainer inside of a workshop), but I think that's a separate issue. I've changed the title of this issue to better reflect that and I'll close this issue.