Settings
Open Settings to change operational preferences. Groups separate mission behaviour, resource limits, permissions, fallback policy and other enabled features. Each registry setting shows where its effective value comes from.
Environment → configuration file → saved UI value → default is the precedence order. If an environment or file value controls a setting, changing the saved value does not override it. See Configuration.
Memory presets
In Settings → Resources, Timon shows detected RAM and the automatic RAM class. Choose 8, 16, 32 or 64 GB to save three memory limits together:
| RAM class | Per mission | All missions, day | All missions, night |
|---|---|---|---|
| 8 GB | 2 GB | 3 GB | 4 GB |
| 16 GB | 4 GB | 6 GB | 8 GB |
| 32 GB | 8 GB | 10 GB | 16 GB |
| 64 GB | 12 GB | 16 GB | 24 GB |
Without an explicit setting, each limit uses the highest class for which detected usable RAM reaches at least 90% of the nominal capacity. This allows for RAM reserved by the kernel and firmware: 7.6 GB uses 8 GB, 15.4 GB uses 16 GB, 31 GB uses 32 GB, and 62.5 GB uses 64 GB. The 64 GB class starts at 57.6 GB; 57 GB still uses 32 GB. Below 8 GB the minimum class remains 8 GB; 12 GB uses 8 GB and 28 GB uses 16 GB. Detection uses GB of 1024³ bytes. Existing saved limits are kept. CPU limits are unchanged.
Preset values remain editable individually. Environment and configuration-file values keep priority over saved presets. Reset a saved field to return to its automatic default, unless a higher-priority value still controls it.
The resource guard applies changes on its next tick (normally within 30 seconds) without restarting Timon. Lowering a ceiling can stop a process already over that limit. Enforcement uses the host's available confinement support; detecting RAM does not add systemd confinement to Windows or macOS.
Backend and fallback choices
Settings → LLM backends lists built-in providers, providers installed by plugins, and providers you added yourself. Only a superadmin can change them. Drag a row's handle to set the order in model selectors. Keyboard users can press Space on the handle, move with the arrow keys, then press Space again.
Turning a backend off hides it from selectors and refuses new launches that explicitly name it. Timon shows the agents, routines and pending tasks that still reference it before confirmation; those choices are kept, without a silent fallback. The last active backend cannot be disabled. If the usual default is disabled, launches with no explicit backend use an active one. Existing running missions are not stopped by this setting.
Choose Edit to rename a backend, choose its picture, add an exact model ID, hide or show models, change their order, or select the default model. For built-in and plugin backends, connection details remain under their provider's control. An exact model ID is sent unchanged; a display label does not create an alias. Newly added models appear first and carry a New badge for seven days. Renaming one does not restart that period.
Use the live backend catalogue (timon backends) rather than copying model IDs from an old guide. Providers can appear or disappear as tools, credentials or plugins change. Select the backend and its model together. To add a provider of your own, see Add a provider.
The LLM fallback group controls global fallback behaviour. A series can override it by scope, and a task can carry an even more specific override. Unknown quota reset times are displayed as unknown; the cooldown is a fallback estimate, not a provider guarantee.
Appearance and plugin settings
Select an installed theme from Appearance. Installed themes that are not selected remain in the gallery without overriding the current palette.
Plugins can add fields to an existing group or provide their own category. A manifest-only settings declaration generates a form automatically. Secret fields display whether a value is configured; they do not return the stored secret to the browser.
Layout preferences
Use layout editing controls to move, resize or remove widgets. A removed card remains available in the palette. Host configuration and disabled modules can hide surfaces independently of your personal placement preferences.
Remote access
The remote-access panel and WebUI settings show a Tailscale Serve command when Timon manages a known local web listener. The command uses that listener's configured port, regardless of the browser address.
For external hosting, including Docker behind a reverse proxy, the sharing command is withheld because the host-side target is unknown. Verify which local address serves Timon on the host before configuring Tailscale Serve. A port inside a container is not necessarily published on the host. If you switch to Timon's managed web server, reopen the panel to read its current configuration and update your existing Tailscale forwarding rule accordingly.