Integrations

Google Sign-In

NeuralCode includes a real OAuth 2.0 + PKCE desktop sign-in flow for Google, using a localhost loopback — the recommended pattern for native apps.

How it works#

The flow follows Google's recommended desktop pattern. NeuralCode opens your system browser to Google's consent screen, runs a temporary loopback server on 127.0.0.1 to catch the redirect, exchanges the authorization code (secured with PKCE), and fetches your basic profile.

1
Configure credentials
Provide a Google OAuth client ID (and, for “Web”-type clients, a secret) in settings. These are stored locally.
2
Sign in
Trigger Google sign-in; your browser opens to accounts.google.com with a PKCE challenge.
3
Approve
After you approve, Google redirects to the local loopback, the code is exchanged for tokens, and a styled “Signed in” page confirms it.

Scopes & data#

Item	Detail
Scopes	`openid`, `email`, `profile` — basic identity only.
Stored	Your name, email and picture (the profile).
Not stored	The Google access token is not persisted — only the resulting profile.

Optional integration

Google sign-in is an available capability in NeuralCode's flow layer. The primary identity used across the app — for pushing branches and opening PRs — is GitHub. Sign out at any time to clear the stored Google profile.

MCP servers

Settings