login Command

Log the Frame-Master CLI in to frame-master.com so you can publish plugins and templates.

📖 Usage

frame-master login
frame-master login --no-browser
frame-master login --host 100.96.0.3
frame-master login --code 'http://127.0.0.1:port/callback?code=...&state=...'
frame-master logout
frame-master whoami

🔐 How it works

The CLI starts an OpenAuthster authorization-code login with PKCE.
Your browser opens the issuer. Sign in with the same account you use on frame-master.com.
The issuer redirects to a loopback callback on 127.0.0.1.
On the same machine, the CLI receives that callback. Over SSH, or when the browser cannot reach this host, paste the redirected URL (the address bar still has the code if the page fails to load) or pass --code.
The CLI stores the access and refresh tokens in ~/.openauthster/ (0600). No project secret is stored.

frame-master logout deletes those tokens locally. It does not revoke the refresh token on the issuer.

Override the site with FRAME_MASTER_BASE_URL for local docs. FRAME_MASTER_TOKEN can still pass an access token instead of the token file, for CI.

⚙️ Options

--no-browser — Print the authorize URL without opening a browser
--code <callback> — Finish login with a pasted callback URL or authorization code
--host <address> — Bind the callback on a private address (100.96.0.3, 192.168.1.20, 10.0.0.5). The redirect URI is http://<address>:<port>/callback
-h, --help — Show help

👤 Related commands

frame-master logout — Delete the stored OpenAuthster tokens
frame-master whoami — Show the logged-in user and GitHub App status
frame-master whoami --json — Print the same data as JSON

Publishing requires an active GitHub App link whose login matches the repository owner. If whoami says GitHub is not connected, open the printed install URL (usually /settings) and install the Frame-Master GitHub App on your personal account.

🎯 Next Steps