Settings & integrations
Settings are organized for the logged-in user and for server-side integrations.
General & appearance
Section titled “General & appearance”- Theme presets, optional auto theme following the OS, default model selection; values sync from the server when available.
Git identity
Section titled “Git identity”- Default name and email used for Git actions; may be mirrored into global Git config on the host in supported deployments.
SSH key for Git (Docker / self-hosted)
Section titled “SSH key for Git (Docker / self-hosted)”On first startup the server creates an ed25519 keypair under the config volume (.ssh/id_ed25519 and .ssh/id_ed25519.pub). Settings → Git shows the public and private key so you can register the public key on your Git provider and use SSH remotes for git push.
- Add the public key where your host expects it (user SSH keys, deploy keys, etc.).
- Use an SSH remote URL; HTTPS remotes do not use this key.
- The private key is sensitive; anyone with it can authenticate as this identity wherever the public key is trusted.
Agent authentication
Section titled “Agent authentication”- Cursor and Claude: status, login flows using an embedded terminal (xterm + WebSocket PTY), logout, optional Claude API token storage.
- Mistral Vibe API key (optional) when used by your deployment.
- Shows MCP status (enabled, port).
- Configure MCP client servers (stdio command or HTTP URL with headers) for extended tooling.
Notifications & API access
Section titled “Notifications & API access”- Web push: browser permission and subscription against server VAPID keys.
- API tokens: create named tokens (secret shown once), revoke, observe last-used metadata.