Skip to main content

Authentication

The Driverforge CLI authenticates you with Driverforge so it can act on your behalf — listing your organizations, talking to your controllers, and deploying drivers. You sign in once with driverforge login; the CLI stores the credentials locally and refreshes them automatically, so you rarely think about it again until you driverforge logout.

Preview

The driverforge CLI is in preview. Commands and flags documented here may change before the stable release. Follow along or share feedback on our roadmap.

Do I have to log in?​

No — the core of the CLI works anonymously. You can author, build, package, encrypt, and source-map a driver entirely offline, with no account and nothing to sign up for. That's the whole local development loop, available the moment you install driverforge.

Signing in unlocks the parts that go through the Anvil cloud — anything that needs Driverforge to know who you are and which controllers are yours: deploy and sync to push a build to a controller, agent to upgrade one, and org / device to choose where those act.

How it works​

driverforge login uses the OAuth 2.0 device authorization grant: it shows a short code, opens your browser to confirm it, and waits while you authorize — your password is never entered into or seen by the CLI. Credentials are stored locally and refreshed automatically.

Commands​