这种方式很慢，每次需要大概一分钟以上。

[Barry04]

这种方式很慢，每次需要大概一分钟以上。

[anyrobert]

Hi @Barry04 — thanks for reporting the slow response time.

To help us pinpoint where the ~60s+ is spent (CLI spawn vs model catalog vs inference vs ACP/tools vs proxy overhead), we added a benchmark script to the repo. Could you run it and paste the full terminal output here?

Steps

1. Make sure you have a recent clone of this repo and the Cursor CLI is installed and logged in (agent login or CURSOR_API_KEY set).
2. From the repo root:

npm install
npm run build
node examples/benchmark-latency.mjs

Optional (if auto model hits usage limits or you want a lighter model):

BENCH_MODEL=composer-2.5 node examples/benchmark-latency.mjs

The script prints timings for:

• CLI spawn / --list-models
• Direct CLI completion
• Direct ACP (no proxy)
• Proxy sync + stream (if you have the proxy running)
• Ephemeral ACP proxy + client-tool round-trip

That breakdown will show whether the delay is mostly startup, inference, ACP, or tool passthrough — or something specific to your setup.

Also helpful if you can mention:

• OS and Node version
• Whether you use CURSOR_BRIDGE_USE_ACP=true
• Whether requests include tools / tool loops
• Sync vs stream: true

---

Language: This project’s issues are maintained in English so maintainers and other users can follow along. Would you mind replying in English on this thread (and opening future issues in English)? Thanks!

We’ll dig in once we have your benchmark output.

[anyrobert]

Quick follow-up: the benchmark script is now on main.

Pull latest and run:

git pull
npm install
npm run build
node examples/benchmark-latency.mjs

File: examples/benchmark-latency.mjs

Paste the full output when you can — that will show us where the latency gap is on your machine.