The agent scheduling is too slow

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m using a third - party API (mimo - v2.5 - pro), and the agent scheduling of Cursor is extremely slow, so I’m thinking of switching to CC. There are no problems when using CC.

Steps to Reproduce

use mimo and ask questions,the first response is too slow if compare cc

Expected Behavior

response quickly

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.2.16
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, this is expected behavior, not a bug.

Cursor Agent mode does multi-step work on every turn. It pulls context, searches your codebase, plans, runs tool calls, and often makes multiple model calls on top of the actual model API call. A direct CLI client like Claude Code usually sends one request, so time-to-first-token is naturally lower.

A few things to try if you want lower latency:

  • Use Ask mode for Q and A style questions. It has much less overhead than Agent.
  • Use Inline Edit with Cmd+K for targeted edits.
  • Keep Agent context small. Attach fewer files and use a smaller workspace.

For BYOK models, latency also depends on how the third-party endpoint performs under heavier multi-tool-call workloads, which is more work than a single chat turn.

If you’re seeing something more specific than general orchestration overhead, like long stalls before any output or specific errors, share a Request ID and we can take a closer look.

This must be a bug. The clade code won’t behave like this. I hope you can make improvements.