Support & Troubleshooting

Installation

How do I install the gulaq Chrome extension?

gulaq is currently installed in Developer Mode (before Chrome Web Store publication):

• Clone or download the gulaq repository from GitHub.
• Open Chrome and go to chrome://extensions.
• Enable Developer Mode (top right toggle).
• Click Load Unpacked and select the extension/ folder from the repository.
• Note the Extension ID shown under the gulaq extension card — you will need this for native host registration.

How do I install the Desktop Vault?

• Navigate to the native-host/ folder in the repository.
• Run cargo build --release to compile the native host binary.
• Run node scripts/install.js <your-extension-id> to register the native messaging host with Chrome.
• For the Tauri desktop GUI, navigate to the desktop/ folder and run npm run tauri dev.

Native Messaging & Desktop Vault

“Native host unavailable” error

This error means the Chrome extension cannot connect to the local Desktop Vault. Common causes:

• Desktop Vault not running — Make sure the gulaq desktop app or native host is running. Start it via the Tauri app or run the native host binary directly.
• Wrong extension ID in host manifest — The native host manifest must include your exact extension ID. Re-run the install script with the correct ID from chrome://extensions.
• Native host manifest not registered — On Windows, the manifest must be registered in the Windows Registry. On macOS/Linux, it must be placed in the correct system directory. Run the install script again to fix this.
• Binary not found — Ensure cargo build --release completed successfully and the binary exists in target/release/.

Desktop Vault not saving data

• Verify the vault folder path in the desktop app settings. Ensure the path exists and has write permissions.
• Check that the SQLite database is not locked by another process.
• Restart the desktop app and try again.
• Check available disk space — SQLite writes will fail if the disk is full.

Sign-In & Authentication

Google login is not working / “provider not enabled”

• Ensure the Google OAuth provider is enabled in the Supabase dashboard under Authentication → Providers.
• Verify that the Supabase redirect URL is correctly configured in Google Cloud Console OAuth credentials.
• If using the extension identity API, confirm the extension ID is listed in the authorized origins in Google Cloud Console.
• Try signing in again after clearing the extension’s local storage via chrome://extensions → Details → Inspect views → Clear storage.

Supabase redirect URL error

The redirect URL after Google sign-in must be whitelisted in both Supabase and Google Cloud Console. The URL typically takes the form: https://<your-supabase-project>.supabase.co/auth/v1/callback. Check that this URL is added under Supabase → Authentication → URL Configuration → Redirect URLs.

Signed out unexpectedly

• Supabase auth tokens expire. The extension should auto-refresh them, but if the device was offline during expiry, a re-sign-in may be required.
• Clearing browser data or extension storage will also clear the stored session.

AI Chat Capture

AI chat capture is not working on a supported platform

AI platforms regularly update their page structure. This can break DOM-based capture. Common causes:

• Platform changed its DOM — Check the gulaq GitHub repository for updated adapters or a patch. Report the issue if no fix is available yet.
• Content script not injected — Go to chrome://extensions, click Details on gulaq, and confirm it has permission for the affected domain. Try reloading the AI platform tab.
• Page not fully loaded — gulaq content scripts run at document_idle. Ensure the page has finished loading before triggering capture.
• Conversation too large — Very long conversations may take extra time. Try using Accuracy Mode for large chats.

Capture completeness score is low

• Scroll the entire conversation to the top and then to the bottom before capturing — some platforms use virtual DOM and do not render off-screen messages.
• Use Accuracy Mode (Guided capture) to step through the conversation section by section.
• For very large conversations, try capturing in segments.

Duplicate chats appearing in vault

• gulaq deduplicates captures before writing to the vault. If duplicates appear, check whether the same conversation was captured multiple times before dedup processing completed.
• You can manually delete duplicate entries from the desktop app vault manager.

Workspace Restore

Restored tabs require sign-in

gulaq saves tab URLs but does not save cookies, session tokens, or authentication state for third-party websites. If your session on a restored website has expired, you will need to sign in again. This is by design — gulaq does not have access to cookies for third-party sites.

Restore is waiting / hanging

• If restoring from the desktop vault, ensure the gulaq Chrome extension is running and the native messaging connection is active.
• Large workspaces (100+ tabs) may take several seconds to restore. Allow up to 30 seconds before considering it stuck.
• Check whether Chrome is rate-limiting tab creation. Try restoring in smaller batches.

Tab groups are not restored correctly

• Ensure the tabGroups permission is granted to the extension.
• Tab group colors and titles should restore correctly. If they don’t, try saving the workspace again and re-restoring.

Account & Access

Features are not available after sign-in

• gulaq is currently free with full feature access — no trial or payment is required.
• Ensure you are signed in. Some features require an authenticated account.
• Sign out and sign in again to refresh your account status.
• If the issue persists, contact us with your account email for manual verification.

“Account check failed” error

• This error means the extension could not reach the Supabase backend to verify your account. Check your internet connection.
• If your internet connection is fine and the error persists, the Supabase service may be temporarily unavailable. Check the Supabase status page and try again later.