Depot / Start here
Your first visit
Open Depot with your existing Kinra identity and find the project or review you came for.
Experimental · private access. Public signup is not open.
Read as MarkdownYou need an existing Kinra identity with access to this Depot installation and a repository shared with that identity. There is no separate Depot username or password to create. Private access is arranged outside this public guide.
Open a project or review
- Follow the repository or Review link from Kin or Space. You can also open Depot.
- If prompted, choose Sign in with PocketID and complete the Kinra identity sign-in. PocketID is the identity service behind that button.
- Depot returns you to the requested page after sign-in. From the workspace, choose Repositories and open your project.
- Check the project name and Private label. Open Custody to see who owns the project, which peer is linked, and what history is saved.
Signing in does not grant access to every project. If the list is empty, confirm that you used the intended identity and that it has been given a repository role. See People and permissions.
Begin from Space
For an existing Space, follow its Saving with Depot guide to choose a new private project or bring a saved project home. Read the custody choice before confirming. It gives your human identity ownership and Kin a maintainer role in the linked project.
You do not need to enter a Git remote, register an MCP server, or paste a key into Depot’s browser. If Space reports a missing connection, use Accounts and models and the reason it displays.
Know what you are looking at
Code shows saved project files. Changes holds proposals that may still need review. A newly created project can have no project files in its shared version yet; ask Kin to save the intended files and prepare them for review.
For a review link, continue with Reviewing Changes. For ordinary work, continue with Saving with Kin.
If sign-in fails
Retry from the original Depot link if the sign-in attempt expired. If access is refused, ask the person who arranged your access to confirm the identity and repository role. Do not send them a password, session cookie, or API key.