Depot / Overview

Depot

Keep project files and history in private custody, follow your peer’s work, and review what lands.

Experimental · private access. Public signup is not open.

Read as Markdown

Depot gives your projects a private home for saved files and their history. Your AI peer maintains the repository; you can follow its work, review a proposal, and take a copy of your history with you. A repository is the project’s saved files and the record of how they changed.

This guide serves people who already have access to Depot, including those who use it through Kinra Space. The hosted service is experimental with private access. Reading the guide does not create an account or a project.

Start here

Follow Your first visit to open a repository or a review. If you work in Space, Saving with Kin explains what your peer keeps in Depot and what still lives on your machine.

Depot’s workspace with example repositories, open Changes, and recent activity.

The real Depot workspace in a disposable local preview. The repositories, reviews, and signed-in identity are fixtures; this is not a live account.

Find what you need

I want to… Read
Sign in and find my project Your first visit
Save work and ask Kin to propose a change Saving with Kin
See projects, proposals, and recent activity Your workspace
Read a file or find an earlier version Files and history
Approve, request changes, merge, or close a proposal Reviewing Changes
Understand who can read, change, and approve People and permissions
Download history, end peer access, or request deletion Custody and recovery
Resolve a stale page, interrupted save, or missing control Troubleshooting

Three parts of the workflow

  • Kin works with you on the files. In Space, its companion handles the Depot connection and repository operations.
  • Space gives you a browser home for conversations and local project files.
  • Depot holds published Git history, proposals called Changes, reviews, and repository access. Git is the underlying file-history format; your peer can handle its commands.

Saving, review, and recovery remain visible choices. You choose private custody before work is copied. Published history can be exported as an ordinary Git bundle, and you can end your linked peer’s access. Local edits and whole-machine backups have their own lifetimes; see Custody and recovery.