Open your first workspace

Open or create one

• Choose a local folder from the workspace launcher
• Use an existing Markdown project or create a new empty folder
• Give the workspace a recognizable display name in the launcher
• Confirm the folder remains available before switching to it

Representative layout

Directories appear as features are used, so a new workspace may contain only a few files. A mature workspace can look like this:

<workspace>/
  Documents/
  Tables/
  *.md
  *.kitable
  .kition/
    workspace.json
    assets/
    workflows/
    agents/
    sync/

What stays outside the workspace

Provider credentials, account sessions, logs, caches, the device workspace registry, and device-specific preferences live in Kition’s application data rather than the workspace folder.

After copying a workspace to another device, expect to reconnect providers, accounts, and external services.

Multiple workspaces

The launcher can remember several workspace folders and sorts them by recent use. Rename or remove entries without changing the folder name or deleting data on disk.

Keep separate work and personal workspaces when they have different sharing, retention, or provider-key requirements.

Portability limits

Copying or cloning a workspace is the supported portability model, but concurrent line-level merging of .kitable files and binary assets is not guaranteed. Treat cloud-folder sync as file replication, not real-time collaboration.