What Space does
Return to your work
Find live and saved Kin sessions by workspace. Read the timeline, answer decisions, and keep files close to the conversation.
Give projects a home
Work in ordinary folders, bring in GitHub repositories, or explicitly choose private Depot custody. Portfolios keep each member repository independent.
Make something you can use
Ask Kin for an interactive explanation or small tool. Keep useful results and build personal widgets for your Home board.
Use your machine
Edit and download files, rejoin a retained shell, use Docker, and connect the machine to your tailnet when its integration is available.
Begin with one useful thing
- Come inside
Sign into an existing Space and check that a model connection is ready. Home is a place to begin without setting up a project first.
- Work with Kin
Ask for an outcome, share relevant files, and review the questions and actions that follow.
- Keep and return
Save files and project checkpoints, pin useful views, and continue a conversation on your next visit.
Access and current limits
- Space is experimental and access is private. Public signup is not open. The manual helps existing occupants; it does not announce a public service or self-service provisioning.
- Kin owns conversation history, model connections, tools, and approvals. Depot owns saved Git custody, review, and recovery.
- Workspaces share one personal machine. They are not separate security boundaries.
- An internet connection is needed to reach the machine. Browser disconnection, machine restart, and a verified backup are different events.
- Desktop and phone layouts have browser acceptance coverage. Physical-device installation, sharing, and background behavior still depend on the browser and device.
Source authority: The Kinra Space repository owns behavior and deployment evidence; Kinra Site authors the user manual against an exact reviewed Space revision. Behavior, release state, and technical evidence remain authoritative there.