Skip to content

Troubleshooting

Solutions to common issues you might encounter with jolt.

The jolt binary isn’t in your PATH.

Homebrew install:

Terminal window
# Verify installation
brew list jolt
# If installed, try:
eval "$(/opt/homebrew/bin/brew shellenv)"

Cargo install:

Terminal window
# Add cargo bin to PATH
export PATH="$HOME/.cargo/bin:$PATH"
# Or reinstall
cargo install jolt-tui --force

Source install:

Terminal window
# Copy to PATH
sudo cp ./target/release/jolt /usr/local/bin/

Missing Xcode tools:

Terminal window
xcode-select --install

Rust not installed:

Terminal window
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

Outdated Rust:

Terminal window
rustup update
  1. Resize terminal — Often fixes rendering issues

  2. Force redraw — Press Ctrl+L

  3. Check TERM variable:

    Terminal window
    echo $TERM
    # Should be xterm-256color or similar
  4. Set correct TERM:

    Terminal window
    export TERM=xterm-256color
    jolt
  1. Verify 256 color support:

    Terminal window
    # Should show colored gradient
    for i in {0..255}; do printf "\e[48;5;${i}m \e[0m"; done; echo
  2. Check theme:

    Terminal window
    jolt --theme default
  3. Try different terminal:

    • iTerm2, Alacritty, and Kitty have best color support
    • Default Terminal.app may have issues with some themes

jolt needs a minimum terminal size:

  • Width: 80 columns
  • Height: 24 rows

Resize your terminal or reduce font size.

Power metrics require Apple Silicon:

  • M1, M2, M3, M4 series chips
  • Intel Macs cannot report power consumption

Verify your chip:

Terminal window
sysctl -n machdep.cpu.brand_string
  1. Check macOS battery:

    Terminal window
    pmset -g batt
  2. Compare with ioreg:

    Terminal window
    ioreg -r -c AppleSmartBattery | grep -E "Cycle|Capacity|Health"
  3. Report bug if mismatched — jolt should match these sources

  1. Check permissions:

    • System Settings → Privacy & Security → Full Disk Access
    • Add your terminal app
  2. Run debug:

    Terminal window
    jolt debug
  3. Check for errors:

    Terminal window
    jolt 2>&1 | grep -i error
  1. Check if already running:

    Terminal window
    jolt daemon status
    pgrep -f "jolt daemon"
  2. Check logs:

    Terminal window
    jolt logs
  3. Try foreground mode:

    Terminal window
    jolt daemon start --foreground
  4. Check socket:

    macOS:

    Terminal window
    ls -la ~/Library/Caches/jolt/daemon.sock

    Linux:

    Terminal window
    ls -la ~/.local/share/jolt/daemon.sock
  1. Verify daemon is running:

    Terminal window
    jolt daemon status
  2. Check socket permissions:

    macOS:

    Terminal window
    ls -la ~/Library/Caches/jolt/daemon.sock

    Linux:

    Terminal window
    ls -la ~/.local/share/jolt/daemon.sock
  3. Restart daemon:

    Terminal window
    jolt daemon stop
    jolt daemon start

Increase sample interval in your config file:

macOS: ~/Library/Application Support/jolt/config.toml Linux: ~/.config/jolt/config.toml

[daemon]
sample_interval = 120 # Every 2 minutes

Then restart:

Terminal window
jolt daemon stop && jolt daemon start

jolt creates it on first run. If missing:

Terminal window
# Check location
jolt config --path
# Create default config
jolt config --reset
  1. Verify syntax:

    macOS:

    Terminal window
    cat ~/Library/Application\ Support/jolt/config.toml

    Linux:

    Terminal window
    cat ~/.config/jolt/config.toml
  2. Check for typos — TOML is case-sensitive

  3. Restart jolt — Some changes require restart

  4. Check for overrides:

    Terminal window
    # Environment variables override config
    echo $JOLT_THEME
Terminal window
jolt config --reset

Or manually delete the config file (see jolt config --path for location).

  1. Reduce refresh rate:

    Terminal window
    jolt --refresh-ms 2000
  2. Enable low power mode:

    Terminal window
    jolt --low-power
  3. Close other heavy apps — jolt shows you what’s using resources!

  1. Check refresh rate:

    refresh_ms = 1000 # Don't go below 500
  2. Disable process tracking:

    [panels]
    processes = false
  3. Report bug — jolt should use minimal CPU

Terminal window
jolt debug > debug.txt
Terminal window
jolt --version

Include in bug reports:

  • jolt version
  • macOS version
  • Chip type (Intel/M1/M2/etc)
  • Terminal app
  • Output of jolt debug
  • Steps to reproduce

Report at: https://github.com/jordond/jolt/issues