Croli
Reference
An option-by-option account of every settings screen and every switch in Croli, plus the standalone features in the left sidebar. If you want to know what something actually does, what its default is, or which platform it shows up on, look here.
The three features in the sidebar
Beside the settings, the left sidebar holds three features with a page each:
| Feature | What it covers |
|---|---|
| Plugins and skills | MCP servers and skills: adding capabilities to the workspace |
| Automations | Agent tasks that run again on a schedule or on demand |
| Library | A read-only index of the files that have passed through an agent |
All three rows can be switched off under View options → Navigation items; once they are, the status bar's quick-actions menu still gets you in.
How to reach a settings screen
The sidebar of Croli's settings window is arranged in four groups, but a fair number of pages are not in the sidebar — they hang off another page, or can only be reached by visiting the route directly. The tables below are ordered by "how you actually get in":
In the sidebar
| Group | Screen | What it covers |
|---|---|---|
| Workspace | Appearance | Theme, zoom, fonts, background image, chat area width |
| Workspace | General | Default terminal, hardware acceleration, close-window behavior, notifications and sounds |
| Workspace | Keyboard shortcuts | Every rebindable key combination |
| Workspace | Computer use | The limits on an agent reading and driving desktop windows |
| Workspace | Browser control | Built-in browser: where it opens, sharing permissions, profiles |
| AI | Agents | Installation, auth, models and native config of the four built-in CLIs |
| AI | Extension tools | Switches for the extra tools Croli hands to agents |
| AI | Model providers | Credentials for API providers you set up yourself |
| Integrations | Version control | Which git to use |
| System | System | Updates, launch at login, proxy, language, data and sync |
| System | Runtime logs | Log level and the live viewer |
Reached from elsewhere
| Screen | How to get there |
|---|---|
| Collaboration | The very bottom of the Agents page (Multi-Agent Collaboration) |
Where settings live, and who they affect
This deserves to be said once on its own, because it decides whether "I changed it on this machine" shows up on another one:
- Stored in the backend — shared by every client of the same Croli backend. Change it in the desktop window and the browser and mobile clients connected to the same backend change too. Agent configuration, model providers, extension tools, proxy, language, the default terminal and the Git path are all of this kind.
- Per device — applies only to this machine / this browser, and does not sync with the account. Appearance, keyboard shortcuts, desktop notifications, notification sounds and hardware acceleration are all of this kind. The one exception inside Appearance is the background image file itself, which lives in the backend and is shared by all clients.
A few rules that run through everything
Remember these and you will save yourself a lot of "why didn't my change do anything":
- Extension tools are injected when the agent starts. Flipping a switch does not affect a running session; it counts from the next launch.
- Most browser settings "apply to tabs opened from now on". The inspector, the hosting mode and the proxy all behave this way.
- Credentials are in the keychain, not in the backup. After a restore you have to re-enter the GitHub tokens.
- When you are connected to a remote server, "this machine" means the server. Computer use and backup/restore both act on that end.