Documentation
Everything you need to connect WakaTime-compatible tooling to Chronova
Quick Links
Chronova accepts the same heartbeats and endpoints as WakaTime, making migration seamless.
Quick Install
Linux (GNU libc)
Most Linux distributions including Ubuntu, Debian, Fedora, CentOS
curl -fsSL https://raw.githubusercontent.com/nx-solutions-ug/chronova-cli/main/install-linux.sh | bashLinux (musl libc)
Alpine Linux and other musl-based distributions
CHRONOVA_CLI_MUSL=true curl -fsSL https://raw.githubusercontent.com/nx-solutions-ug/chronova-cli/main/install-linux.sh | bashmacOS
Supports both Intel (x86_64) and Apple Silicon (ARM64) Macs
curl -fsSL https://raw.githubusercontent.com/nx-solutions-ug/chronova-cli/main/install-macos.sh | bashWindows (PowerShell)
Windows 10/11 with PowerShell 5.1 or later
irm https://raw.githubusercontent.com/nx-solutions-ug/chronova-cli/main/install-windows.ps1 | iexAlternative Windows Command
If you encounter execution policy issues, use:
powershell -ExecutionPolicy Bypass -Command "& {irm https://raw.githubusercontent.com/nx-solutions-ug/chronova-cli/main/install-windows.ps1 | iex}"Post-Installation
Configure API Key
Get your API key from chronova.dev/settings and add it to ~/.chronova.cfg:
[settings]api_key = your-api-key-hereapi_url = https://chronova.dev/api/v1Verify Installation
Test your installation:
chronova-cli --versionchronova-cli --todayTroubleshooting
Permission Denied
If you get permission errors:
chmod +x ~/.chronova/chronova-cliCommand Not Found
Ensure ~/.local/bin is in your PATH:
export PATH="$HOME/.local/bin:$PATH"Windows Execution Policy
Run PowerShell as Administrator:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUserManual Download
Download binaries from GitHub releases:
https://github.com/nx-solutions-ug/chronova-cli/releasesMigration Guide
Backup & Install
Creates timestamped backup of ~/.wakatime* files, downloads the correct binary for your platform, and installs to ~/.chronova/
PATH & Symlinks
Creates symlinks in ~/.local/bin/ for chronova-cli and wakatime-cli commands. Also creates ~/.wakatime.cfg symlink for plugin compatibility.
API Key Migration
Extracts your existing WakaTime API key automatically or prompts you to enter a new one from chronova.dev/settings
Editor Integration
VS Code, JetBrains, Vim, and other editor plugins work seamlessly without reconfiguration through compatibility symlinks
Editor Integrations
Install WakaTime plugins in your editor of choice. They will automatically use the Chronova CLI through compatibility symlinks.
Visual Studio Code
ext install WakaTime.vscode-wakatimeOpen the Extensions panel (Ctrl+Shift+X) and search for "WakaTime".
JetBrains IDEs
Settings → Plugins → Marketplace → "WakaTime"Works with IntelliJ IDEA, PyCharm, WebStorm, PhpStorm, and Rider.
Neovim/Vim
Plug 'wakatime/vim-wakatime'Add to your plugin manager (vim-plug example shown above).
Sublime Text
Package Control: Install Package → "WakaTime"Restart Sublime after installation to initialize the plugin.
Frequently Asked Questions
Chronova is an alternative to WakaTime that uses compatible APIs. You maintain full ownership of your time-tracking data while using familiar WakaTime tooling and plugins.
No. Chronova is an independent project. WakaTime® is a registered trademark of WakaTime LLC. All compatibility features are provided solely to help teams migrate.
Yes. You can configure different editors to send data to different endpoints. Ensure each CLI instance uses the correct API key and endpoint configuration.
The Chronova CLI migration tool can automatically transfer your historical coding data, project mappings, and editor integrations from WakaTime.
Chronova supports all core WakaTime features but may not include premium features like team dashboards or advanced analytics available in WakaTime paid plans.
Trademarks
Chronova is not affiliated with, endorsed by, or connected to WakaTime LLC. WakaTime® remains a registered trademark of WakaTime LLC. All compatibility features are provided solely to help teams migrate.