Other Panels

• Terminal: watch the live output of commands Klaus runs.
• Overview: what this session is doing right now and what it is doing it with, broken into several sections (see below).
• Plan: open the right-panel editor from a complete proposal to inspect and edit PLAN.md, then Save or Revert. This is separate from the execution progress checklist; see Plan mode.
• Goal: open the right-panel editor from the goal row above the composer to inspect the full objective and update time, then Save or Revert. Completion or clearing closes the editor; completion records remain in the conversation. See Goals and side tasks.
• Prototype: interface prototypes generated in chat open a full interface editor on the right. You and the agent read and write the same design document, with versions, branches and undo/redo; export images as PNG, JPG, WebP, SVG or PDF, or export a design file you can keep editing. Designs are saved with the conversation and survive app restarts. Provided by the official prototype design plugin bundled with the installer.
• Files and Changes: browse and directly edit files in the working directory, and see what changed in the code; see Workspaces, Git, and Changes.
• Mini: the small companion floating on the desktop; see Mini and Pets.
• Phone: "Settings → Remote Control", see Remote-control sessions. That page also has "Keep this computer awake while plugged in": while remote access is on and the computer is plugged in, it will not sleep and drop your phone's connection; it has no effect on battery.

Overview panel sections

• Plan: the execution task list and progress for the current turn. Empty when there are no tasks. Review complete proposals in the conversation and edit their full text in the Plan tab.
• Sub-agents: the background sub-agents that were dispatched, one row each with an avatar, task name and status. Only background ones are listed.
• Background processes: long-lived processes Klaus started (a dev server, for example), and whether they are still running.
• Computer Use: appears only when Computer Use has actually taken action.
• Artifacts: the files this session changed or produced. Click one to preview it in place, switch between source and preview, open it in a separate window, or reveal it in Finder; see Session Artifacts. To browse the whole project directory, use the "Files" panel.
• Citations: what this session actually drew on, split into three sub-tabs — skills, memory and MCP. "Why does it know this?" usually has an answer here.

Context usage is not in the Overview panel. It is the circular chip next to the input area.

How the phone connects

Read this when you are asking "why won't my phone connect":

• The local service the desktop opens binds only to 127.0.0.1 and does not open up to the LAN. Your phone can connect because the desktop dials out on a WebSocket to a relay, and the relay feeds the phone's requests back down that same connection. So you do not need to be on the same Wi-Fi, and you do not need to open a port.
• The relay is only a pipe; it grants no extra permission. Requests that arrive through it end up going through the same interface the desktop UI itself uses, so your phone can never do more than the desktop can.
• You must sign in to your Klaus account first: the relay verifies this desktop by account. When you are signed out, that leg never starts at all, and the page says "Please sign in first" outright instead of spinning on "Connecting" forever.
• Pairing credentials do exist, but they are deliberately not exposed in the UI: the settings page has a single toggle, "Allow remote control of this device", plus an account device list (rename or remove entries). There is no pairing code, no QR code and no reset button. To disconnect a device, remove it from the list, or just turn the toggle off.
• A dropped connection reconnects on its own (backing off over 1, 2, 5 and 15 seconds), with a heartbeat every 20 seconds in normal operation. Devices in the list show one of three states: online, reconnecting, or offline.