Skip to main content
Authentication links the CLI to your nowrun account. Running nowrun login does double duty: it signs the CLI in and installs the nowrun skill, so your AI agent can self-discover every available command from that point on. It also registers the hosted nowrun-docs MCP server in your tool’s config.

​
Run nowrun login

The CLI prints an approval URL and opens your browser. Approve the device while signed in to your nowrun account, and the CLI picks up the session automatically. There is no token to find or paste. Approving in the browser is the entire step.
The approval window is about five minutes. If it lapses you get a clear timeout, and running nowrun login again issues a fresh code.

​
What it sets up

  1. Authenticates the CLI with your account, so deploys are attributed to you.
  2. Installs the nowrun skill into your AI tool, which teaches your agent the command surface and how to use it, and registers the hosted nowrun-docs MCP server so the agent can read these docs while it works.

​
If your agent is running this

The agent cannot approve the device for you. It will run nowrun login, show you the URL, and wait until you approve. Once you do, it continues on its own.

​
Check the session

This validates against the backend rather than only checking local state, so it tells you when a session has been revoked or has expired instead of reporting a stale one as healthy.

​
Re-authenticating and signing out

nowrun login is safe to re-run at any point, on a new machine or after a fresh install. nowrun logout signs out and deletes the stored credentials.

​
No browser on this machine?

nowrun login prints the approval URL before it tries to open anything. On a server, a container, or over SSH, open that URL on your phone or another computer and approve there. The waiting command picks the session up as soon as you do.
Next: Deploy your first app