Gemini CLI最优雅的食用方法【爽用gemini-2.5-pro不占用API额度】

开发调优
,
1

主包白嫖习惯了，不想花钱买ai coder订阅，研究了一段时间还是OAuth登录Gemini CLI是目前无成本，性能最强的路子。

食用方法如下：

  1. 安装 Node.js（这个不用指导了吧）
  2. 安装 Gemini CLI npm install -g @google/gemini-cli
  3. 在你的项目目录创建.env文件
  4. 文件里面写你的本地代理端口
http_proxy=http://127.0.0.1:{port}
https_proxy=http://127.0.0.1:{port}
no_proxy=localhost,127.0.0.1
  1. Gemini启动！gemini 或者指定模型启动gemini -m "gemini-2.5-pro"
  2. 选择使用goggle账户登陆。
  • 权限：默认可访问 Gemini 2.5 Pro 模型，支持最大 1M token 的上下文窗口。
  • 计费：免费额度为每日 1,000 次请求。
  • 说明：登录时使用 Google 账户，无需管理 API 密钥，适合个人开发和试用。
  • 重要：最主要这不会占用你的免费API额度！
76 个赞
佬们最近写代码都用的啥AI工具
2

感谢大佬分享

5 个赞
3

还有什么方法能打的？

1 个赞
4

2api可以指定2.5pro模型吗？

1 个赞
5

同问同问

2 个赞
6

还能这样啊，牛

1 个赞
7

用了没几下，就切换成flash了.

2 个赞
8

之前测试，大概用十几次就切换了 flash 了。

2 个赞
9

可以的喵~

10

试试这个？gemini -m "gemini-2.5-pro"

1 个赞
11

这个可以吗？

gemini -m "gemini-2.5-pro"
12

但是Gemini Cli用没几下就切成2.5flash了，也不知道具体是怎么个计数法

2 个赞
13

抓个虫，使用 google 账号登录 :rofl:

2 个赞
14

这个会不会不切？gemini -m "gemini-2.5-pro"

15

gemini code根本就是免费用，不需要api站

16

还是会切的，我试过，而且就算你把源码改了强制它不切换，它到达限制后直接不让用 :rofl:，但是不清楚限制是什么

17

感谢大佬！

1 个赞
18

据说2.5pro的限制很小喵~
然后模型计数是一起的 所以好像用0605会好些的喵(瘫

似乎是这样的喵~ 反代可以用很多次0605的(

1 个赞
19

限制不住的，哈基米自动给你切模型的

20

我是直接报错了老板

Error reading lifetime Google Accounts: TypeError: Cannot read properties of undefined (reading 'length')
    at getLifetimeGoogleAccounts (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/utils/user_account.js:74:34)
    at ClearcutLogger.createLogEvent (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/telemetry/clearcut-logger/clearcut-logger.js:59:31)
    at ClearcutLogger.logStartSessionEvent (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/telemetry/clearcut-logger/clearcut-logger.js:255:35)
    at new Config (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/config/config.js:218:47)
    at loadCliConfig (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/dist/src/config/config.js:263:12)
    at async main (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/dist/src/gemini.js:113:20)
Attempt 1 failed. Retrying with backoff... TypeError: Invalid URL
    at new URL (node:internal/url:826:25)
    at new HttpsProxyAgent (E:\New Folder\node-globall\node_modules\@google\gemini-cli\node_modules\https-proxy-agent\dist\index.js:65:50)
    at ClearcutLogger.getProxyAgent (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/telemetry/clearcut-logger/clearcut-logger.js:519:20)
    at file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/telemetry/clearcut-logger/clearcut-logger.js:114:29
    at new Promise (<anonymous>)
    at flushFn (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/telemetry/clearcut-logger/clearcut-logger.js:96:31)
    at retryWithBackoff (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/utils/retry.js:62:26)
    at ClearcutLogger.flushToClearcut (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/telemetry/clearcut-logger/clearcut-logger.js:130:42)
    at ClearcutLogger.logStartSessionEvent (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/telemetry/clearcut-logger/clearcut-logger.js:256:14)
    at new Config (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/config/config.js:218:47) {
  code: 'ERR_INVALID_URL',
  input: 'http://127.0.0.1:{port}'
}
An unexpected critical error occurred:
TypeError: Invalid URL
    at new URL (node:internal/url:826:25)
    at #getUrl (E:\New Folder\node-globall\node_modules\@google\gemini-cli\node_modules\undici\lib\dispatcher\proxy-agent.js:216:14)
    at new ProxyAgent (E:\New Folder\node-globall\node_modules\@google\gemini-cli\node_modules\undici\lib\dispatcher\proxy-agent.js:108:29)
    at new WebFetchTool (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/tools/web-fetch.js:42:33)
    at registerCoreTool (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/config/config.js:506:39)
    at Config.createToolRegistry (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/config/config.js:515:9)
    at Config.initialize (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/node_modules/@google/gemini-cli-core/dist/src/config/config.js:231:40)
    at main (file:///E:/New%20Folder/node-globall/node_modules/@google/gemini-cli/dist/src/gemini.js:133:18)
PS C:\Users\Warm Li\Desktop\cc-p4>
1 个赞