Clerk Debug Bundle

Overview

Collect all necessary debug information for Clerk troubleshooting and support.

Prerequisites

• Clerk SDK installed
• Access to application logs
• Browser with developer tools

Instructions

1. Step 1: Environment Debug Script
2. Step 2: Runtime Health Check
3. Step 3: Client-Side Debug Component
4. Step 4: Request Debug Middleware
5. Step 5: Generate Support Bundle

For full implementation details and code examples, load: Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)

Output

• Environment debug information
• Runtime health check endpoint
• Client-side debug panel
• Support bundle script

Error Handling

Issue	Debug Action
Auth not working	Check /api/clerk-health endpoint
Token issues	Use debug panel to inspect token
Middleware problems	Enable CLERK_DEBUG=true
Session issues	Check session state in debug panel

Resources

• Clerk Support
• Clerk Discord
• GitHub Issues

Next Steps

Proceed to clerk-rate-limits for understanding Clerk rate limits.

Examples

Basic usage: Apply clerk debug bundle to a standard project setup with default configuration options.

Advanced scenario: Customize clerk debug bundle for production environments with multiple constraints and team-specific requirements.