Get started
CLI and slash commands
Four commands you run in a terminal, and seven you type inside a Claude Code session. You will mostly only ever need setup and doctor.
Terminal commands
Each of these runs a fresh copy, so they work even when an existing install is broken.
- setup installs everything and signs you in. Safe to re-run.
- auth signs you in again, on its own. Use it if your token expired or you switched account.
- update updates the CLI and the plugin to the current release.
- doctor checks your install and prints what it found.
npx -y @lineman-io/cli@latest setupnpx -y @lineman-io/cli@latest authnpx -y @lineman-io/cli@latest updatenpx -y @lineman-io/cli@latest doctorInstalling the command permanently
If you would rather type lineman than the full command each time, install it globally.
npm i -g @lineman-io/cli@latestInside a Claude Code session
These work in any session with the plugin installed.
/lineman:authsign in, or switch account/lineman:doctorthe same checklist, without leaving your session/lineman:statswhat Lineman has saved you so far/lineman:upgradewhat your plan includes, and what a higher one would add/lineman:linemanhow to run a supervised session/lineman:statuslineturn the savings statusline on or off/lineman:telemetrysee or change what usage data is sent
Settings and overrides
Settings live in ~/.lineman/config.json. You can override them per session with environment variables, which is mainly useful in CI.
LINEMAN_API_TOKENsigns in without a browser. This is what you set in CI.LINEMAN_TELEMETRYturns usage reporting off.
An environment variable always wins over the config file, and is never written back to it.