CremindEnvironment Variables
Reference for the environment variables Cremind reads — system and working directories, UI and server settings, ports, and the CLI token.
Cremind reads a small set of environment variables to locate its files, point the CLI at the right server, and configure the UI listener. The table below lists the variables known today; this page is being expanded and cross-checked against the source before it is treated as exhaustive.
| Variable | Purpose |
|---|---|
CREMIND_SYSTEM_DIR | Cremind's internal system directory (default ~/.cremind). |
CREMIND_INSTALL_DIR | Where the Cremind install lives. |
CREMIND_WORKING_DIR | Overrides the base working directory (used for side-by-side staging installs). |
CREMIND_UI_PORT | Port the SPA/UI listener binds to. Set to 0 to disable the listener (e.g. when an external nginx serves the SPA). |
CREMIND_UI_DIR | Path to the built SPA directory to serve. |
CREMIND_SERVER | URL the cremind CLI talks to (default http://localhost:1112). |
CREMIND_TOKEN | The admin/profile JWT the CLI authenticates with. |
Default ports
| Port | Service |
|---|---|
1112 | API / backend |
1515 | UI (SPA) |
6080 | VNC (Docker-mode desktop, at /vnc.html) |
Documentation in progress
This page is still being written and cross-checked against the source.
The variables above are confirmed, but the full set Cremind reads — and
the precise default of each — is being verified. In the meantime, see
the install reference and source on GitHub:
cremind-ai/cremind. For the
env vars injected into agent-spawned shells specifically, see the
cremind system-vars CLI reference. To set server-wide,
non-secret configuration instead, use
Server-wide configuration.
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.
Using Cremind
The four ways to reach your Cremind agent — the web UI, the desktop app, the cremind CLI, and chat channels — and when to use each.