Google OAuth 2.0 PKCE flow in a React/Next.js app — no backend, no client secret

<h1> Introduction </h1> <p>Last time, we tore apart the core mechanics of <strong>RFC 6749 (Authorization Code Grant)</strong>.</p> <ul> <li><a

<p>Most "add MCP to your app" posts stop at stdio: a local process, a config file,<br /> a token you paste in. That works on your laptop and nowhere else. A <em>remote</em><br />

<p>Step by step on how to implement Google OAuth in Next.js with NestJS.</p> <p>Demo example: <a href="https://mamolio.vercel.app/signin" rel="noopener

<p><em>By **grloper</em>* (<a href="https://github.com/grloper" rel="noopener noreferrer">GitHub @grloper</a>)*</p> <h2> 1. Introduction: The Subscription Dilemma in Modern Agent

<p>When building a CLI tool that needs GitHub access, you have three options:</p> <ol> <li>Ask users to create a personal access token manually (bad UX)</li> <li>Redirect to a web

<h1> How I built keyless OAuth sign-in for my AI companion: PKCE, a single-use loopback callback, and a token that never touches disk </h1> <p>Ankita is my open-source desktop AI

<h2> Introduction </h2> <p>Authentication is one of those things that looks simple in a tutorial and becomes surprisingly complex in production. Between token storage, CSRF