Settings page
Tune Memtrace from the dashboard or with `memtrace settings`, without remembering environment variables. Saved once, applied by every running Memtrace.
Memtrace is tuned through environment variables, and nobody remembers them. The Settings page lists the ones worth changing, in plain words, with a switch, slider or choice for each and a line saying what each end of the slider does. Change something and it takes effect in every running Memtrace, or on its next start where the page says so.
The Settings page#
Open the dashboard and choose the gear in the top bar. Settings are grouped by what they are for (start-up and freshness, CPU, memory, search, git hooks, privacy and so on). The everyday ones are visible; turn on Show advanced for the expert tuning, or search: a search looks inside the advanced settings too and also matches the variable name, so pasting MEMTRACE_EMBED_BATCH_SIZE finds its card.
- Changes are staged. A bar at the bottom shows how many are unsaved, with Save changes (or Ctrl/Cmd+S) and Discard. Nothing changes until you save.
- A slider shows its value in words, marks the default on the track, and says what the left and right ends mean. A slider marked Automatic is chosen by Memtrace from your machine until you touch it.
- More under a setting explains when to change it and what it costs, shows the variable behind it and the value the process holds right now.
- A setting that only matters while another is on (the CPU allowance only matters while the adaptive CPU budget is on) is dimmed and says so.
When a change applies#
Every setting carries one of two badges:
| Badge | Meaning |
|---|---|
| Instant | The code reads the value each time the feature runs. Every running Memtrace (the dashboard daemon, each editor’s memtrace mcp, an index in progress) picks it up within a few seconds. |
| After restart | The value is read once while Memtrace starts, or when a model or service is built. It is saved straight away and used the next time Memtrace starts; a banner at the top of the page lists what is waiting and the command to restart. |
memtrace stop && memtrace start
What wins#
From strongest to weakest:
- A command-line flag for that run (for example
--max-coresover the saved thread limit). - A variable already set in the process environment: your shell profile, a service unit, CI. The page shows it as locked with its value and why, and ignores the slider rather than pretending it works. Unset the variable to manage the setting here.
- The value saved on the Settings page.
- A project
.envfile, then Memtrace’s own default.
From a terminal#
memtrace settings is the same thing without a browser. Both edit the same file, so a change made in either shows up in the other.
memtrace settings list # what differs from the default (--all for everything, --json for tools) memtrace settings get MEMTRACE_FRESHNESS_WAIT_SECS memtrace settings set MEMTRACE_FRESHNESS_WAIT_SECS 25 memtrace settings set MEMTRACE_NO_REPLAY off # a switch: on / off memtrace settings set MEMTRACE_MAX_THREADS auto # back to automatic memtrace settings reset MEMTRACE_MAX_THREADS # one setting back to its default memtrace settings reset # everything memtrace settings effective --json # the environment a fresh start would see
The settings file#
Choices are saved to ~/.memtrace/settings.json as plain variable names and values. Editing it by hand works, but only the settings Memtrace manages are read from it, and a value its control cannot represent is ignored, so a typo can never push garbage into the environment. Saving a value equal to the default simply removes it from the file.
The settings page only answers from the machine Memtrace runs on, and refuses requests from other websites. If you expose the dashboard on a network with MEMTRACE_UI_HOST, settings stay read-only from there.
What is not a setting#
The page deliberately has no secrets, tokens or licence keys, no path to a binary or library, no URL or endpoint, no ports, and nothing that deletes data. A settings file must never be a way to change what runs or who Memtrace talks to; those stay environment variables and flags. The environment variable reference still lists every variable.