oauth-login

Automate OAuth login by running a browser flow that handles local callbacks and persists access tokens directly into your project's environment variables. This reduces manual login steps and credential handling for browser verification.

Yes, Playwright MCP is required to automate the Google and GitHub OAuth login flows. It drives the browser-based verification process, handles the local OAuth callback, and captures the tokens for storage.

You need valid OAuth credentials with appropriate redirect URIs configured for Google or GitHub, along with a browser automation tool like Playwright MCP. The skill uses these to complete the login flow and write tokens to your environment.

Yes, the OAuth automation skill stores access tokens in your project's .env file and saves refresh tokens when they are available from the provider's response during the login flow.

The best way to trigger an automated OAuth login flow is to run the command with your chosen provider, then follow the prompts to authorize the application and automatically save the returned tokens to your environment.

Browser automation for local OAuth callback verification is limited to Google and GitHub providers and requires valid OAuth credentials with correctly configured redirect URIs to successfully complete the token exchange and storage.