Skip to content
Glade
Esc
↑↓navigate↵open⌘Jpreview
On this page
llms.txt

Cursor

Run the Cursor CLI agent in Glade with your Cursor account. What it needs, how to sign in, and what works.

Glade runs your installed Cursor CLI (cursor-agent) with the account it’s signed in to.

Requirement Value
Minimum version 2026.1.0
Install Cursor CLI installation
Sign in cursor-agent login

Set up

Install the Cursor CLI

Follow Cursor’s guide, then check that cursor-agent runs in a fresh terminal.

Sign in

Run cursor-agent login.

Pick a model

The model picker lists every Cursor model with its own effort, thinking, fast and context settings.

What works

  • Chats, tools, approvals and slash commands, the same way as Grok Build and OpenCode.
  • Forks copy the chat up to the reply into a fresh session.
  • /compact has the agent write a summary and continues in a fresh session.
  • Usage shows the billing cycle and on-demand spend, read from your Cursor sign-in.

Good to know

  • Cursor reports no context or token usage, so there’s no context meter. Run /compact when a chat gets long.
  • Messages sent mid-turn wait for the turn to finish.
  • Every model switch becomes Cursor’s CLI default.
  • Cursor can’t delete a session, so a deleted chat’s history stays in Cursor’s own storage.

Under the hood

Glade talks to Cursor over the Agent Client Protocol, on the adapter it shares with Grok Build and OpenCode. Glade’s tools and your MCP servers reach it as HTTP MCP servers.