Server-Wide Configuration

Read and write non-secret server-wide settings — the working directory, JWT issuer, log level, and more — with cremind setup server-config.

Some Cremind settings apply to the whole server rather than a single profile: the default working directory, the JWT issuer, the log level, and similar. These are the same key/value pairs the setup payload carries under server_config, and you read or write them after first run with cremind setup server-config.

These subcommands require admin auth — CREMIND_TOKEN must belong to an admin-capable profile.

In the web UI

Sidebar -> Settings -> Admin -> Server config

That page shows the non-secret server settings as a key/value editor, and exposes a "Reset setup" action that mirrors cremind setup reconfigure.

Reading settings

# Every key as a table
cremind setup server-config get

user_working_dir   /home/li/work
jwt_issuer         cremind
log_level          info

Pass a single key to print just its value — handy in scripts:

cremind setup server-config get user_working_dir

/home/li/work

With --json, the output is the full JSON object (or {<key>: <value>} for the single-key form).

Writing settings

set takes one or more KEY=VALUE pairs. Each pair is split on the first =, so the value side may itself contain = characters.

cremind setup server-config set log_level=debug user_working_dir=/srv/cremind

All updates are sent in a single PATCH: if any one pair is rejected, none are applied. The command is silent on success.

# Move the working directory and confirm it
cremind setup server-config set user_working_dir=/mnt/cremind
cremind setup server-config get user_working_dir

/mnt/cremind

Common keys

These are the server-wide keys you will most often touch. Run cremind setup server-config get to see the full set live on your installation.

Key	Holds
`user_working_dir`	The user-facing default working directory the agent operates in.
`jwt_issuer`	The issuer string stamped into minted JWTs.
`log_level`	Server log verbosity (e.g. `info`, `debug`).

SQLite overrides TOML

Server-wide settings written here are persisted in SQLite, and those stored values override the corresponding entries in the TOML settings.toml file. TOML supplies the baseline a fresh server boots with; once you write a key through server-config set (or the Admin UI), the database value takes precedence.

If a TOML edit 'won't take'

A value you edited in settings.toml that does not seem to apply is almost always being shadowed by a database override. Update it through cremind setup server-config set instead, or remove the override so the TOML baseline applies again.

Resetting the server

To make the Setup Wizard run again — for example after rotating the JWT secret — an admin resets the completion flag:

cremind setup reconfigure

The next UI load shows the wizard, and cremind setup status reports setup_complete=false until a new setup complete call lands. See Headless bootstrap for the full re-run and recovery flows.

Troubleshooting

401 Unauthorized — server-config requires admin auth. Confirm CREMIND_TOKEN belongs to an admin profile with cremind me.
A set was rejected and nothing changed — updates are all-or-nothing in one PATCH. Fix the offending KEY=VALUE pair and resend the whole set.