We're here to help
Stuck on something, found a bug, or have an idea to make ColibotAI better? Start with the Guide for step-by-step answers, open an issue on GitHub, or reach out directly. We read everything.
Find the right channel
Most questions are answered in the Guide. For bugs and feature requests, GitHub keeps everything tracked in the open.
Read the Guide
Install, choose your AI engine, set up on-device or your own key, notes, shortcuts, privacy and troubleshooting — all in one place.
Open the GuideReport a bug
Something not working? Open a GitHub issue with the details below and we'll dig in. Public issues help other users too.
Open an issueRequest a feature
Tell us what would make ColibotAI better for you. See what's already planned on the roadmap and add your voice.
See the roadmapHelp us fix it faster
A good report gets a quick fix. Turn on Debug mode for detailed errors, then include these details.
- What you did — the page, the text you selected, and which action (Translate / Summarize / Explain / Search / Quick Translate).
- Your engine setup — on-device, or which provider and model (never paste your API key).
- What happened vs. what you expected — the exact error text helps. Enable Debug mode (Settings → Behavior) for the raw provider/HTTP detail.
- Your environment — Chrome version and OS. On-device AI needs Chrome desktop 138+.
Troubleshooting on-device AI? The Guide's Troubleshooting & FAQ section covers the chrome://flags and chrome://components steps.
Contact the team
Prefer to write to us directly — for support, partnerships, or anything that doesn't fit a GitHub issue? Send a message and we'll get back to you. Published by WebWakeUp, made by Edoardo Guzzi.
For privacy or data requests, see the Privacy Policy. ColibotAI stores no analytics and has no backend — your support message is the only thing we receive.
Common questions
On-device AI says "Unavailable" — what do I do?
On-device AI needs Chrome desktop 138+ and capable hardware, and downloads a model on first use. Follow the steps in the Guide's On-device AI section, then click Recheck. Or set the engine to Auto so it falls back to your API key.
My API key is rejected on save.
Double-check the key and that you granted the provider's host permission when saving. ColibotAI runs a zero-token check on save and shows ✓ valid / ✗ rejected immediately. See Bring your own key.
My custom / local endpoint is unreachable.
Verify the Base URL (usually ends in /v1), that the server is running, and that it allows browser requests (CORS). Details in Custom / Local LLM.
Where are my notes, and can I back them up?
Notes live locally in your browser. Use Export in the side panel for a JSON backup and Import on another device. More in the Guide's Notes section.
Is ColibotAI free?
Yes. The extension is free and on-device AI is free. With your own key you pay only your provider's usage directly. A local / custom model is free too.
How can I support the project?
Star us on GitHub, leave a Chrome Web Store review, or chip in on the Donations page. Thank you!