Your data
Modular keeps its data on your machine. Your project folders stay where they are; Modular only reads and works in them.
Where it lives#
| What | Where |
|---|---|
The app's data root: database (modular.db), settings, agents, sessions, plugins, logs, worktrees | macOS ~/Library/Application Support/@modular/desktop/data; Windows %APPDATA%\@modular\desktop\data; Linux ~/.config/@modular/desktop/data |
| Home folder: agent skills, Chronicle models, runtime files | ~/.modular-ade |
| A project's own Modular files (skills, worktree setup) | <project>/.modular/ |
| A board kept in its project | <project>/.kanbo/board.db |
Builds from before the rename to Modular kept their data in @cradle/desktop and
~/.cradle; Modular moves it to the new places on its first start.
Moving the data#
Settings → Help → Support → Modular data directory → Change location copies the data to a new folder, checks it, and restarts. The old copy stays until the move has succeeded.
Backups#
Settings → Data → Backup exports everything Modular owns into one
.modular-backup file, and restores it on another computer. The file holds the
database, settings, agents, sessions, plugins and locally stored credentials: keep it
private. Your project folders, and what other tools keep outside Modular, are not in
it. Restoring keeps the current data as a rollback copy, and goes back to it if Modular
does not start.
Settings you can set from outside#
| Variable | Does |
|---|---|
MODULAR_DESKTOP_USER_DATA_DIR | Run the desktop app on another data folder |
MODULAR_DATA_DIR | The data root of a server you run yourself |
MODULAR_HOST, MODULAR_PORT | Where that server listens (default 127.0.0.1:21423) |
MODULAR_SERVER_URL | Which server the modular CLI talks to |