Settings
This part of the docs explains every setting in Splitkick. For each setting you get:
- Default: the value of a new install.
- What it does: the real behavior, also the parts that the label does not tell.
- Why change it: who the setting is for, and what you get when you change it.
- Cost: what it costs in tokens, usage quota, speed, disk or privacy. Only when there is a cost.
Open the settings
- App settings: press ⌘, (Ctrl+, on Windows and Linux), or use Settings in the sidebar. The search field at the top finds a setting by its name or by a keyword, also a single magic prompt or a shortcut.
- Project settings: click the gear icon on a project row in the sidebar, or right-click the project and select Project Settings. The command palette (⌘K) has Project Settings too.
App settings apply to all projects. A project setting applies to one project and wins over the app setting with the same name, for example Default Backend.
Per device or for the whole instance
Most settings are kept by the Splitkick instance, so the desktop app and each Web Access browser share them. Some settings are kept per device: each app window, browser or phone has its own value. These are:
- everything in Appearance and Terminal, and the Keybindings
- Debug mode (Experimental)
- in General: Editor, Terminal, Git Client, Open In, Compact chat view, Expand tool calls by default, Confirm before closing, Desktop notifications and the three sound settings
So when you change the theme on your phone, the Mac keeps its theme.
The pages
The pages follow the groups of the Settings dialog:
| Page | Panes |
|---|---|
| General | General |
| Appearance and terminal | Appearance, Terminal, Keybindings |
| Backends | Claude, Codex, OpenCode, Cursor, PI, Command Code, Grok, Kimi Code, Antigravity CLI, GitHub CLI, CodeRabbit CLI |
| Magic Prompts | Magic Prompts |
| Agents and plugins | Agents, Opinionated |
| Connectivity | Providers, Web Access, Web Browser, MCP Servers, Integrations |
| Usage and Experimental | Usage, Experimental |
| Project settings | General, Integrations, Mr. Robot, MCP Servers, splitkick.json |
Settings that cost the most
Three settings can use a lot of tokens or usage quota in the background: Auto-save context, Mr. Robot with yolo, and five reviewers in Code Review. Read their Cost notes before you turn them on.