Pre-validate Credentials: Catch Errors Before Job Execution

Introduction

Have you ever started a job only to have it fail minutes later with an "authentication error"?

With DevLoop Runner's Credential Validation feature, you can verify that your GitHub tokens and AI credentials work correctly before running any jobs. Get immediate feedback on issues, saving you valuable time.

What is Credential Validation?

Credential Validation tests whether your configured credentials actually work.

What Gets Validated

1. GitHub Token

   • Repository access permissions
   • Pull request creation permissions
   • Issue read permissions

2. AI Credentials

   • OpenAI API Key validity
   • Codex auth.json authentication
   • Claude Code Credentials expiration
   • Anthropic API Key validity

Understanding Results

After validation completes, you'll see status for each credential:

• ✅ Success: Credential is working correctly
• ⚠️ Warning: Works but needs attention (e.g., expiring soon)
• ❌ Failed: There's a problem with this credential

How to Use

Step 1: Access Settings Page

1. Click "Settings" in the sidebar
2. Scroll down to the "Credential Validation" section

Step 2: Run Validation

1. Select the GitHub Account to validate with
2. Click the "Validate Credentials" button
3. A validation job will start

Step 3: Review Results

Once validation completes (usually 1-2 minutes), you'll see a summary:

• Results for each category (git, openai, claude, anthropic)
• Specific error messages for any issues
• Recommended actions to fix problems

Common Validation Errors and Solutions

GitHub Token Issues

"Bad credentials" Error

• Token is invalid or expired
• Generate a new token and re-register it

"Resource not accessible" Error

• Missing required permissions
• Ensure the repo scope is granted when generating the token

AI Credential Issues

"Invalid API key" Error

• API key may not have been copied correctly
• Generate a new key from the provider's console

"Rate limit exceeded" Error

• You've hit the API usage limit
• Wait a while or upgrade your plan

"Credentials expired" Error

• Claude Code Credentials have expired
• Obtain and update with new credentials

Best Practices

Regular Validation

• Always validate after registering new credentials
• Validate accounts that haven't been used recently
• Update Claude Code Credentials before they expire

When Troubleshooting

1. Run validation first to identify the issue
2. Fix based on the error message
3. Re-validate to confirm the problem is resolved

Team Usage

• If you have multiple GitHub accounts registered, validate each one
• AI credentials are shared settings, so one validation covers all jobs

Summary

• Pre-validation: Catch problems before running jobs
• Detailed feedback: Clear understanding of what's wrong
• Time savings: Reduce failed jobs due to auth errors

When in doubt about your credentials, run a validation first. If there are issues, you can address them before running actual jobs.