Extension Icon

FanBar

Switch FanBar cooling presets, set a fixed fan speed, and watch fans and temperatures on your Mac.
Overview

FanBar for Raycast

Control FanBar from Raycast: switch cooling presets (custom ones included), set a fixed fan speed, hand the fans back to macOS, and keep the CPU temperature in the menu bar.

CommandWhat it does
Switch PresetLists built-in and custom presets and marks the selected one. ↵ runs the preset's curve until the Restore automatic control timer in FanBar Settings; ⌘↵ keeps it until changed (--hold).
Fan StatusMode, each fan's speed and range, CPU/GPU/SSD temperatures, and when macOS control comes back.
Fixed RPMHolds every fan at one speed, checked against the range all fans accept. Tick Hold until changed to skip the restore timer.
AutomaticHands the fans back to macOS and shows the result as a HUD.
FanBar Menu BarCPU temperature in the menu bar, refreshed every minute, with fans, temperatures, preset switching (⌥ to hold) and Automatic in its menu.

Requirements

The extension drives the fanbar command-line tool that ships inside FanBar.app 0.7.0 and later. Install it on PATH from FanBar Settings › General › Command Line & Automation › Command-line tool › Install…, or by hand:

sudo mkdir -p /usr/local/bin
sudo ln -sf /Applications/FanBar.app/Contents/Helpers/fanbar /usr/local/bin/fanbar

Raycast does not load your shell profile, so the extension looks for the tool itself, in this order:

  1. the fanbar Path preference, if set;
  2. /usr/local/bin/fanbar (the Settings link);
  3. /opt/homebrew/bin/fanbar (Homebrew on Apple Silicon);
  4. /Applications/FanBar.app/Contents/Helpers/fanbar.

When none exists, every command says so and offers the install command.

Behaviour

  • Exit codes become toasts: 1 "FanBar refused the command" with the app's message, 2 "fanbar did not understand the command", 3 "FanBar could not be reached".
  • Presets are switched by their id (builtin:2, custom:<uuid>), so a custom preset that shares a name with a built-in still switches the right one.
  • Like the CLI, the commands you run start FanBar when it is not running. The menu bar's background refresh passes --no-launch, so it never reopens a FanBar you quit; it shows "FanBar is not running" instead. Clicking a preset in its menu is an explicit request and may start FanBar.