Settings & integrations
Settings let you configure your Nova Code instance — from appearance to agent connections. Open Settings from the sidebar.
Appearance
Section titled “Appearance”- Theme: Choose from preset themes. The auto option follows your OS/browser preference, using Deep Space for dark mode and Cloud for light mode by default. OLED uses a true black background and elevated grays for surfaces, with the same rose accent as Infrared—suited to AMOLED displays and low ambient light.
- Default model: Set the default AI model for new sessions (including an auto option that lets the agent decide).
Git identity
Section titled “Git identity”Set a default name and email used for all Git operations (commits, pushes). These are applied globally and can be overridden per workspace.
SSH key for Git
Section titled “SSH key for Git”On first startup, the server generates an ed25519 SSH keypair under the config volume. The Settings → Git screen shows both keys:
- Public key — copy this into your Git provider (GitHub, GitLab, etc.) as a deploy key or SSH key.
- Private key — treat as a secret; anyone with it can authenticate wherever the public key is trusted.
Use SSH remote URLs (e.g. git@github.com:org/repo.git) for pushes. HTTPS remotes use the host’s credential helper, not this key.
Agent authentication
Section titled “Agent authentication”Cursor & Claude
Section titled “Cursor & Claude”Both agents are authenticated through an embedded terminal in the browser:
- Go to Settings → Agent Auth.
- Click Login for the agent you want to configure.
- Complete the interactive authentication flow in the terminal that appears.
- Credentials are stored under the config volume and persist across restarts.
Status indicators show whether each agent is currently authenticated.
Mistral Vibe (optional)
Section titled “Mistral Vibe (optional)”Mistral Vibe requires two things:
- The
vibeCLI must be installed and onPATHon the server (override with theVIBE_COMMANDenvironment variable if needed). - An API key must be configured in Settings → Mistral Vibe.
The dashboard only shows Mistral Vibe as an available agent when both conditions are met. The API key is stored under the config volume.
Chat rendering merges assistant text from the Vibe stream so repeated final chunks or cumulative full-text snapshots do not show as duplicated sentences in a single reply.
MCP client servers
Section titled “MCP client servers”Connect external MCP servers so your agents can use additional tools and capabilities:
- Go to Settings → MCP.
- Add servers by specifying either a stdio command or an HTTP URL, with optional environment variables or headers.
- Use Test connectivity to verify each server before agents load it. Stdio entries are briefly spawned; HTTP entries receive a test GET request.
MCP configuration is written to the config volume so Cursor reads .cursor/mcp.json and Claude merges into .claude.json automatically.
Push notifications
Section titled “Push notifications”Enable browser notifications to be alerted when long-running sessions produce output:
- Grant browser notification permission when prompted.
- Nova Code uses VAPID keys (generated automatically) for web push — no external service required.
The notification title still includes the workspace and session name; the body shows a short preview of the last assistant reply, or the last tool result if the run finished without a final text message.
REST API access
Section titled “REST API access”The API uses the same JWT you receive after login. To make API calls from scripts or other tools:
curl -H "Authorization: Bearer <your-jwt>" http://localhost:3030/api/workspacesThere is no separate API key system — use the JWT from your browser session.