Skip to content

FAQ

Common questions and answers about jolt.

Yes! jolt supports Linux with the same features as macOS:

  • ✅ Battery status (percentage, state, health, cycles)
  • ✅ Power metrics (watts) via RAPL
  • ✅ Process list with CPU usage
  • ✅ All TUI features

Note: Power metrics on Linux require permissions. See installation guide.

Yes, but with limited functionality. Intel Macs will show:

  • ✅ Battery status (percentage, state, health, cycles)
  • ✅ Process list with CPU usage
  • ❌ Power metrics (watts) — requires Apple Silicon

For full power metrics on Intel hardware, use Linux with RAPL support.

Yes! jolt is fully terminal-based and works great over SSH:

Terminal window
ssh myserver
jolt

Make sure your terminal supports 256 colors for the best experience.

Yes, jolt works in terminal multiplexers. If you experience display issues:

Terminal window
# In tmux, ensure 256 color support
set -g default-terminal "screen-256color"

Very little. At the default 1-second refresh rate:

  • ~0.1-0.2% CPU usage
  • ~15-20 MB memory

Use --low-power mode to reduce even further.

Yes! Use pipe mode for JSON output:

Terminal window
jolt pipe --samples 1 | jq '.battery.percentage'

Why is “Time Remaining” sometimes inaccurate?

Section titled “Why is “Time Remaining” sometimes inaccurate?”

The time remaining is calculated based on current power consumption. It changes as your workload changes. A sudden increase in CPU usage will immediately affect the estimate.

What’s the difference between battery health and charge?

Section titled “What’s the difference between battery health and charge?”
  • Charge — Current battery level (0-100%)
  • Health — Maximum capacity compared to original design (degrades over time)

A battery at 100% charge but 80% health can only hold 80% of its original capacity.

Power metrics require platform-specific hardware support:

macOS:

  1. Apple Silicon Mac (M1/M2/M3/M4)
  2. macOS 11.0 or later

Intel Macs cannot report per-component power consumption.

Linux:

  1. Intel or AMD CPU with RAPL support (kernel 3.13+)
  2. Proper permissions configured

See the installation guide for Linux setup.

Your Mac is connected to power but not charging. This happens when:

  • Battery is optimizing charge (staying at 80%)
  • Charger wattage is too low
  • Battery temperature is too high/low

Very accurate. jolt reads directly from Apple’s IOReport framework, the same source used by Activity Monitor and system power management.

Why do some processes show high energy impact with low CPU?

Section titled “Why do some processes show high energy impact with low CPU?”

Energy impact considers more than CPU:

  • Disk I/O
  • Network activity
  • GPU usage
  • Wake frequency (waking from idle)

A process can have low CPU but high disk I/O, resulting in elevated energy impact.

Yes! Select a process and press K. You’ll be asked to confirm before the process is killed.

jolt groups parent and child processes. Press Enter to expand a group and see individual children.

  • Built-in themes: Bundled with jolt
  • Custom themes:
    • macOS: ~/Library/Application Support/jolt/themes/
    • Linux: ~/.config/jolt/themes/
  • Imported themes: Same as custom themes
Terminal window
# From CLI
jolt theme import "Dracula"
# Or from TUI
# Press T, then i, search and select
  1. Check terminal color support:

    Terminal window
    echo $TERM
    # Should show xterm-256color or similar
  2. Validate theme:

    Terminal window
    jolt theme check --theme my-theme
  3. Try a built-in theme to compare:

    Terminal window
    jolt --theme default

The daemon collects data continuously, even when you’re not running jolt. This enables:

  • Historical analysis
  • Trend tracking
  • Export and reporting

No. The daemon:

  • Uses <0.1% CPU
  • Uses ~10 MB memory
  • Writes to disk once per minute (by default)
Terminal window
jolt daemon status

Or in the TUI, press d to see daemon info.

Yes! The daemon is optional. The TUI works independently with real-time data.

Some features require permissions:

  1. Full Disk Access — For some process information
  2. Automation — For system preference detection

Grant permissions in System Settings → Privacy & Security.

Try:

  1. Resize your terminal window
  2. Press Ctrl+L to redraw
  3. Check terminal color support
  4. Try a different terminal emulator
  1. Increase refresh interval:

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

    Terminal window
    jolt --low-power
  3. Check for resource-heavy processes in the list

  1. Check config file location:

    Terminal window
    jolt config --path
  2. Validate config syntax:

    macOS:

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

    Linux:

    Terminal window
    cat ~/.config/jolt/config.toml
  3. Reset to defaults:

    Terminal window
    jolt config --reset