Claude Code Desktop — Operator Cheatsheet

Desktop vs CLI — when to use which

The Claude Desktop app has three tabs: Chat, Cowork, and Code. This cheatsheet covers the Code tab — a GUI for the same agent engine as the CLI, optimized for parallel sessions, visual diffs, and integrated terminal/browser panes.

Use Desktop when you juggle multiple repos or want diff review without tmux. Stay in CLI for SSH servers, scripts, and minimal environments.

Core concepts

| Concept | Meaning |

|---------|---------|

| Session | One conversation + project folder + isolated changes |

| Sidebar | All active/recent sessions; run several in parallel |

| Pane layout | Drag-and-drop grid: chat, diff, terminal, files, browser |

| Side chat | Branch question using context without polluting main thread |

| Worktree | Parallel sessions can use Git worktrees for isolation |

Desktop shares skills, plugins, MCP config, and CLAUDE.md with the CLI.

Install and first launch

1. Download Claude Desktop from Anthropic (Pro/Max/Team/Enterprise or API-enabled account)
2. Open the Code tab
3. Pick a project folder — same as you would cd in CLI
4. Run /doctor in the prompt box to verify environment

CLI handoff: In terminal session, run /desktop to continue in the app with history intact.

Permission modes (critical)

Cycle with Shift+Tab (verify with Ctrl+/ or Cmd+/ shortcut list on your OS):

| Mode | Behavior |

|------|----------|

| Manual | Approve each tool use |

| Accept Edits | Auto-approve file edits after you trust the session |

| Plan | Plan only — no file writes until you promote |

| Auto / Bypass | Faster; use only on low-risk branches |

MyGearHut default: Plan for multi-file work → Accept Edits for vetted tasks → never Bypass on main.

Slash commands worth memorizing

| Command | Purpose |

|---------|---------|

| /plan | Enter dedicated plan mode |

| /doctor or /checkup | Diagnose install, MCP bloat, heavy hooks |

| /desktop | Move CLI session to Desktop (from terminal) |

| /btw | Side question without derailing main task |

| /help | Command list for your version |

| /permissions | Tune allow/deny tools |

Browse + → Plugins to add capabilities without manual MCP wiring.

Keyboard shortcuts (macOS / Windows)

| Action | Mac | Windows |

|--------|-----|---------|

| Shortcut cheat sheet | Cmd+/ | Ctrl+/ |

| Side chat | Cmd+; | Ctrl+; |

| Cycle permission modes | Shift+Tab | Shift+Tab |

Use the in-app shortcut panel — bindings update between releases.

Workspace layout recipes

Recipe A — Ship a feature

[ Chat 60% ] [ Diff 40% ]
[ Terminal full width bottom ]

Run tests in terminal while reviewing diffs above.

Recipe B — Full-stack loop

[ Chat ] [ Browser preview ] [ Terminal ]

Start dev server; Claude verifies UI in Browser pane.

Recipe C — Research + implement

Main chat for implementation; side chat (/btw) for docs questions.

Drag pane borders to save layouts per project.

Session management

• New session from sidebar for each independent task
• Filter/group sidebar by project or status when juggling many agents
• Cloud / SSH sessions — continue long jobs off-machine (plan-dependent)
• Watch tasks pane for subagents and background commands

Before starting parallel sessions, confirm separate Git branches or worktrees — avoids merge nightmares.

Built-in panes

| Pane | Use |

|------|-----|

| Diff | Comment inline; approve/reject hunks |

| Terminal | npm test, git, docker — same machine |

| File editor | Spot edits without leaving app |

| Browser | Local dev preview + external docs (sandboxed) |

Configure preview servers so Claude hits the correct localhost port.

Connectors

Link GitHub, Slack, Linear, and similar integrations from settings/connectors menu (availability varies by plan). Use for PR monitoring and CI awareness — not as excuse to skip local tests.

Computer use (macOS / Windows)

Desktop can control screen/apps for tasks GUI tools require. Enable deliberately; scope which apps and folders are in bounds. Treat as Yellow zone in the AI Decision Test.

View modes

Toggle Verbose / Normal / Summary to control how much tool-call noise you see. Summary for monitoring many agents; Verbose when debugging why Claude picked a wrong file.

Daily operator loop

1. Open sidebar → pick yesterday's session or spawn fresh branch
2. /doctor if anything feels sluggish (unused MCP costs context)
3. Plan mode for task → execute → diff review
4. Terminal: lint/test before push
5. Side chat for "why did we choose X?" without resetting main thread

Troubleshooting

| Symptom | Try |

|---------|-----|

| Slow context | /doctor — prune unused MCP/skills |

| Wrong project files | Confirm session folder in sidebar header |

| CLI/Desktop drift | Same CLAUDE.md; restart app after config change |

| Preview wrong port | Set preview server config explicitly |

Cheatsheet checklist

• /doctor run this week
• Permission mode visible before large edit
• Parallel sessions isolated by branch/worktree
• Tests run in integrated terminal before merge
• Side chat used instead of polluting main prompt

---

Pair this with Claude Code From Zero and Boris Cherny Principles. More gear in the MyGearHut library and The Gear Drop newsletter.