Claude Code デスクトップアプリ完全ガイド：新UIで変わった15の機能を初心者向けに解説

m0h @exploraX_ claude code's redesigned desktop UI - the complete guide for beginners 6 13 79 17K claude code's desktop UI was rebuilt from the ground up, here's everything that changed and how to set it up as a beginner. #1 — what actually changed before this update, claude code was a terminal. one session. one task. you watching it scroll until it finished. that's gone. the new desktop app is a full parallel workspace — multiple sessions running at once, each visible in a sidebar, each working independently. you're not waiting on claude anymore. you're directing it. anthropic said it themselves: the app is "built for how agentic coding actually feels now." 0:32 #2 — who can use it + how to get it available on pro, max, team, enterprise, and api access. free tier — not yet. setup: — go to claude.com/download — download for mac or windows — sign in with your anthropic account — open the app → you're in the sidebar immediately no config files. no terminal setup. just open it. #3 — the sidebar every active session, every recent session — one unified panel on the left. filter by status, project, or environment. group by project. when a pull request closes, the session auto-archives. no manual cleanup. this is the feature that makes parallel work actually manageable. #4 — running multiple sessions this is the core workflow the whole redesign was built for: — open a session → give claude a task (say, refactoring a component) — while it runs → click "new session" — point session 2 at a different task (writing tests for another module) — group both under the same project — click between them freely — claude keeps working on task A while you review task B you're no longer idle while claude writes code. you're running 2, 3, 4 things at once and reviewing results as they land. #5 — drag-and-drop workspace every pane — terminal, preview, diff viewer, chat — is fully movable. practical beginner layout: chat left (full height) · terminal top-right · diff viewer bottom-right gives you the conversation, the output, and the code changes all visible at once. layout saves per session — set it once, done. #6 — integrated terminal before: run a test → alt-tab to system terminal → navigate to directory → run command → switch back to claude → explain what happened. now: terminal is built into the app. claude sees the output. you see the output. everything stays in one place. every context switch you eliminate is a workflow that actually gets finished. #7 — file editor open and edit files directly inside claude code. no more jumping to VS Code mid-task to make a quick change. and claude sees your edits in real time — meaning it has context on what you changed without you explaining it. #8 — diff viewer (rebuilt) large diffs used to be slow and painful to navigate. now it handles big changesets fast, all in-app. combine this with parallel sessions: claude finishes a refactor in session one → you review the diff → session two is still writing tests. review no longer blocks everything else. #9 — preview pane render HTML files, PDFs, and local app servers directly inside claude code. if you're building frontend — rendered output sits right next to the code generating it. no dev server in a separate terminal. no browser tab you keep refreshing. #10 — side chat (the feature most will miss) cmd+; on mac · ctrl+; on windows/linux a side chat branches off your main conversation — pulls in the full context — without contaminating the main task. use case: claude is halfway through building a feature. you want to ask a question about the approach without derailing the active session. side chat. ask. get the answer. main session keeps running. memorize this shortcut. you'll use it constantly. #11 — view modes three modes controlling how much of claude's process you see: — verbose → every tool call, every file read, every decision point — normal → key actions and outputs, no noise — summary → results only beginner tip: start on normal. switch to verbose when something breaks and you need to trace what went wrong. use summary when you're juggling multiple sessions. four sessions on verbose is chaos. #12 — SSH support (now on macOS) run claude code sessions on a remote server directly from the desktop app. was linux-only before. session runs on the remote machine's resources — not your laptop's. large codebases, heavy builds — this changes what's possible from a macbook. file this one away. you'll want it when projects get bigger. #13 — usage dashboard real-time context window consumption and session usage, built into the app. every session has a context window limit. hit it mid-task and output quality drops — or the session cuts off entirely. the dashboard shows where you stand before that happens. approaching the limit → wrap up the task → start a fresh session. #14 — shortcuts worth knowing cmd+/ or ctrl+/ → full shortcut list cmd+; or ctrl+; → side chat (don't sleep on this) new session shortcut → parallel session from anywhere session switching → jump between sessions without touching the mouse don't try to memorize all of them. just start with the side chat shortcut and the session switcher. #15 — the bigger picture claude code is no longer a terminal tool you tolerate because the model is good. it's a full development environment. an IDE built by the same company that builds the model — which means the integration between model capability and app design is tighter than anything cursor, windsurf, or copilot can match. those are wrappers around someone else's model. this is the model maker building the interface around its own agent. parallel sessions, drag-and-drop workspaces, built-in terminal, real-time file editing — this is anthropic planting a flag at the IDE layer. the era of watching one agent work on one task at a time is already starting to feel like the old way. follow for more AI content like this!!! Want to publish your own Article? Upgrade to Premium 7:21 PM · Apr 20, 2026 · 17.6K Views 6 13 79 83 Read 6 replies