AI Disruption

AI Disruption

A Week on Claude Code Desktop: Terminal, Gone for Good

Claude Code Desktop review: split-screen diffs, auto CI fixes, and phone dispatch. See why I ditched terminal windows for good after one week.

Meng Li's avatar
Meng Li
Sep 16, 2026
∙ Paid

“AI Disruption” Publication 10,500 Subscriptions 20% Discount Offer Link.


To be honest, I looked down on the Desktop app at first. The terminal was working fine — type claude and get to work. Why bother installing another app?

Then last week I was working on three requests at once, flipping between three terminal windows, and pasted session A’s diff into session B. That’s when I decided to give Desktop a serious week. Here’s the conclusion up front: it’s not a terminal in a wrapper. It’s the same engine with a completely different way of working. The features below are the ones I actually paid for with real use.

First, get this straight: the session is the core unit

Open the Code tab. Every conversation is a “session” — its own chat history + its own project folder. You can run several in the sidebar at once, and they don’t interfere with each other.

The important part is the four settings when you create a session: runtime (local / cloud / SSH), project folder, model, and permission mode. Don’t just smash Next. Especially the environment field — more on how useful cloud sessions are later.

User's avatar

Continue reading this post for free, courtesy of Meng Li.

Or purchase a paid subscription.
© 2026 Meng Li · Privacy ∙ Terms ∙ Collection notice
Start your SubstackGet the app
Substack is the home for great culture