This is a WIP! This is a fork of the WakaTime for Visual Studio Code extension. This fork aims to fulfill two goals:
- Add multi-server support. (Send data to multiple wakatime servers)
- Remove bloat/tech debt from the original WakaTime extension (remove the CLI dependency, remove dead code, etc...)
I do plan to create a completely custom plugin implementing the API spec when I have more time.
- Download the .vsix file from the GitHub Release
- Go to
Extensions > ...
(See below image) - Click on Install from VSIX
- Select the .vsix file you downloaded
- Open the Command Pallette
- Go to
Preferences: Open User Settings (JSON)
- Add (and configure) the following sinppet
{
"wakatime.apiConfig": [
{
"apiUrl": "https://wakatime.example.com/api",
"apiKey": "api-key"
},
{
"apiUrl": "https://wakapi.dev/api",
"apiKey": "another-api-key"
}
],
}
WakaTime is an open source VS Code plugin for metrics, insights, and time tracking automatically generated from your programming activity.
- Use VSCode and your coding activity will be displayed on your WakaTime dashboard
Visit https://wakatime.com to see your coding activity.
VS Code specific settings are available from ⌘ + Shift + P
, then typing wakatime
.
For example, to hide today's coding activity in your status bar:
Press ⌘ + Shift + P
then set WakaTime: Status Bar Coding Activity
to false
.
Extension settings are stored in the INI file at $HOME/.wakatime.cfg
.
More information can be found from wakatime-cli.
If using an online IDE like gitpods, add your api key to global ENV key WAKATIME_API_KEY
.
Notes:
$HOME
defaults to$HOME
- To disable the extension at startup add
disabled=true
to your config, this operation can also be performed by pressing⌘ + Shift + P
and selectingWakaTime: Disable
.
First, turn on debug mode:
- Press
F1
or⌘ + Shift + P
- Type
> WakaTime: Debug
, and pressEnter
. - Select
true
, then pressEnter
.
Next, open your Developer Console to view logs and errors:
Help → Toggle Developer Tools
Errors outside the scope of vscode-wakatime go to $HOME/.wakatime/wakatime.log
from wakatime-cli.
If your error message contains "won't send heartbeat due to backoff" then delete your ~/.wakatime/wakatime-internal.cfg
file to trigger an API connection so we can see the real error message.
The How to Debug Plugins guide shows how to check when coding activity was last received from your editor using the Plugins Status Page.
Microsoft Windows Only: Using WakaTime behind a corporate proxy? Try enabling your Windows Root Certs inside VS Code with the win-ca extension:
Press Ctrl + Shift + X
, search for win-ca
, press Install
.
For more general troubleshooting info, see the wakatime-cli Troubleshooting Section.
If you're connected to a remote host using the ssh extension you might want to force WakaTime to run locally instead on the server. This configuration is needed when the server you connect is shared among other people. Please follow this guide.
-
Click the Extensions sidebar item in VS Code.
-
Type
wakatime
and hit enter. -
Click the settings icon next to WakaTime, then click Uninstall.
-
Delete the
~/.wakatime*
files in your home directory, unless you’re still using WakaTime with another IDE.
Pull requests, bug reports, and feature requests are welcome! Please search existing issues before creating a new one.
To run from source:
git clone [email protected]:wakatime/vscode-wakatime.git
cd vscode-wakatime
npm install
npm run watch
- Install the extension from the marketplace
- Then symlink
~/.vscode/extensions/wakatime.vscode-wakatime-*/dist/extension.js
to./dist/extension.js
Or to run the web version from source:
git clone [email protected]:wakatime/vscode-wakatime.git
cd vscode-wakatime
npm install
npm run compile
npm run open-in-browser
- Go to localhost:3000 in your web browser
Many thanks to all contributors!
Made with ❤️ by the WakaTime Team.