Using Cursor with T3 Code
Connect the Cursor agent CLI to T3 Code, understand the difference between cursor-agent and the Cursor IDE, and see whether it's worth using outside the editor.
Cursor support in T3 Code runs through cursor-agent, the CLI — not the Cursor editor. Getting that distinction right saves confusion.
Setup#
cursor-agent loginThen start T3 Code and pick Cursor as your provider:
npx t3@latestThe cursor-agent CLI ships with Cursor. If the command isn't found, check your Cursor installation and make sure the CLI is on your PATH.
cursor-agent is not the Cursor IDE#
| Cursor IDE | cursor-agent CLI | |
|---|---|---|
| Form | Full VS Code-based editor | Command-line agent |
| Used by T3 Code | No | Yes |
| Interface | Its own | T3 Code's |
| Editing files by hand | Yes | Not its job |
T3 Code doesn't embed or replace the Cursor editor. It drives the same agent from a different front end. If what you want is Cursor's inline completions and editor experience, keep using Cursor — they solve different problems. Full comparison →
Why use Cursor's agent outside Cursor#
Three reasons people actually do this:
- Parallel agents. Worktree-per-thread gives you three Cursor agents on three branches, which the editor doesn't offer as a first-class workflow.
- One interface for several agents. Cursor for one task, Codex for another, in the same window, with the same git flow around both.
- Remote and mobile. Pair a phone or laptop to a server and check on runs from anywhere. The editor is tied to the machine it's installed on.
If none of those apply, staying in Cursor is a perfectly good answer. The honest case for T3 Code here is workflow, not capability.
Billing#
Your Cursor subscription. T3 Code adds no fee and holds no key — cursor-agent is authenticated independently and usage counts against your Cursor account.
Troubleshooting#
cursor-agentnot found — either the CLI isn't installed with your Cursor build, or it isn't on the PATH that T3 Code inherited. PATH fixes →- Auth failures — run
cursor-agent loginagain; sessions expire - Sessions won't start — update Cursor and the agent CLI. Version skew between an agent CLI and T3 Code is the usual cause across every provider
FAQ#
Does T3 Code support Cursor?#
Yes, through the cursor-agent CLI. Authenticate with cursor-agent login and select Cursor as your provider in T3 Code.
Is T3 Code a replacement for Cursor?#
No. Cursor is a full editor with inline completions; T3 Code is a GUI for running coding agents. Many people use both — Cursor for hands-on editing, T3 Code for delegating longer tasks to parallel agents.
Do I need a Cursor subscription to use Cursor in T3 Code?#
Yes. T3 Code uses your authenticated cursor-agent session, so usage counts against your Cursor account. T3 Code itself is free.
Can I run Cursor and Codex agents at the same time in T3 Code?#
Yes. Authenticate both CLIs and run them in separate threads, each with its own git worktree.