FAQ & troubleshooting
Answers to common questions about Cordy for Chrome — cost, installing and updating, the consent dialog, permissions, WebGPU and local models, provider detection, keyboard shortcuts, and feedback.
Common questions and fixes. If something isn't here, the feature pages linked at the bottom go deeper.
General
Is Cordy free?
The extension is free. Because it's bring-your-own-key, you pay your AI provider directly for what you use — or nothing at all if you run local, on-device models. There's no Cordy subscription or account.
Is Cordy on the Chrome Web Store?
Yes. Install Cordy from the Chrome Web Store; it is the only supported install path, and Chrome updates it automatically. The .zip attached to each public release is published for verification, not as another way to install. See Installation.
How do I see what changed in an update?
Open Release notes at the bottom of the dashboard sidebar, or from the side-panel settings. The notes are bundled with the extension. Chinese interfaces show Chinese notes; other languages show English. From 2.5.5 on, each version links to its public release page, and All releases opens the full list. After an update, an Updated to v… notice offers View changes and Got it.
Where did the New Tab page go?
Cordy 2.5.3 removed its custom New Tab page (clock, wallpaper, and quick links). Search is on the dashboard Search page. To have Cordy open Collections when the browser starts, turn on Settings → General → Startup → Open Collections when the browser starts; it is off by default.
Which browsers and versions are supported?
Chrome 148 or newer. That is the extension manifest's minimum version.
Wasn't this called "Web Nexus"?
Yes — Cordy for Chrome was formerly Web Nexus. It was renamed to Cordy across the whole product. Older references to "Web Nexus" mean this extension.
Is my data safe?
Yes. Everything is stored locally, keys are encrypted, prompts go straight to the provider you configured, and there's no telemetry and no Cordy backend. The full model is in Privacy & permissions.
Setup and providers
Why did I see a "Send to a cloud AI service?" dialog?
That's the one-time cloud consent gate. The first time you send anything to a cloud model, Cordy confirms that your text goes to the provider you configured (and nowhere else). Accept it once; you can withdraw consent later in Settings → Data Management → Data & privacy. Local models never show it. See Privacy.
It says "AI feature not configured" or lists no models.
No provider is connected yet. Open Dashboard → Settings → AI Config → Provider Configuration, add your key, and click Detect. Then pick Chat under Feature Models. See Providers & models.
A provider shows "Unavailable" or isn't detected.
Re-check the API key and Base URL, then click Detect again. Confirm the key is active with the provider and that you have network access. For a custom OpenAI-compatible endpoint, remember to type its model IDs manually — the manual model list decides which models are available. Check model catalog is only a diagnostic; if it fails, the models you entered keep working.
Do I need an API key at all?
No. You can run entirely on-device with Chrome's Gemini Nano, in-browser Gemma, or a local runtime. See Local & on-device AI.
Site access and permissions
In-page features don't work.
Open Settings → Permissions and check In-Page Features. If it shows Not enabled, click Enable and approve Chrome's prompt. Chat and panel features are unaffected; only in-page features (selection menu, page read-aloud, the command palette, reading page content) need it. In-page features never run on browser pages, the Chrome Web Store, or extension pages.
The command-palette shortcut does nothing.
When the palette can't open on the current page, Cordy opens Settings → Permissions with a hint that explains why: website access is missing, the page is not an http or https page, or the page needs a reload.
Why didn't Cordy warn me it can "read all my data on all sites"?
Because it doesn't request that at install. Site access is optional and granted from a button when you choose to use in-page features. See Privacy & permissions.
How do I revoke access?
- Site access: Settings → Permissions → In-Page Features → Revoke access.
- Bookmarks, browsing history, clear browsing data: Settings → Permissions → Revoke on that row.
- Cloud consent: Settings → Data Management → Data & privacy → Withdraw consent.
Local models and WebGPU
What do local models need?
Turn on Local AI (Experimental) in Settings and accept the risk notice. In-browser models (Gemma) and Kokoro TTS require WebGPU; Gemini Nano requires enabling Chrome's AI flags. See Local & on-device AI.
"WebGPU is required but not available."
Your browser/device doesn't expose WebGPU. Update Chrome and your graphics drivers. If it still isn't available, use Chrome built-in AI or a local-native runtime instead of the in-browser models.
A model download is stuck or failed.
Cancel and retry, and make sure you have enough free disk space (the Gemma models are several GB). A stalled download can also mean WebGPU isn't available.
How do I enable Chrome's Gemini Nano?
Set chrome://flags/#prompt-api-for-gemini-nano to Enabled and chrome://flags/#optimization-guide-on-device-model to Enabled BypassPerfRequirement, relaunch Chrome, then use Initialize Model in Settings → Local AI.
Chat
How do I clear or export a conversation?
Use /clear to archive the current chat and start fresh, or /export to save it as Markdown. You can also copy any single message. See Chat.
My attachment was rejected.
Attachments are limited to 5 files, 10 MB each, and need a multimodal cloud model. Local models don't accept attachments — switch to a cloud model or remove the files.
The reply timed out.
The connection to the background worker was interrupted. Send again; if it keeps happening, click Reload side panel on the panel's error screen.
Keyboard shortcuts
Global (managed by Chrome, remappable at chrome://extensions/shortcuts)
| Action | Windows / Linux | macOS |
|---|---|---|
| Toggle the side panel | Ctrl + Shift + Y | Cmd + Shift + Y |
| Open the command palette | Ctrl + Shift + P | Cmd + Shift + P |
| Collect the current window's tabs | Ctrl + Shift + K | Cmd + Shift + K |
| Open the extension action | Ctrl + Shift + L | Cmd + Shift + L |
Chat and conversation tabs
| Action | Shortcut |
|---|---|
| Send message | Ctrl + Enter (default) or Enter (configurable) |
| New line | Enter or Shift + Enter (matches your send-key choice) |
| Browse input history | ↑ / ↓ in an empty composer |
| New conversation tab | Alt + T |
| Close current tab | Alt + W |
| Reopen last closed tab | Alt + Shift + T |
| Jump to tab 1–9 | Alt + 1 … Alt + 9 |
| Next / previous tab | Ctrl/Cmd + Tab / Ctrl/Cmd + Shift + Tab |
| Open command menu (in composer) | / |
| Insert a browser-context mention | @ |
You can change the send-message key in Settings → Shortcuts.
Feedback
Report bugs, ask questions, or suggest features here. For a bug report, export the logs from Settings → Logs → Export JSON and attach the file; logs exclude messages, replies, and keys.
Report security vulnerabilities privately through a GitHub security advisory, not as a public issue.