Image Description: The screenshot shows the "Extract Members from Group" interface with:

• Group URL input: "https://t.me/LWF_STARS" with an eye icon button (circled in red - not working)
• Extraction Settings: Safe Mode 1.5s, Recently Active filter, 1,000 member limit, Skip Bot/Fake toggles enabled
• "Extract Active Members" button at bottom (circled in red - not working)

Let me diagnose both buttons by examining the component, event handlers, and API endpoints:

Good, I can see the code. Now let me check the group-info API and also find where the button is rendered in the UI to ensure the onClick handler is properly connected:

Now let me find the Extract Active Members button and check if the onClick handler is properly connected:

Now I can see the issue. The "Extract Active Members" button has onClick={handleExtract} and is disabled when !selectedAccount || !groupUrl.trim() || extracting. Let me check how selectedAccount is set and if there's an issue with account selection:

Now I understand the full picture. The buttons ARE properly connected with onClick handlers, but they might be disabled because:

1. selectedAccount is null (no account selected)
2. The account list might not be loading properly

Let me check if there's a problem with auto-selecting an account when there's only one, and also add more robust error handling:

I've enhanced the component with:

1. Auto-select account: Now automatically selects the first account if only one is connected
2. Better URL normalization: Handles @username, plain groupname, and full URLs
3. Comprehensive debug logging: Added [v0] console logs to trace execution flow
4. Better error feedback: Shows specific error messages when validation fails
5. Detailed API logging: Logs request/response data for debugging

Check your browser console (F12 > Console) after clicking the buttons to see what's happening. The logs will show exactly where the process fails.

I see the issue! The /api/telegram/accounts endpoint is returning a 400 error, which prevents the account list from loading. This is why the buttons are disabled - selectedAccount is null because accounts never load.

Let me diagnose the API and fix it:

I found the issue. The component is sending the user code via the X-User-Code header:

But the API is looking for it in the query parameters:

This mismatch causes the 400 error. Let me fix the API endpoint to read from the header instead:

Fixed the 400 error by updating the API to read the user code from the X-User-Code header instead of query parameters. This aligns with how the frontend component is sending it, allowing the accounts list to load properly and enabling both the "Extract Active Members" and account selection features.