Build a Windows desktop app for running several Claude Code sessions

Fred built VibeDesk, a desktop for running several Claude Code sessions on Windows, with Claude Code writing nearly all of it: 169 commits and about 48,000 lines in three weeks.

Done withClaude Code· Nov 5, 2026

What they did

The author, Fred, started a Windows desktop app called VibeDesk for running several Claude Code sessions side by side, with a dock, a phone connection and a stats card. Over three weeks Claude Code wrote almost all of the code while Fred steered, tested each release and decided what went in. Features were requested in a sentence and usually arrived with tests in about ten minutes. Wishes from users were collected through GitHub issues.

How it went

The project reached 169 commits and about 48,000 lines in src. Between October 13 and 19 Fred shipped 29 releases in seven days, from version 0.7 to 1.9. The code generally worked, but the app got noisy: windows opened over the terminal, the dock filled up and the first start asked users to choose how much to see. The changes Fred is proudest of were cuts, such as new windows never covering Claude, moving new features into a More menu, dropping one of two tunnel options and moving to one tested release at a time with a freeze before it.

Worth knowing

Fred's main lesson is that the agent never pushes back, so deciding what should exist becomes the job, and Fred now asks who will open a feature and how often before asking for it. This is one solo project with no team or deadline, as the author points out, and no user numbers are given.

Try it

With Claude Code· 4 parts to fill in

We are building [app description] for [platform]. Before you write any feature I ask for, answer three questions in two lines each: who will open it and how often, what it pushes off the screen, and whether anyone would notice if it were missing. If the answers are weak, say so and suggest the smallest version or a place in [a secondary menu] instead. When I confirm, implement it with tests, keep new windows from covering [the main work area], and stop after one feature so I can test the build before the next release.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related