Platform support¶
kbolt supports macOS and Linux for the full local workflow. Windows can run the CLI through Cargo, but managed background services are not available on Windows.
At a glance¶
| Capability | macOS | Linux | Windows |
|---|---|---|---|
| Homebrew install | yes | yes, x86_64 | no |
| GitHub release binary | x86_64, aarch64 | x86_64 | no |
| Cargo install | yes | yes, including aarch64 when native dependencies build | yes |
kbolt setup local |
yes, with llama-server |
yes, with llama-server |
requires llama-server |
kbolt watch enable |
yes, via user launchd |
yes, via user systemd |
no managed service |
kbolt watch --foreground |
yes | yes | terminal process |
kbolt schedule |
yes, via user launchd |
yes, via user systemd |
no managed scheduler |
macOS¶
Homebrew is the shortest path:
The release workflow also builds x86_64 and aarch64 macOS archives.
Managed watcher and schedule commands install user-level launchd entries. They do not require sudo.
Linux¶
Homebrew is supported on Linux x86_64 systems that use Homebrew:
The release workflow also builds a Linux x86_64 archive.
Managed watcher and schedule commands install user-level systemd units. They do not require sudo.
For Linux aarch64, use Cargo:
Prebuilt release archives are available for Linux x86_64. Linux aarch64 users should install with Cargo.
Windows¶
Windows users should install with Cargo:
Managed watcher and schedule commands are not supported on Windows. Use kbolt update for refreshes, or run kbolt watch --foreground in a terminal.
Next steps¶
- Install kbolt with Install.
- Keep files fresh with Keep indexes fresh.
- Check paths in Data locations.