Login
Connect the CLI to your contract.dev account.
login
contract-dev login [--no-browser] [--skill | --no-skill]The CLI shows a one-time code and opens the activation page. Approving there saves credentials to ~/.contract.dev/credentials.json, bound to your account and to the workspace active in the app at that moment. To act on another workspace, make it the active one in the app and log in again with workspace use.
| Flag | Description |
|---|---|
--no-browser | Print the activation URL instead of opening it. |
--skill | Also install the agent skill, without asking. |
--no-skill | Do not offer the agent skill. |
One-time code: ABCD-1234
Opening https://app.contract.dev/activate?code=ABCD-1234
Waiting for approval...
Logged in as you@example.com
Install the agent skill for Claude Code, Codex, Cursor and other agents? (Y/n)Logging in again replaces the saved credentials. When you belong to several workspaces, the CLI says which one the credentials are bound to.
Agent skill
At the end, login offers to install the agent skill, so Claude Code, Codex, Cursor and other coding agents can use the CLI. The question is asked once, at an interactive terminal; a declined offer is not asked again, and nothing is offered when the skill is already installed. contract-dev skills install installs it later. See Agent Integration.
whoami
contract-dev whoamiPrints the account and workspace the CLI acts as, the credentials file and app URL it uses, and the key’s id.
logout
contract-dev logoutRevoked the API key.
Removed /Users/you/.contract.dev/credentials.jsonThe key is revoked first, so it does not outlive this machine. If the server cannot be reached, the credentials file is still removed and the CLI says the key was not revoked.