@tellwang/cli

Shell access to the TellWang control plane. tellwang exposes every control-plane tool as a command, discovering them from the server so it cannot drift from the API.

npm i -g @tellwang/cli
tellwang login
tellwang commands
tellwang get-release-status --wok-id mystg | jq -r .latest_attempt.id

Why a CLI

An agent host has to register an MCP server, and that registration is the part that intermittently fails. A binary on $PATH has no handshake. --help is universal discoverability, output is JSON so it pipes, and a flag parser refuses a missing required argument before a request is sent — naming the flag and, for promote, where to obtain its value.

Authentication

tellwang login runs the control plane's existing MCP OAuth: dynamic client registration, authorization code with S256 PKCE on a 127.0.0.1 callback, and a refresh token. Same flow Claude Code and Cursor use; the session is revocable centrally.

Credentials resolve in order:

1. TELLWANG_API_KEY — CI and automation; overrides everything.
2. /run/tellwang-secrets/mcp-key — a hosted Agent Cell is already credentialed, so it needs no login.
3. ~/.tellwang/credentials (mode 0600) — your OAuth session, auto-refreshed.

tellwang whoami reports which is in play without printing it.

Skill

skills/SKILL.md ships with the package — point an agent at it for the conventions that matter: ship with git, pin promotions from a verified receipt, verify before claiming, migrations over ad-hoc SQL.

Platforms

Prebuilt for macOS, Linux, and Windows on both arm64 and x64 — six static binaries, no runtime dependencies beyond the Node launcher npm installs it with. Anywhere else, build from source: cd cli && go build -o tellwang .