General

Settings → General brings together the default terminal, rendering acceleration, close behavior, notifications and sounds.

What this screen owns splits in two, with different reach:

• Backend-stored (default terminal, colorize command output, close button behavior) is shared by every client of the same backend — change it in the desktop window and the browser and phone clients connected to the same Croli follow.
• Per-device (disable hardware acceleration, desktop notifications, notification sounds) only applies to this machine / this browser.

On open, the page loads your stored settings. If that fails, a red notice hangs at the top and the affected controls stay disabled — otherwise one failed load would overwrite your stored shell with System default.

Default terminal

The shell you pick here is used in two places: when Croli opens a new terminal tab, and when Croli runs a whole command line on an agent's behalf.

Agents that bring their own shell are not affected. Codex, Claude Code and the like run commands inside their own process, with their own shell, and Croli cannot reach in.

Below the title, a Currently using line shows the executable actually in use right now.

The options in the dropdown:

An option that is not installed on this machine is marked "(not installed)" but can still be picked. The three Windows options do not appear on macOS or Linux.

Picking one of the ready-made options takes effect immediately, with no Save to press; if it cannot be stored, the selection snaps back to the previous one and tells you.

Custom path expands a sub-card below it: a Shell path field — an absolute path, or a name that can be found on PATH — and a Save button next to it. Nothing is written until you press Save. If the path cannot be found on this machine an amber warning appears under the field, but you can still save it: the path may belong to another machine, or you may not have installed it yet.

Colorize command output

One switch, off by default. Turned on, it forces ANSI color out of the commands agents run, so their output renders in color in the transcript instead of as plain text. Takes effect on new sessions; already-running ones are untouched.

It is stored together with the default terminal above, which is why this switch is greyed out until the page has finished loading the settings.

Disable hardware acceleration

Only appears on the Windows and Linux desktop builds. Not on macOS (WKWebView has no such switch), not in a browser, and not in a remote workspace window pointed at a remote server.

If the app shows a black screen or rendering glitches — common with AMD GPUs or some Intel integrated GPUs on Windows, and with the proprietary NVIDIA driver on Linux — you can turn hardware acceleration off. Off by default, meaning hardware acceleration is on by default.

It lives in the desktop build's local preference file and needs a restart to take effect. After a change, a "Saved. Restart the app for the change to take effect." banner appears with a Restart now button; as long as the stored value differs from the one the current process started with, that banner stays, including after you leave this screen and come back.

Close button behavior

Desktop only, and not in a remote workspace window.

Choose what the main window's close button does:

Whether it can go to the tray is up to the system. On Linux this dropdown is always disabled: GNOME 45 onwards no longer provides StatusNotifierWatcher, Croli rules the tray unavailable, and the description becomes "This system has no usable tray, so the close button always exits Croli." On Windows and macOS it depends on whether the tray icon installed.

Desktop notifications

Raise an OS notification when an agent needs you. The master switch is on by default, changes are written immediately, and there is no save button. The setting applies to this device only; another browser or another machine holds its own separate copy.

The block is collapsed every time you open settings, and the master switch sits on the title row: turning it on expands the contents at the same time, and turning it off puts every control away again, leaving just that one line.

Notification permission

Whether a notification can appear at all is the browser's or the system's call. The badge on this card shows where that stands:

The desktop app stays on Managed by the system: it hands the notification to the system notification centre, and the system does not turn around and tell the app whether Croli is allowed. So there is no Allowed / Blocked to read there, and a test send is the only way to find out whether notifications get through.

A test send ignores every switch on this screen: it fires even with the window right in front of you and every event turned off. If it cannot be delivered, the system's own error is shown as-is.

macOS adds a Delivered as row. The monospace badge is the app the system files these notifications under — the switches that apply are that app's own. Normally it is Croli itself. If it turns amber, Croli could not claim its own identifier and the system is posting under another app's identity (usually Terminal); installing Croli into the Applications folder and reopening it restores its own. Windows and Linux have no such row — they post under Croli's own name to begin with.

Notify when, and which events

• Notify when — Always / Window is not focused / Window is not visible (default). The default is the strictest tier: a window spread out on a second monitor counts as visible and will not fire. If notifications never seem to arrive, switch to Window is not focused.
• Hide notification contents — off by default. Turned on, the body becomes a generic line and agent output never reaches the system notification centre — which keeps its payload outside the app, still there after you close the conversation. The title still names the folder, so you can tell which window to go back to.
• Events — six switches, all on by default: Turn Complete, Permission Request, Agent Question, Agent Error, Background task, Work task. An event turned off only stops the notification; the message still lands in the interface. Repeats of the same event within a few seconds collapse into one notification.

Notification sound

Also a collapsible block, collapsed by default, with the master switch on the title row.

Play a short sound when an agent event fires. The setting applies to this device only. The master switch is off by default, and sounds play in the workspace window of this browser or app only.

• Volume — 0–100%, in steps of 5%, default 60%. The Preview next to it plays one sound at the current volume.
• Only when the window is not focused — off by default. Stays silent while you are looking at Croli.
• Events — five rows, each with a tone dropdown and a play button; picking a tone previews it right away.

Available tones: Silent, Chime, Ding, Blip, Pop, Alert, Descending.

Worth knowing

• Both the notification and the sound sections are saved per device; change one in the settings window and the workspace follows immediately, with no need to reopen it.
• The User Message event has a sound only, no desktop notification — no point popping up a window to tell you about a message you sent yourself.
• Collaboration and delegation, the in-conversation extension tools, and the built-in browser all used to be on this screen; each now has a page of its own: Extension Tools, Agents, Browser Use.