getsetgetsetfrom source to resource Agent Control Center
Theme
Apply for beta access
Docs/Install the CLI and sign in

Install the CLI and sign in

Use your ACC identity from a terminal. Enroll a runner separately when the machine should execute work.

Source-reviewed guide · deployment verification pending8 September 2026

Install

Use the published ACC CLI package. Check the beta invitation's supported release and platform requirements before installing.

npm i -g @tokenfactory/acc-runner
acc doctor

The package installs acc and the older acc-runner alias. Prefer acc in new instructions.

Sign in as yourself

acc login
acc whoami
  1. Follow the device-code instructions printed by the CLI.
  2. Open the authorization page on a trusted browser and sign in with your ACC identity.
  3. Confirm the device request you initiated.
  4. Return to the terminal. acc whoami should identify the expected account.

There is no separate CLI account to create. CLI access follows your account and organization permissions.

Personal sign-in is not runner enrollment

acc login signs you in. acc runner login registers this machine to receive work. The legacy acc-runner login means machine enrollment, not personal sign-in.

Sign out and revoke

acc logout

Your personal CLI session also appears in the app's session settings. Revoke it there if a device is lost. Runner credentials have a separate lifecycle; use the runner guide to disconnect a machine.

If authorization expires

Start a fresh login and approve the new code. Check the app address and account. Never paste tokens or screenshots of authorization codes into support requests.