Claude Code: from the terminal to Desktop
Eight pages to move from the terminal to Claude Code Desktop: day one, the map of the window, the shortcuts and your first cloud routine.
Before anything else, import your sessions
Help, Troubleshooting brings in the terminal's.
Juan Andrés Núñez · wmedia.es
What is inside
Eight pages to keep beside you while you switch: checklists, tables and two prompts to copy.
- Day one: importing your terminal sessions and picking an environment.
- The map of the window: the conversation and the five panels around it.
- The shortcuts and gestures you will use from the first minute.
- Which conversation to open: side conversation, fork, subtask or message.
- Two prompts ready to copy: a side conversation and a whiteboard.
- Which panel for what: terminal, diff, browser, files and side chat.
- Your first cloud routine, step by step.
The criterion, in one sentence
Bring your sessions over on day one and stay a week or two before you judge it.
The switch is easy to start and easy to leave half done. You open the app, the first bit of friction makes you miss what you had in the terminal, and you go back. That is why the first page is not about features: it is about bringing over what you already had.
What changes your day the most is not where you type, but how many conversations you run at once and how they split the work. A side conversation for one topic, a fork for another path, a message to another conversation without jumping to it.
The cloud closes the loop: a routine that wakes up on its own, works in its environment and notifies you with a PR. You delegate what is clear and does not need you, and you give it the memory yourself, because every run starts like the first one.
What stays inside the PDF is the tables of shortcuts, conversations and panels, and the two prompts. Those are the pages worth keeping in view during the first days.
Frequently asked questions
Do I have to leave the terminal?
No. Desktop has its own terminal panel, and Claude sees the output of the commands you run there. The first thing the guide does is bring over your CLI sessions, so you do not start from zero.
What is the difference between a side conversation, a fork and a subtask?
A side conversation carries one topic or task with its own prompt and reports to the main one. A fork opens another path with all the context. A subtask is a subagent that works on its own, orchestrated by Claude.
Why do my messages between conversations sit waiting?
Because the conversations that receive them ask for permission. Turn on auto mode or skip permissions in all of them; otherwise the messages wait in a queue.
Does a cloud routine remember what it did last time?
No. Every run starts like the first one, so you give it the memory yourself. That is why it pays to delegate only what is clear and does not need you.