Skip to content
vic

cerebroapp/cerebro

šŸ”µ Cerebro is an open-source launcher to improve your productivity and efficiency

cerebroapp/cerebro.json
{
"createdAt": "2016-07-03T14:42:01Z",
"defaultBranch": "master",
"description": "šŸ”µ Cerebro is an open-source launcher to improve your productivity and efficiency",
"fullName": "cerebroapp/cerebro",
"homepage": "https://www.cerebroapp.com/",
"language": "JavaScript",
"name": "cerebro",
"pushedAt": "2025-11-15T10:37:06Z",
"stargazersCount": 8511,
"topics": [
"cerebro",
"electron",
"launcher",
"search"
],
"updatedAt": "2025-11-26T16:57:28Z",
"url": "https://github.com/cerebroapp/cerebro"
}

Cerebro is an open-source launcher to improve your productivity and efficiency

You can download the latest version on the releases page.

After the installation, use the default shortcut, ctrl+space, to show the app window. You can customize this shortcut by clicking on the icon in the menu bar, and then selecting ā€œPreferencesā€¦ā€.

Cerebro

  • Search the web with your favourite search engine
  • Search & launch application, i.e. spotify
  • Navigate the file system with file previews (i.e. ~/Dropbox/passport.pdf)
  • Calculator
  • Smart converter. 15$, 150 Ń€ŃƒŠ±Š»ŠµŠ¹ в евро, 100 eur in gbp;

You can manage and install more plugins by typing plugins <plugin-name> in the Cerebro search bar.

Discover plugins and more at Cerebro’s Awesome List.

If you’re interested in creating your own plugin, check the plugins documentation.

Cerebro provides several shortcuts to improve your productivity:

  • ctrl+c: copy the result from a plugin to the clipboard, if the plugin does not provida a result, the term you introduced will be copied
  • ctrl+1...9: select directly a result from the list
  • ctrl+[hjkl]: navigate through the results using vim-like keys (Also ctrl+o to select the result)

Use the shortcut ctrl+space to open the app window, and type Cerebro Settings. There you will be able to change the Theme.

Currently Light and Dark Themes are supported out of the box

change-cerebro-theme

You can find the config file in the following path depending on your OS:

Windows: %APPDATA%/Cerebro/config.json

Linux: $XDG_CONFIG_HOME/Cerebro/config.json or ~/.config/Cerebro/config.json

macOS: ~/Library/Application Support/Cerebro/config.json

āš ļø A bad configuration file can break Cerebro. If you’re not sure what you’re doing, don’t edit the config file directly.

If you’d like to install a version of Cerebro, but the executable hasn’t been released, you can follow these instructions to build it from source:

  1. Clone the repository

  2. Install dependencies with yarn:

    Terminal window
    yarn --force
  3. Build the package:

    Terminal window
    yarn package

Note: in CI we use yarn build as there is an action to package and publish the executables

If you’re a linux user, you might need to grant execution permissions to the executable. To do so, open the terminal and run the following command:

Terminal window
sudo chmod +x <path to the executable>

Then, you can install the executable by running the following command:

  • If you’re using the AppImage executable:

    Terminal window
    ./<path to the executable>
  • If you’re using the deb executable:

    Terminal window
    dpkg -i <path to the executable>

On some computers you might need run these commands with elevated privileges (sudo). sudo ./<path to the executable> or sudo dpkg -i <path to the executable>

CerebroApp is an open source project and we welcome contributions from the community. In this document you will find information about how Cerebro works and how to contribute to the project.

āš ļø NOTE: This document is for Cerebro developers. If you are looking for how to develop a plugin please check plugin developers documentation.

Cerebro is based on Electron and React.

A basic Electron app is composed of a main process and a renderer process. The main process is responsible for the app lifecycle, the renderer process is responsible for the UI.

In our case we use:

  • [app/main.development.js]!(/app/main.development.js) as the main process
  • [app/main/main.js]!(/app/main/main.js) as the main renderer process
  • [app/background/background.js]!(/app/background/background.js) as a secondary renderer process

All this files are bundled and transpiled with Webpack and Babel.

The build process is managed by electron-builder.

This two-renderer process architecture is used to keep the main renderer process (Cerebro) responsive and to avoid blocking the UI when executing long tasks.

When we need to execute a long task we send a message to the background process, which executes the task asynchronously and sends a message back to the main renderer when the task is completed.

This is the way we implement the plugins system. Their initializeAsync method is executed in the background process.

First, clone the repo via git:

Terminal window
git clone https://github.com/cerebroapp/cerebro.git cerebro

Open the project

Terminal window
cd cerebro

And then install dependencies:

Terminal window
yarn
Terminal window
yarn run dev

Note: requires a node version >=16.x

  1. AssertionError: Current node version is not supported for development on npm postinstall. After yarn postinstall script checks node version. If you see this error you have to check node and npm version in package.json devEngines section and install proper ones.

  2. Uncaught Error: Module version mismatch. Exepcted 50, got ... This error means that node modules with native extensions build with wrong node version (your local node version != node version, included to electron). To fix this issue run yarn --force

The project is using conventional commit specification to keep track of changes. This helps us with the realeases and enforces a consistent style. You can commit as usually following this style or use the following commands that will help you to commit with the right style:

  • yarn cz
  • yarn commit

CerebroApp is using GH actions to build the app and publish it to a release. To publish a new release follow the steps below:

  1. Update the version on both package.json and app/package.json files.
  2. Create a release with from GH and publish it. 🚧 The release tag MUST contain the v prefix (āŒ 0.1.2 → āœ…v0.1.2).
  3. Complete the name with a name and a description of the release.
  4. The GH action is triggered and the release is updated when executables are built.

MIT Ā© Cerebro App