Skip to main content

Overview

The velatir command is installed on the system path by the Windows MSI and the macOS package. It is the supported way to control and script the desktop client.

At a Glance

Global Flags

Exit Codes

Control Commands

status

Show the current state of the desktop client: version, uptime, whether capture is running, and the last update check. Add --json for a structured result.

start

Activate AI traffic capture.

stop

Pause AI traffic capture without uninstalling. The client keeps running but stops capturing.

restart

Stop then start. Velatir re-binds on its own when the network changes, so a restart is only a manual fallback. See VPN compatibility.

Tray Icon

hide

Hide the system-tray icon. It stays hidden across restarts; capture continues normally. To hide it from install, use the VELATIR_HIDE_TRAY MSI property; see Enterprise deployment.

show

Show the tray icon again.

Update Commands

update

Check whether a newer version is available (does not download).
Add --apply to install and relaunch the new version immediately. Use this to force an update before the regular poll picks it up.

host restart

Restart Velatir’s capture process. It comes back within 30 seconds. Useful after a configuration change that needs a reload.

quit

Stop the desktop client. It will not restart on its own; it stays stopped until its service starts again (next boot, or sc start VelatirAgent on Windows) or you launch it manually.

Observability Commands

events

Stream the client’s event log. Filter by event type with --filter.

logs

Tail the agent or host log. Useful when diagnosing why traces are not appearing for an application.

version

Show the CLI, agent, and host versions.

health

Show current health and the reason and fix for any failing check. Exits 0 when healthy and non-zero when degraded, so it works as a monitoring probe. See Health checks.

test

Run a one-shot, end-to-end check of the install.
Sends a synthetic trace and prints the result. Success confirms the whole chain works: the client is running, the ingest key is valid, and the backend is reachable. It exits non-zero with a reason when something is wrong.

Configuration Commands

get-config

Show the effective configuration. The ingest key is masked.

set-api-key

Update the Velatir ingest key. Velatir restarts so the new key takes effect immediately; pass --no-restart to skip the restart.

set-ca

Provide a bring-your-own certificate authority. The file must be a PFX (PKCS#12) bundle. Velatir restarts so it takes effect immediately; pass --no-restart to skip the restart. See Enterprise deployment for the recommended distribution pattern.

Common Recipes

Verify the install end to end

velatir test confirms the client, ingest key, and backend are all working. To watch live capture instead, run velatir logs --host -f and trigger an interaction in a supported AI application.

Rotate the ingest key

Confirm with status that the masked key has changed.

Force the latest version

Re-bind after a VPN change

Only needed as a manual fallback; Velatir re-binds on its own when the network changes. See VPN compatibility.

Next Steps

Troubleshooting

Resolve agent-unreachable errors and other common issues.

Enterprise deployment

Drive the CLI from MDM and scripted rollouts.

How it works

Understand what the desktop client does.

FAQ

Quick answers to the questions that come up most often.