[BUG] Local coding API keys generated through the UI can never authenticate due to database column mismatch

[Ridanshi]

Bug Summary

API keys generated through the local coding key creation flow are stored in a different database column than the authentication flow uses for verification.

As a result, all generated keys are permanently invalid.

Describe the bug

The key creation endpoint stores hashes in:

api_key

The synchronization endpoint validates using:

api_key_hash

The creation flow never populates api_key_hash.

Therefore authentication queries always return zero matches.

To Reproduce

1. Create a local coding API key.
2. Save the generated key.
3. Attempt synchronization using:

Authorization: Bearer

4. Observe:

{
"error": "Invalid API key"
}

5. Repeat with newly generated keys.
6. Observe identical failure.

Expected behavior

Keys generated through the UI should authenticate successfully.

Actual behavior

Every generated key is rejected.

Additional context

Affected files:

• src/app/api/local-coding/keys/route.ts
• src/app/api/local-coding/sync/route.ts

Related migrations:

• 20260521000000_add_local_coding_tables.sql
• 20260522000000_add_api_key_hash_column.sql

This currently makes the entire local coding sync feature unusable.

[Ridanshi]

Hi @Priyanshu-byte-coder,
I investigated this issue and would like to work on a fix.

The key creation flow and key verification flow currently use different database columns, causing all generated API keys to fail authentication.

I plan to:

• align storage and verification logic
• preserve existing API key workflows
• add integration tests covering key generation and authentication

Please assign this issue to me.