workos-convex-debug

Diagnose and fix WorkOS AuthKit authentication issues in Convex deployments.

5|1|Updated May 31, 2026
One-click install
npx skills add https://github.com/waynesutton/teleprompter --skill workos-convex-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workos-convex-debug
Source: https://github.com/waynesutton/teleprompter/tree/main/.cursor/skills/workos-convex-debug
Command: npx skills add https://github.com/waynesutton/teleprompter --skill workos-convex-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides guidance to diagnose and troubleshoot authentication issues in Convex apps using WorkOS AuthKit, helping teams quickly identify and resolve sign-in failures, missing email claims, and JWT validation problems.

Core Features & Use Cases

  • Comprehensive diagnostic guidance for common issues such as sign-in button not working, identity returning null, missing email fields, admin checks failing, and OAuth callback problems.
  • Environment and configuration validation, including environment variables, WorkOS dashboard JWT templates, and deployment readiness of Convex auth config.
  • Debugging utilities and best practices with logging strategies for frontend and backend to surface root causes.

Quick Start

Follow the diagnostic checklist to reproduce and resolve a WorkOS AuthKit authentication issue in a Convex deployment.

Frequently Asked Questions about workos-convex-debug

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does WorkOS AuthKit return a null identity during Convex sign-in?

WorkOS AuthKit returns a null identity during Convex sign-in when JWT validation fails due to missing claims or incorrect provider configuration in auth.config.ts. Diagnose by verifying environment variables and ensuring the WorkOS dashboard JWT template is correctly configured.

How do I fix missing email claims in a Convex WorkOS authentication deployment?

Fix missing email claims in Convex WorkOS authentication by validating the JWT template configuration in the WorkOS dashboard and checking that the deployed Convex auth.config.ts correctly maps identity fields. Frontend and backend logging helps surface the root cause of the missing fields.

What environment variables are required for WorkOS AuthKit with Convex?

WorkOS AuthKit with Convex requires VITE_WORKOS_CLIENT_ID, VITE_WORKOS_REDIRECT_URI, and WORKOS_CLIENT_ID. These environment variables must be correctly set across local development and Netlify or Convex production setups to prevent sign-in failures and OAuth callback errors.

How do I troubleshoot OAuth callback problems with WorkOS in a Netlify and Convex production setup?

Troubleshoot WorkOS OAuth callback problems in Netlify and Convex by verifying the VITE_WORKOS_REDIRECT_URI matches the production domain, confirming environment variables are deployed, and validating the Convex auth.config.ts multiple providers setup against the WorkOS dashboard configuration.

Do I need a specific auth.config.ts configuration for WorkOS admin checks in Convex?

Yes, WorkOS admin checks in Convex require a correctly deployed auth.config.ts supporting multiple providers. When admin checks fail, validate the JWT validation logic and ensure the WorkOS dashboard JWT template includes the necessary role or identity claims.

What is the best way to debug JWT validation errors with WorkOS AuthKit and Convex?

Debug JWT validation errors with WorkOS AuthKit and Convex by applying frontend and backend logging strategies to surface root causes. Validate the WorkOS dashboard JWT templates, check environment variables, and confirm the deployed Convex auth.config.ts matches the expected provider configuration.