anomalyco / anomalyco/opencode

Zen signup fails after successful Google and GitHub authentication: Invalid email

Open
#39,414 3 comments 0 reactions 1 assignee View on GitHub

@StarpTech is already working on this.

Since Jul 29, 2026.

Dominant language
TypeScript
Stars
209k
Forks
27.5k
PR merge metrics
PR metrics pending

Description

Description

I am unable to create or access an OpenCode Zen account.

Both authentication providers complete successfully:

  1. Google with a personal, normal @gmail.com account
  2. GitHub with a verified email address

After authentication redirects back to OpenCode, the browser displays a blank page containing:

{"error":"No authorization code found.","cause":{"error":"server_error","error_description":"Invalid email"}}

The identical error occurs with both providers.

Additional information:

  • Personal Gmail account (not Google Workspace)
  • Verified GitHub account
  • Chrome 150
  • Incognito mode tested
  • Cookies cleared
  • Both Google and GitHub authentication complete successfully.
  • The error only occurs after OpenCode redirects back from the authentication provider.
Plugins

None

OpenCode version

Not installed. This occurs during account authentication on the website.

Steps to reproduce
  1. Go to https://opencode.ai/auth
  2. Click "Continue with Google".
  3. Authenticate successfully with a personal Gmail account.
  4. After Google redirects back to OpenCode, a blank page appears containing:

{"error":"No authorization code found.","cause":{"error":"server_error","error_description":"Invalid email"}}

  1. Repeat using "Continue with GitHub".
  2. The exact same error occurs.
Screenshot and/or share link
Image
Operating System

Ubuntu 18.04 LTS

Terminal

Not applicable (website authentication issue)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.