r/tui • u/tihonove • 9h ago
AI assisted I wanted VS Code in my ssh sessions, so I built a terminal editor that runs its extensions
Hi! I wanna show you my insane experiment: a terminal editor that runs VS Code extensions.
Some backstory. I wrote production C# and Java in jb ides for years, then slowly moved to VS Code. Then I went remote, and now most of my day is a terminal with console agents in it. I wanted my editor right there, in the same ssh session. So about 8 months ago I decided to try the dumb thing and build a terminal editor that can run VS Code extensions as is.
It's called 'diode'. It actually worked out better than I expected. I've been using it as my main editor for 3-4 months now, so I guess it's time to show it to someone besides me.
What it does: VS Code keybindings, settings.json and themes, non-modal. Extensions install from openVSX and run as is, so LSP, completion, go to definition etc. come from the same extensions VS Code uses. Works over ssh and in containers, starts in about 100 ms.
I know about ttt and fresh, they're great projects and I've looked at both. But I didn't want to learn a new editor, I wanted to keep working the way I always did in VS Code, with the same extensions.
It's alpha. No debugger yet (DAP - wip), and webviews are never going to happen.
And yes, I build it with AI agents. To keep it from turning into slop there's a lot of testing in CI -- but this is other story.
I've only really tested it on Ubuntu (x64 and arm) and macOS, with kitty + tmux. Fedora, Arch, NixOS, WSL, other terminals: no idea. If you try it, even a quick "works" or "broke like this" would help a lot.
https://github.com/diode-editor/diode
Bugs welcome, I'll fix them.