terminal-code – VS Code inside the terminal: SKIP, 42/100 | Ideas Lab

A terminal-based VS Code clone targeting developers who work exclusively in SSH sessions or remote environments.

The pain

Developers working on remote servers via SSH face friction switching between terminal editors (vim, nano) and full IDEs. They lose IDE features like autocomplete, debugging, and file navigation. SSH tunneling VS Code is slow and adds latency.

The gap

VS Code is Electron-based and resource-heavy. Lightweight terminal editors lack modern IDE features. No tool bridges this gap with a true IDE experience that runs natively in the terminal.

Build angle

Start by validating demand with remote/embedded systems developers, DevOps engineers, and sysadmins. Build a minimal version supporting syntax highlighting, file tree, and basic autocomplete. Charge per seat or as part of a dev tools bundle. Expand to debugging and language server support only if users show willingness to pay.

Strengths

Real problem for a specific segment (remote developers, embedded systems work)
Low barrier to distribution (just a binary or package)
Potential to be faster and lighter than VS Code
Existing terminal UI frameworks (Bubble Tea, Ink) reduce build complexity

Risks

Extremely narrow TAM, most developers use local machines or cloud IDEs (GitHub Codespaces, Gitpod)
VS Code dominance means users expect feature parity; building that is a multi-year effort
Vim and Neovim already own the terminal editor space with strong communities and plugins
Unclear monetization, developers rarely pay for tools; enterprise adoption is slow
High churn risk if VS Code adds native SSH support (they're already working on this)
Building a language server client, debugger, and extension ecosystem is massive scope creep

Fly Labs Method

Is the pain real, is there a gap, is it the right time, can one person build it.

42

Value Equation

Dream outcome and how likely it feels, against the time and effort it costs.

35

One-Person Business

Curiosity pull, identity fit, and a path from free value to paid for a solo creator.

58

Viral Frameworks

Hook strength, shareability, and how cheaply it can be tested.

48

Builder Lens

Evidence the problem exists, timing, defensibility, and a model that fits on a napkin.

52

Five lenses, one composite. How scoring works

The angle

Start by validating demand with remote/embedded systems developers, DevOps engineers, and sysadmins. Build a minimal version supporting syntax highlighting, file tree, and basic autocomplete. Charge per seat or as part of a dev tools bundle. Expand to debugging and language server support only if users show willingness to pay.

No market research recorded for this idea yet.

Excessive CAPTCHA challenges degrading GitHub login UX for enterprise users

GitHub's anti-bot protection forces users, especially those with organizational emails, to solve 10 blurry puzzles multiple times, creating an extremely painful and frustrating user experience.

Dev

BUILD

86FL score

GTA modders tediously manually edit assembly files for modpacks

Creating .oiv modpacks for GTA is tedious and error-prone due to buggy project manager software, forcing manual editing of assembly files.

Dev

BUILD

85FL score

BreezePDF – Free, in-browser PDF editor

BreezePDF lets you edit, sign, merge, compress, redact, OCR, fill forms, extract tables, and use 30+ more PDF tools — all in the browser, no sign-up. Files never leave your computer.I built it because when people search Google for common PDF tasks, many of the tools they find upload documents to a server. I wanted an option that keeps files local instead.I posted an earlier version on HN last spring: https://news.ycombinator.com/item?id=43880962At the time it only supported a small set of features. Over the last 10 months I rebuilt large parts of it and expanded it to nearly 40 tools, including several ideas that came from comments in that earlier thread.There is also now a desktop app for macOS, Windows, and Linux, plus a CLI/SDK for developers.

Dev

BUILD

85FL score

All Dev ideas