# Projects and workspaces

> Give work its own folder, open its overview, and keep track of repository changes.

**Experimental · private access. Public signup is not open.**

<!-- SOURCE: src/routes/+page.svelte, src/lib/Workspace.svelte, src/lib/WorkspaceHealth.svelte, src/lib/Source.svelte, internal/home/workspaces.go, internal/home/workspace_health.go -->

A project gives a folder its own place in the sidebar. Its workspace holds
sessions, Files, Source, and Terminal. Projects on the same machine can access
shared files; creating a project is not an isolation or permission boundary.

## Choose where work belongs

| Choice in New project | Use it for |
| --- | --- |
| **Local folder or GitHub repository** | A folder on your machine, optionally cloned from an existing GitHub repository. |
| **New private project in Depot** | A new repository kept privately in Depot, after your explicit custody choice. |
| **Recover a project from Depot** | An existing saved Depot repository you want to bring onto this machine. |

An existing GitHub repository keeps its configured remote. It is not moved to
Depot by registering it as a project.

## Create a local or GitHub project

1. Open **Projects → New project**.
2. Enter a **Project name** and choose **Local folder or GitHub repository**
   under **Where it belongs**.
3. For a GitHub clone, provide the repository. You can also use **Your profile →
   Manage GitHub… → Bring into a project** to fill the form from a repository.
4. Choose **Create project**.
5. Space opens its first session in Chat. Read Kin's trust decision for the
   new workspace before continuing.

**You should see:** the project in the sidebar and its name above the session.
If setup stops, Projects retains the attempt. Choose **Resume project** and
retry it after resolving the reported problem.

## Read the workspace Overview

Click a workspace name in the sidebar or topbar. Its Overview shows live and
recent saved sessions, repository status, and key documents. Managed Depot
repositories also show custody and inspected Changes; portfolios show members.

[![A fictional Garden workspace overview in Paper.](/docs-assets/space/workspace-desktop.png)](/docs-assets/space/workspace-desktop.png)

*A local example project. The overview brings sessions, documents, and local
measurements together; it does not run a review automatically.*

Use **New session** to start work or choose an existing session to continue it.
Files, Source, and Terminal open in this workspace. Opening Overview leaves
your browser's current session attachment while Kin can keep working.

**Workspace health** reports guidance files, declarations, and nearby
conventions. Token counts are estimates of file size, not the session's actual
model usage or a compliance score. Missing files and unreadable files remain
distinct. **Refresh workspace** reads current facts.

**Review with Kin** starts a new session for a read-only alignment assessment.
Kin examines the guidance and suggests improvements with evidence. Review
those suggestions before asking for changes.

## Keep local Git history

For a local or GitHub repository, **Source** shows the branch and files marked
modified, added, untracked, or in conflict. Review the changes, enter a commit
message, and choose **Commit changes** to keep a local checkpoint.

With a remote configured, **Fetch** reads remote updates, **Pull · fast-forward**
brings compatible updates into the checkout, and **Push branch** sends your
branch after confirmation. A local commit is not a remote copy.

A folder inside a repository is ordinary files; Source works at the repository's
own root. If an interrupted merge is reported, resolve its conflicts or use
**Undo interrupted merge** after reviewing what will be discarded. Commits stay
blocked while conflicts remain.

For several related repositories, continue with [Portfolios](/docs/space/portfolios/).

_Source authority: Kinra Site (src/content/docs/space/projects.md)._