desktop

Workspaces and sessions

Keep each conversation and its results connected to the right local project.

Desktopbeginner0.7.0 Stable
Verified 2026-07-21View sourceReport a docs issue

A workspace is the local project Kestrel may inspect or change. A session keeps the conversation, activity, and results for one line of work. One workspace can have several sessions, and each session remains connected to the project where it began.

Kestrel Desktop Mission Control showing run and session filters with a visible provider setup error
Mission Control keeps run history, session filters, and a blocking setup problem visible in the same view. Finish provider setup before starting the first session.

Continue an existing task

  1. Select the project from the workspace library.
  2. Open the session that contains the work you want to continue.
  3. Review the last messages, terminal state, and any waiting request.
  4. Confirm the active mode, model, and tools before asking Kestrel to proceed.

Start a separate task

Create a new session when the goal or working history should be independent. Do not create a replacement session merely because a run is waiting or failed; use the existing session’s control and recovery options first.

Install guidance for the project

Use the Agent skills panel to install a standard SKILL.md package from a public HTTPS Git repository. Choose the branch and, when the skill is inside a larger repository, its repository-relative directory. Desktop shows whether each skill is pending, ready, stale, failed, or waiting for removal, along with the installed commit and content digest.

Desktop checks for branch updates when the project is activated. If work is running, installs, updates, and removals wait until the workspace is idle, so a run always uses one stable, verified skill snapshot. Inspect a skill to see its exact source and installed instructions. Skills provide guidance only; they cannot grant tools, credentials, or additional workspace access.