Install

Install the CLI

npm i -g @wrktr/cli
# or, without Node:
curl -fsSL https://wrktr.com/install | sh

Either way you get a standalone binary for macOS or Linux; it needs git. The install script puts it in ~/.wrktr/bin (set WRKTR_INSTALL_DIR to change that) and installs the latest release (set WRKTR_VERSION to pin one).

Check it:

wrktr --version

Set up the machine

wrktr setup

wrktr setup does everything a machine needs, and is safe to run again: each step it finds done, it skips.

1. Signs in (wrktr login): it shows a code and opens the browser for you to approve. The token it receives is saved in ~/.wrktr/config.json, readable only by you.
2. Runs the daemon as a login service (wrktr daemon install). The service is a macOS LaunchAgent; elsewhere, run wrktr daemon under your own supervisor (systemd, a container’s entrypoint).
3. Installs the agent skill (wrktr skill install), which teaches Claude Code and other agents to work the wrktr way. It goes in ~/.claude/skills and ~/.agents/skills.

Given a project, wrktr setup <org>/<project> also gets you a copy to work in: a clone if it’s yours, otherwise a fork into your personal organization. That’s how the starter is meant to be tried.

wrktr whoami          # who the CLI acts as, and your organizations
wrktr daemon status   # what the daemon is syncing

In CI and sandboxes

Skip login and give the CLI a personal access token instead:

wrktr token create --name ci   # once, on your machine: you approve it in the browser
export WRKTR_TOKEN=<the token it printed>

A token can’t create tokens by itself: only a person signed in to the web app can approve a new one. See Scripting wrktr and API authentication.

Next: the quickstart.