Main interface and sessions

Sidebar

The sidebar has two parts. On top is a column of fixed entries: New chat, Extensions (a collapsible group containing Connectors / Skills / Plugins / Quick commands / Agents), Channels, Scheduled tasks, Memory, and Friends (see Friends). Below is the session list, divided into four sections:

• Pinned tasks: sessions you pinned by hand.
• Channels: sessions that come from external instant messaging; see Channels.
• Projects: projects grouped by working directory; expanding one shows the sessions under that project. Create a project for a directory and the sessions inside it revolve around real files and commands; ordinary chats not attached to any project are listed separately in the section below. Workspaces and each friend's task conversations also form their own groups in this section. These groups can be dragged into order, or moved by holding Alt and pressing the up and down arrow keys, and the order is remembered.
• Recent tasks: all remaining historical sessions.

Each of the four sections can collapse on its own, and the collapsed state is remembered for next time. When a collapsed section has activity, a badge appears on it, so nothing running gets missed while it is folded away. If the selected session's title is too long to fit, it scrolls automatically as a marquee.

Session rows also carry status indicators, and the sorting puts sessions that are waiting on you first, with the priority order waiting for input > unread > running > idle:

• "Needs input" is a blue pill — it is asking you something (a follow-up card or a question that needs your choice). Clicking the pill snoozes it for a minute so you can finish what you are doing first.
• "Awaiting approval" is a green chip — there is a permission card waiting for you to let it through.
• The sidebar toolbar has an activity view toggle that shows only sessions with something going on; paired with a "jump to the next session needing attention" command, you can step through them one by one.
• Whether a session is "running" depends only on its own turn: once the turn ends, the sidebar and composer stop showing it as running even if background sub-agents it dispatched are still working; follow their progress in the Overview panel.
• Global search (⌘/Ctrl+K) covers every session, including collapsed sections, sessions not yet loaded by paging, and friend conversations.

Session operations

Every session supports: rename, pin, export, copy session ID, continue in a new task (forks a new session from the current one, marked as a "forked session"), report an issue, archive, and delete. All of these live in the ⋯ menu on the right of the session row. Archived sessions can be viewed, searched, unarchived, or deleted under "Settings → Archived sessions".

• A fork is a snapshot: at the moment the fork is created, the original session's record is copied, and the two lines then go their separate ways — messages added to the original afterwards never flow into the fork. If the original session is running, it first waits for the current turn to finish (up to 20 seconds) before forking; otherwise the fork would only capture half a conversation. You can also fork from a specific message: forking from one of your messages carries over only the content before it, while forking from an assistant reply carries over the whole conversation up to and including that reply. A fork inherits the original session's project and working directory, and keeps the original session's title.
• "Revert" rolls back the conversation only; it does not touch files. Reverting from a message returns the conversation to the state before that message was sent: the message's text goes back into your input box, the messages after it are removed from the context, and files on disk stay exactly as they are — the confirmation dialog says so explicitly. "Delete everything after" likewise only affects the conversation.
• Undoing files as well is a different action: the undo button on a turn's changes block, which restores files specifically and leaves the conversation alone. That one depends on file checkpoints, and checkpointing is off by default with no toggle in the UI (it is the checkpointing setting in the engine configuration, and you can ask Klaus to turn it on for you). So by default "revert" never touches files at all, and undoing files tells you there is no checkpoint available — it is not an undo button that can take back broken code changes; if you want that, enable checkpointing first.
• Unanswered questions come back to the composer: if Klaus asked you a question during a task and you switched away before answering, it reappears above the composer when you return to the session, so you do not have to scroll back for it. Some questions are optional clarifications: Klaus keeps working on a reasonable assumption, and you can answer at any time to correct course, or skip or postpone it; the task does not stop for it.
• When enabled, snapshots are kept in a shadow git repository (~/.klaus/checkpoints/<project-fingerprint>/): the worktree points at your project while the history lands in the shadow repository, so your own .git, branches, and staging area are never touched, and the project itself does not need to be a git repository (only git on the machine). Restoring is destructive: tracked files are changed back, untracked files are removed, and everything done after the snapshot is gone.
• Archiving is not deleting: the session moves from the sidebar to "Settings → Archived sessions", can be unarchived at any time, and you can even fork directly from an archived session to continue. Archiving requires that the session is not currently running; if it still has background processes, the confirmation dialog adds a line: "This session still has N background processes active".
• Running tasks resume on their own after a restart: whether it is an update restart, a crash, or you quitting and reopening the app, Klaus remembers which sessions still had an unfinished turn when it last exited and automatically clicks continue for you on startup, so you never have to hunt them down one by one. Sessions started by channel messages are not covered.

Multiple windows and Find

• "New Window" in the menu opens additional independent main windows, each keeping its own drafts and panel layout, so you can follow several tasks in parallel.
• "Find" (⌘/Ctrl+F) searches the content of the current window — chat, files, changes and browser pages — with a match count, case sensitivity and Find Previous / Find Next; results refresh live while a reply streams. It is separate from global search (⌘/Ctrl+K), which covers every session.