Built-in AI API with local build.

189 views
Skip to first unread message

arnaud...@intel.com

unread,
Jun 18, 2025, 7:10:56 AM6/18/25
to Chromium-dev
Hello there!

I m trying to use Built-in AI API on my local chromium built.

translator API works fine on chrome, Canary and Chromium own build.
https://developer.chrome.com/docs/ai/translator-api
I can create, and download missing language and translate.

Language Detector API doesn t work on my local build.
https://developer.chrome.com/docs/ai/language-detection

The API is existing, it works fine on Chrome and Canary.
asking the availability on my own build returns: "downloadable"
Creating a languageDetector is hanging (no returned promises). I would expect a download to start, but nothing happens.
https://developer.chrome.com/docs/ai/language-detection#api_playground doesn't launch properly either.

Apparently it happened to other people and other OSes.
I filed a bug: https://issues.chromium.org/issues/422910890 but no real answer yet.

My main question is: Do I need Google API keys? which one, since I cannot find any API key related directly to AI.

Thanks in advance.
Arno

Reilly Grant

unread,
Jun 18, 2025, 1:21:59 PM6/18/25
to arnaud...@intel.com, Chromium-dev
The right people are already responding to your bug and will continue to follow up there.
Reilly Grant | Software Engineer | rei...@chromium.org | Google Chrome


--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/1be76e61-e64c-4a91-bcf8-6f9744cfcdd9n%40chromium.org.

arnaud...@intel.com

unread,
Jun 19, 2025, 1:52:03 AM6/19/25
to Chromium-dev, Reilly Grant, Chromium-dev, arnaud...@intel.com
I would hope so,  I was just trying my chance here with a broader audience, if someone experienced the same and obviously see what I m missing to get it to work.
Because it seems that no one, involved in the bug, can reproduce my issue, most probably because they all have worked before with built-in AI API and have the model "available", or they have some access which I don't or I'm not aware of.
When I asked a random friend, experimented chromium developer, who never worked with LanguageDetector before, he reproduced it on first try, another OS.
Reply all
Reply to author
Forward
0 new messages