I’ve been enjoying using sprites and experimenting with YOLO mode. Thanks for building a great product.
I’ve been using both the sprites CLI (in iTerm2) and the sprites extension for VS Code.
I switch between both tools for different needs:
CLI: using claude code from the terminal
VS Code: reviewing code changes in an IDE
A few things I’ve noticed in VS Code, and I’m not sure if this is a feature or a bug.
The git UI tool built into VS Code doesn’t work.
My python interpreter is not set and I can’t select the interpreter within the sprite from the “select interpreter” command in VS Code
A lot of other VS Code extensions don’t work.
I understand that some extensions “don’t support virtual workspaces” but I am surprised that the git tool doesn’t work.
I know I can get Claude Code to write commit messages and that’s fine. However, I do like reviewing the files that have been changed by Claude Code from VS Code and the git tool in VS Code is a really convenient way to review modified files and diffs.
I had assumed that the VS Code extension was not meant to do those things - that if you want the full remote dev experience then you would use one of VS Code’s own remote dev extensions.
For Sprites, the best option is probably to use tunnels.
That works really well. Thanks for sharing. Git tool now works really well and I can even use the agent chat provided by the IDE.
I guess I am now a little confused about the value of the Sprites VS Code Extension. My expectation was that the sprites extension was going to take care of all of this.
It would be really cool to see a comparison table between Remote Tunnels and Sprites VS Code Extension so folks could make an informed choice on the extension that will work for their use case. For example, I wonder if there are more or less security concerns when using Remote Tunnels.
I think the Sprites extension is an alternative to the CLI, for accessing the Sprites API, to manage and get into your sprites. I don’t think of it so much for actually working inside your sprite.
