whet init

whet init wires your MCP clients (Claude Code, Claude Desktop, Cursor, Cline) to your running Whet Desktop instance. It's the first command you run after installing the app.

What does it do?

1. Probes the local Whet Desktop instance at http://127.0.0.1:7891 to confirm it's responsive.
2. Resolves the agent bearer token — from --bearer-token, from ~/.whet/config.json, or from the OS keychain (in that order).
3. For each detected MCP client, writes the JSON entry that points to the local MCP URL with the resolved bearer token.
4. Verifies the Agent API responds with the resolved token.

Usage

whet init

Pass --yes to skip per-client consent prompts (agent-friendly mode):

whet init --yes

Flags

Flag	Type	Description
--bearer-token <value>	string	Use this token instead of resolving from ~/.whet/config.json or the OS keychain.
--base-url <url>	string	Override the Agent API URL the CLI probes. Defaults to http://127.0.0.1:7891/api/agent/v1.
--mcp-url <url>	string	Override the MCP endpoint URL that the MCP client configs reference. Defaults to http://127.0.0.1:7891/mcp.
--claude-code-scope <scope>	user | project	Where to install the Claude Code entry. Default: best-effort autodetect.
-y, --yes	flag	Skip per-client consent prompts. Required for unattended runs.

Expected output

$ whet init
✓ Whet Desktop reachable · http://127.0.0.1:7891/health 200
✓ Resolved bearer token from OS keychain
✓ Wrote Claude Code MCP entry (user scope)
✓ Wrote Claude Desktop entry · ~/Library/Application Support/Claude/claude_desktop_config.json
✓ Wrote Cursor entry · ~/.cursor/mcp.json
✓ Agent API verification · 200 OK

Done. Restart your MCP clients to pick up the new entries.

When to run it again?

• After installing or upgrading Whet Desktop.
• After rotating the agent token in Settings → Agent tokens.
• After pointing at a different instance (e.g. a Team deployment) — pass --mcp-url and --base-url to update every client at once.

Related

• whet auth status — print resolved token + base URL state.
• whet doctor — full diagnostic across local server, OAuth credentials, and adapter rate-limit headroom.