Skip to main content

Installation

Whet ships as a single desktop binary for macOS, Windows and Linux. The whet CLI is bundled with the app — once Whet Desktop is installed, the whet command is on your PATH and connects to the local instance automatically.

Download

Get the latest signed build from whet.so/coming-soon. We'll email you the moment the first public build ships.

When Whet Desktop is installed, opening it once registers the bundled whet binary and starts the local services (workbench UI, local MCP server, embedded database). You do not need a separate CLI install.

Verify

whet --version

Returns the installed version (e.g. whet 1.0.0-alpha.4). If the command isn't found, open Whet Desktop once and try again — the first launch wires the binary into your shell. On macOS the binary lives in /Applications/Whet.app/Contents/Resources/cli; on Windows in %LOCALAPPDATA%\Whet\cli; on Linux in ~/.local/share/whet/cli.

Confirm the local server

The local workbench listens on 127.0.0.1:7891 by default. The CLI already knows the address — no --base-url flag needed on the local instance.

whet auth status

Returns the configured base URL and token state. The agent token is generated automatically on first launch and persists in your OS keychain.

Next step

Connecting to a remote instance (Team / Enterprise)

If your team uses a shared deployment (Team or Enterprise plan), point the CLI at it with:

whet auth login \
--token <agent-token> \
--base-url https://your-team.whet.so/api/agent/v1

This writes ~/.whet/config.json with 600 permissions. The token is never logged.

Troubleshooting

Command not found: whet — open Whet Desktop once, then restart your terminal so it picks up the updated PATH.

401 Unauthorized on a Team / Enterprise instance — the token expired or was revoked. Generate a new one from the workbench UI under Settings → Agent tokens and run whet auth login again.

ECONNREFUSED 127.0.0.1:7891 — Whet Desktop isn't running. Open the app; the CLI will reach the local server automatically.