Published: 2026-04-15

Claude Code Desktop App: Project-Organized Sessions and Multi-Tasking — Full Tutorial

Chapters / key moments (click to jump — plays here on the page)

Anthropic completely redesigned the Claude Code desktop experience. Alex Finn argues the new desktop app is now better than the CLI for most workflows — project-organized sessions, multiple concurrent sessions per project, and visual session management make multi-tasking between codebases practical for the first time.

Source video

"Claude Code for Desktop is the BEST way to build apps with AI EVER (full tutorial)" by Alex Finn — Watch on YouTube →

Key Takeaways

The new desktop app organizes everything by project — each project can run multiple concurrent sessions, and the UI shows all active sessions at a glance. This fundamentally changes how multi-feature development works.
Session management is now visual: you can see which sessions are active, switch between them instantly, and track which is consuming the most context — none of which was possible in the CLI without manual tab juggling.
Vibe coding entry point: the redesigned interface makes Claude Code accessible to developers who found the terminal intimidating, without removing any capability for power users.
CLI remains fully available — the desktop app is an interface layer over the same underlying system. All CLI commands, skills, and MCP configurations work identically.
Parallel feature development workflow: run auth in one session, UI in another, tests in a third — context stays isolated between sessions, so changes in one don't pollute the others.

The Project Organization Model

The core UI change is a project-first hierarchy. Instead of a flat list of sessions, you create projects and sessions live inside them. When you open the app you see your projects, click one, and see all its sessions — currently running, paused, or archived.

For Finn's use case building the "Henry app," he showed three concurrent sessions in the same project: one for scanner functionality, one for the UI redesign, and one for integration tests. Each session has its own context window; they share the codebase but don't share conversation history. When one session makes a file change, other sessions pick it up on their next read — cooperative parallelism without coordination overhead.

Related on OpenClawDatabase

Claude Cowork Setup — getting started with the full Claude Code environment
Session Commands Guide — managing context across multiple sessions

What you can actually set up from this

Extracted from the video's own transcript — the specifics the original summary left out.

Reproducible steps

Local versus cloud sessions, and the rule that separates them
<strong>Local</strong> changes code on your own machine, so the rule is that each concurrent session must touch <em>clearly separate parts</em> of the app or they conflict. <strong>Cloud</strong> takes your code from GitHub, runs on Anthropic's servers, and you pull changes down — which gives more freedom to have sessions overlap, because you merge them one at a time. The presenter runs mostly local for simplicity.
Pin tasks and plan to the interface
The top-right panel control lets you pin panes. The recommended pair is <strong>tasks</strong> (what the agent is working on, what is done, what is next) and <strong>plan</strong> (the high-level view to return to when you lose the thread across many parallel sessions). A live browser preview pane is also available.
Read the attention dot
A <strong>yellow dot beside a session means it needs you</strong> — an approval or a decision. With several sessions running across several projects, this is the mechanism that makes multitasking tractable: you are notified rather than polling.
Sessions organise by project
New session → choose local or cloud → choose the project folder, and the session is filed under that project. For a first-time setup: Code → new session → local → pick a folder, and organisation follows automatically.
Know which of the three tabs you want
<strong>Chat</strong> for brainstorming and unrelated questions. <strong>Cowork</strong> for working with files on your computer without writing code — the worked example is downloading a year of credit-card statements into one folder and having it categorise and build a spreadsheet, reducing a 10-hour annual task to about one. <strong>Code</strong> for the coding sessions above.

Gotchas

The CLI remains the most feature-complete surface; a few advanced features are CLI-only. The presenter's view is that the desktop app is now the better daily driver anyway.
The local-session rule is the one that costs you if ignored: two local sessions editing overlapping code will conflict, and nothing stops you starting them.
Timings and interface details are from April 2026 and the desktop app has changed substantially since; treat the workflow shape as durable and the specific panels as a snapshot.

← Back to News digest · See also: Claude Cowork guide