Authentication

Creating and running a local starter requires no GitHub or Vercel login. Repository operations need GitHub access; Vercel deployment needs Vercel access. Dashboard sync also needs a valid Forjex account connection.

forjex login

The CLI opens an authorization page on your configured Forjex origin. Sign in, review the connection, and authorize the CLI. Return to your terminal when authorization succeeds.

The authorization request expires after three minutes and can be consumed once. If it expires, run the login command again.

forjex login --token <your-github-token>

Replace the placeholder with your own GitHub token. The CLI validates it with GitHub. The token needs appropriate access for your repository operations.

Treat tokens as secrets. Supplying a token on the command line can leave it in shell history; prefer the browser flow for routine login.

The CLI stores credentials in ~/.forjex/config.json with owner-only file permissions. Do not commit or share this file.

forjex whoami
forjex logout

Logging out clears the local CLI configuration. Revoke a provider token in its provider settings if you need to invalidate it everywhere.

Connect Vercel separately when deploying. Signing in with GitHub alone does not grant Vercel access. Follow the deployment prompts or the website's credentials dialog, and check that the correct account or team owns the target project.