Back up and move a workspace

What is workspace-owned

• Markdown documents and .kitable table files
• Workspace assets and attachment metadata
• Whiteboard and workflow data stored in the workspace
• Agent sessions, messages, events, plans, goals, artifacts, and subagent state under .kition/agents
• Workspace sync definitions and state under .kition/sync

What is not included

• Provider keys and account/session tokens
• Application logs and caches
• The device’s workspace launcher registry
• Device-specific display, shortcut, proxy, and notification preferences

Git and privacy

Git works well for Markdown and other reviewable text, but inspect .kition before committing. Agent history and sync state can contain prompts, generated text, record values, email metadata, or other project-sensitive material even when credentials are excluded.

Large images, PDFs, and other binary assets may need Git LFS or a separate backup strategy. Concurrent merging of .kitable files and binaries is not guaranteed.

Third-party folder sync

A folder-sync service can replicate the workspace between devices, but Kition does not describe this as real-time collaborative editing. Two devices changing the same table, workflow, or binary asset can create conflicts that require manual recovery.

• Test the selected sync service with a disposable workspace first
• Wait for synchronization to finish before opening the same workspace elsewhere
• Keep a separate versioned or offline backup
• Review conflict copies instead of deleting them automatically

Restore or move

• Copy or clone the complete workspace to the target location
• Open the folder from the Kition workspace launcher
• Verify documents, tables, attachments, Whiteboards, and workflows
• Reconnect provider credentials, Kition Account, email, and other external services
• Run a small read-only Agent task before resuming automated work