403 Permission denied on resource project default when using Gemini CLI | Kilo | Page 1

tame kite Nov 2, 2025, 3:46 PM

#

Generally, I've been able to use Gemini CLI as a provider with Kilo Code with no issue, but today when trying to use the provider, Kilo Code returns a 403 error. I've tried uninstalling and reinstalling Gemini CLI, re-authenticating with OAuth using my Google account, and restarting VS Code to no avail.

indigo vessel Nov 2, 2025, 4:24 PM

#

Did you check if Gemini cli even works for you?

tame kite Nov 2, 2025, 4:25 PM

#

indigo vessel Did you check if Gemini cli even works for you?

Through the standard CLI interface?

#

yes

indigo vessel Nov 2, 2025, 4:26 PM

#

Huh, then you do have access

#

Could be project error. Iirc kilo does not have dynamic project Discovery

#

Wait for someone to look at this

tame kite Nov 2, 2025, 7:02 PM

#

indigo vessel Wait for someone to look at this

Should I create a GitHub issue for this, or stay in here for now?

indigo vessel Nov 2, 2025, 7:02 PM

#

your choice

tame kite Nov 2, 2025, 7:08 PM

#

Actually nvm, just found a solution from a previous GitHub issue

#

https://github.com/Kilo-Org/kilocode/issues/2838#issuecomment-3390547262

GitHub

GEMINI CLI error · Issue #2838 · Kilo-Org/kilocode

Plugin Type VSCode Extension App Version 4.100.0 Description Gemini CLI API error: [{ "error": { "code": 403, "message": "Permission denied on resource project de...

#403 Permission denied on resource project default when using Gemini CLI