Where Does Cerebro Store Config and Plugins?
Cerebro keeps its config.json plus a plugins folder in the standard per-OS app data location on Windows, Mac and Linux.
Last updated
Cerebro follows the Electron userData convention without deviation. Each OS gets its own standard folder holding config.json with a plugins directory beside it. Learn one platform and the others map directly.
Plugins are plain npm packages inside that plugins folder, which makes manual install and removal trivial. One caution belongs here: the project itself is stale upstream. It still runs, but check your OS compatibility first and keep config.json backed up.
Where Cerebro stores this, by platform
%APPDATA%\Cerebro\config.json
Core options file with the plugins sibling holding node_modules per plugin. Standard Electron userData layout. Quit Cerebro before hand edits.
~/Library/Application Support/Cerebro/config.json
Same config plus plugins layout as Windows. Reach it through Finder Go to Folder since Library stays hidden. Project is archived upstream, so confirm the build runs before customizing.
~/.config/Cerebro/config.json
Same layout under XDG config home, falling back to ~/.config when the variable is unset. Manual plugin installs run from the plugins folder beside this file.
Frequently asked questions
How do I edit Cerebro settings by hand?
Open config.json in the paths below and edit with Cerebro quit, then relaunch. The file holds the core options while each plugin keeps its own folder under plugins node_modules. Keep a copy of config.json before major edits since there is no settings UI for everything.
How do I install Cerebro plugins manually?
Change to the plugins folder beside config.json and install the npm package there with your package manager. Restart Cerebro and the plugin registers. Removing the package folder uninstalls it cleanly.
Is Cerebro still maintained?
Treat it as frozen. The project is stale and archived upstream, so verify the release still runs on your OS before investing in plugins. Export config.json somewhere safe in case a future OS update strands the install.
Notice an outdated path? Let us know.