# Accounts and models

> Connect the services you use and choose a model without confusing sign-in with permission to act.

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

<!-- SOURCE: src/lib/Profile.svelte, src/lib/KinraAccount.svelte, src/lib/ChatGPTAccount.svelte, src/lib/GitHubAccount.svelte, src/lib/GitHubManager.svelte, src/lib/ModelPicker.svelte, src/lib/Decision.svelte -->

Choose your name or avatar at the bottom of the sidebar, then **Your profile**.
Each connection shows its own readiness. Signing into Space, connecting a model,
and allowing an operation are separate steps.

| Connection | What it makes available |
| --- | --- |
| Kinra account | Kinra models and Depot access. |
| ChatGPT | Models available through your connected ChatGPT account. |
| GitHub | Repositories and credentials for Git operations. |
| Tailscale | Your Space machine on your tailnet; see [Tailscale](/docs/space/tailscale/). |

## Check the Kinra connection

Setup begins after Space sign-in and refreshes while it finishes. If offered,
choose **Continue account setup** or **Reconnect Kinra** and follow the flow.
A card that is not ready explains the reported state. Its green mark indicates
that Kin reports the connection ready.

## Connect ChatGPT

1. In Profile, choose **ChatGPT → Connect ChatGPT**.
2. Follow the displayed link and enter the code in the provider's sign-in flow.
3. Complete your own sign-in and consent.
4. Return to Space and wait for **Connected and ready**.
5. Open the composer's model control and choose an available model.

Connecting ChatGPT does not replace the default model automatically. Available
models and settings depend on what the connected service reports.

## Choose a model

The control at the lower edge of the composer shows the current model when Kin
knows it. Open it to choose a model and supported working-mode or reasoning
settings. Unavailable settings explain why they cannot be selected.

New sessions use the Kinra Gateway default unless you explicitly choose another
model. Your choice is remembered for later new sessions. Returning to an
existing session keeps that session's own model. You can choose a model before
starting your first session.

## Connect GitHub

1. Choose **GitHub → Connect GitHub** in Profile.
2. Complete GitHub's device sign-in using the displayed link and code.
3. Return and wait for **Connected as @…**.
4. Open **Manage GitHub…** to search repositories or filter by owner and
   visibility. **Bring into a project** begins a clone; **Use as portfolio…**
   begins [portfolio setup](/docs/space/portfolios/).

**At home** identifies repositories already registered in a workspace.
**Repair connection** repeats the device flow. **Disconnect GitHub** asks for
confirmation and keeps existing clones.

## Review Git access

Connecting GitHub makes credentials available; Kin still asks you to review
their use. Inspect the operation, repository, remote, and credential identity.
Choose **Use once**, **For this session**, **Remember this connection**, or
**Decline** according to the scope you intend.

If a request first sends you through GitHub sign-in, return to **Review Git
access** to make that decision. Provider sign-in alone does not approve the
pending operation.

## Sign out of Space

Use **Your account → Sign out**. This closes Kin and terminal connections in
every tab sharing that Space sign-in. Expiry does the same. Kin retains work and
tmux retains the shell; sign-out is not deletion or a provider-account revocation.

For failed or expired connections, use [Troubleshooting](/docs/space/troubleshooting/).

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