Data locations
Where Murage keeps your bots, conversations, memory, files, settings, keys and logs on Mac, Windows and Linux, and what backups and exports include.
Murage keeps your work on your own computer. This page lists where each kind of data lives, and what a backup or an export takes with it.
The data folder
Everything your bots know and do lives in one folder called .murage in your home folder:
- Mac:
~/.murage(for example/Users/you/.murage) - Windows:
%USERPROFILE%\.murage(for exampleC:\Users\you\.murage) - Linux:
~/.murage(for example/home/you/.murage)
The folder starts with a dot, so it's hidden by default. On a Mac, press Command + Shift + . in Finder to show hidden files. On Windows, turn on Hidden items in File Explorer's View menu.
Murage makes the folder readable only by your own user account. The app has no setting to move it. The MURAGE_DATA_DIR environment variable points Murage at a different folder, but it's meant for testing. See Environment variables and flags.
Updating or reinstalling Murage doesn't touch this folder.
What's inside
You don't need to open these files. Change things in the app, not by hand, unless a guide tells you to.
messages.db: the main database. Conversations, tasks, channel history and what your bots remember.memory-index.db: the search index Murage uses to recall memories quickly.config.json: your settings, including the custom MCP servers you add.bots.jsonandgroups.json: your bots, and your teams and channels.routines.json,calendar-calls.jsonandwebhooks.json: routines, scheduled calls and webhooks.workspaces: one folder per bot. This is each bot's own working folder.attachments: files and images you send in chat.artifact-files: files your bots make and share with you.skillsandskill-state: skills you import or teach, and which bots have them switched on.checkpoints: the snapshots taken before each turn.events: the running record of what happened.
Murage also keeps some folders it can download again, such as engine programs and model lists. Those don't need protecting.
A bot's working folder and MEMORY.md
Each bot gets a folder at .murage/workspaces/<bot id>/. Inside it:
MEMORY.md: the bot's notebook. The first 200 lines (up to about 24,000 bytes) ride along on every turn, so the bot keeps it short.memory/: longer notes on one topic each, as<topic>.mdfiles, which the bot reads when it needs them.threads/<task id>/: a separate desk for each new task.
If you point a bot at a project folder somewhere else on your computer, it works there instead, and that folder stays where it is. See Projects and Memory.
Keys and passwords
In the installed app, the keys and tokens you save (engine and provider keys, channel tokens, connected-app logins) aren't kept in plain text in config.json. Murage encrypts them with your operating system's own credential store and keeps them in a credentials.bin file in the app's system folder:
- Mac:
~/Library/Application Support/Murage - Windows:
%APPDATA%\Murage - Linux:
~/.config/Murage
Because the operating system does the encryption, copying these files to another computer doesn't make the keys usable there. Add them again on the new computer.
Two exceptions to know about:
- Environment values you give a custom MCP server are saved in
config.json, which only your user account can read. Use a token scoped to that one server. See MCP. - Webhook secrets aren't stored at all. Murage keeps only a fingerprint it can check a request against. See Webhooks.
Logs
Murage writes what happens at startup and while it runs to server.log:
- Mac:
~/Library/Logs/Murage - Windows:
%APPDATA%\Murage\logs - Linux:
~/.config/Murage/logs
The same folder holds desktop-crashes.log if the app window has crashed. Remove anything private before you share a log. See Startup and ports.
What a backup includes
A backup is an encrypted copy of your data folder's application data. It includes:
- the database, so conversations, tasks, channel history and memories;
- your settings, bots, teams, routines, scheduled calls and webhooks;
- each bot's working folder, including
MEMORY.md; - attachments, shared files, skills and checkpoints.
It leaves out:
- your saved keys, tokens and connected-app logins. After a restore you add them again;
- engine sessions and engine sign-ins, such as Claude account folders;
- things Murage downloads again when needed, such as engine programs, model lists and the memory model;
- the bot's own browser profiles;
- folders outside the data folder, such as a project folder you pointed a bot at.
Channel links are kept in the backup, but you pair Telegram, Slack or Discord again after a restore before they're used. Starting Murage when you sign in isn't switched back on by a restore either.
A bot's Local VM home folder can't be backed up. If a backup stops with "A bot's virtual-machine workspace can't be included in this backup", turn that computer off for the bot, then back up again.
To set backups up, see Backups and export and Backups.
What an export includes
An export is a file for sharing bots and teams, not a backup. It holds a definition of your bots, never their running state. It includes:
- the bots you pick, with their names, roles, look and instructions, and the channels they share;
- the skills you pick;
- their routines;
- the names of the connected apps they expect, so the person importing knows what to connect.
It never includes:
- keys, passwords, tokens or connected accounts;
- conversations, memory or
MEMORY.md; - permission grants and approvals;
- folder paths from your computer;
- which engine each bot runs on;
- whether a routine was switched on. Imported routines arrive switched off.
Murage scans the export for known secret patterns, but that can't catch everything. Check the file before you share it. See Export and import and Share a team with your staff.