npm install -g @screenforge/director-cli. Start with director init — the commands below are ordered the way you’ll actually run them. Every command accepts --api-url (or $DIRECTOR_API_URL) to point at a non-default deployment; the default is https://api.director.screenforge.co/api.
director init
Installs the Chromium browser Director drives. Run this first — every other command that touches a browser depends on it.
director login
Signs the CLI in to your Director account via a device-code browser handoff. Does not mint an API key by itself.
Writes ~/.director/credentials.json (mode 0600), scoped per --api-url — switching API URLs requires signing in again.
director mcp
Wires Director’s hosted MCP endpoint into a coding agent’s config file.
Fails with a clear error if no supported agent is detected — pass
--agent explicitly in that case.
director session [code]
The one command that opens a real browser on your machine. Captures a session from logging into your own product and uploads it to Director — used whenever an environment needs a fresh authenticated session, not just during setup.
Refuses to upload a session that has zero cookies and zero origins.
director doctor
Read-only diagnostic — checks Node version, Chromium, saved account credentials, $DIRECTOR_API_KEY, and whether Director’s API is reachable. Fixes nothing; exits non-zero if any check fails. Run this any time something isn’t working.
director update
Checks npm for a newer @screenforge/director-cli release and installs it globally if one exists. No flags.
Every command (except
update itself) checks once a day whether a newer CLI version is available and prints a stderr nudge if so — silent under $CI, and never blocks or fails the command.