Skip to main content
Version: v2 (current)

Install on Windows

Install the PanDev Metrics CLI plugin on Windows in about 3 minutes. After this guide your terminal activity (base command + timestamp) shows up in PanDev Metrics dashboards.

Before you begin​

  • Windows 10 or 11 with PowerShell (5.1 or newer, preinstalled)
  • A PanDev Metrics account
  • Your API token — copy it from the PanDev Metrics web app (profile / API settings). The token already carries your workspace and server, so there is nothing else to configure.

Step 1 — Install the plugin​

Open PowerShell as Administrator (right-click PowerShell → Run as administrator) and run:

iwr -useb https://raw.githubusercontent.com/pandev-metriks/homebrew-pandev-cli/main/install.ps1 | iex
note

The install script must run from an elevated (Administrator) PowerShell — it registers the background daemon at the system level.

The script downloads the CLI binary, puts it on your PATH, and registers the background daemon so it starts with your session.

:::tip If the script is blocked PowerShell may block remote scripts depending on your execution policy. Allow it for the current session and run the command again:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned

This affects only the current PowerShell window — it does not change your machine-wide policy. :::

Step 2 — Authenticate​

Sign in with your API token:

pandev login -t <YOUR_TOKEN_HERE>

Replace <YOUR_TOKEN_HERE> with the token you copied from the web app. The token is stored locally so the daemon reconnects automatically after restarts.

Step 3 — Verify​

Confirm that the daemon is running and authenticated:

pandev status

Check that heartbeats are accumulating:

pandev time

You can also open Settings → Plugin → CLI plugin in the PanDev Metrics UI — your machine should appear with a recent heartbeat timestamp.

Useful commands​

pandev --help                 # List every command the plugin exposes
pandev status                 # Daemon health and auth state
pandev time                   # CLI activity captured today
pandev login -t <TOKEN>       # Re-authenticate with a new token

Update​

Re-run the install script from an Administrator PowerShell to pull the latest version:

iwr -useb https://raw.githubusercontent.com/pandev-metriks/homebrew-pandev-cli/main/install.ps1 | iex

Uninstall​

pandev-cli-plugin --uninstall

This stops and removes the background daemon and deletes the locally stored token.

Troubleshooting​

iwr ... | iex fails with a script execution error

Your PowerShell execution policy is blocking remote scripts. Allow them for the current session and re-run the install command:

Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned
pandev: command not found after installation

The installer adds the CLI to your PATH, but the current PowerShell window started before that change. Close and reopen PowerShell, then run pandev status again.

pandev status says "not authenticated"

Re-run pandev login -t <YOUR_TOKEN_HERE> with a fresh token from the web app. Make sure you copied the full token with no leading or trailing spaces.

pandev status shows the daemon as not running

Re-run the install script (Step 1) to re-register the daemon, then check pandev status again.

Self-signed certificate on on-prem server

The plugin honours the Windows certificate store. Import your organisation's root CA into Trusted Root Certification Authorities (run certmgr.msc → Trusted Root Certification Authorities → Certificates → Import).

No data in the dashboard after 30 minutes

Confirm three things:

  1. pandev status reports authenticated and running
  2. pandev time shows a non-zero value
  3. The token belongs to the same account you are viewing in the PanDev Metrics UI

FAQ​

Where do I get the token?​

Open the PanDev Metrics web app, go to your profile / API settings, and copy your API token. The same token works for the IDE plugins.

Which terminals are supported?​

The plugin hooks into the shell, so PowerShell and Windows Terminal both produce heartbeats. Commands run inside WSL are captured by the Linux build instead.

Do I need administrator rights?​

Yes. Run the install script from a PowerShell window opened as Administrator — it registers the background daemon at the system level. After installation, day-to-day commands (pandev status, pandev time, pandev login) run in a normal, non-elevated window.

How do I switch accounts or servers?​

Run pandev login -t <NEW_TOKEN> with a token from the target account. The new token replaces the old one.