Tejus connects to Cursor's terminal agent, Cursor Agent, rather than embedding the Cursor editor. It runs cursor-agent acp and talks to it over the Agent Client Protocol (ACP). Cursor owns the account, model access, and agent service; Tejus provides the surrounding task, working directory, transcript, approvals, Git review, and delivery workflow.

Install

Install Cursor Agent with Cursor's official Windows installer from PowerShell:

irm 'https://cursor.com/install?win32=true' | iex

Tejus looks for the cursor-agent executable on PATH. If it is not there, Tejus also checks the installer's folder, %LOCALAPPDATA%\cursor-agent\. Verify the installation from a new PowerShell window:

cursor-agent --version

Authenticate

Browser-based sign-in is the recommended flow. In Tejus, open Settings → Agent providers, expand Cursor under Provider tools, and click Sign in; Tejus runs cursor-agent login in a terminal window. Or run it yourself:

cursor-agent login

Check the current state with:

cursor-agent status

Cursor Agent can also use CURSOR_API_KEY. Keep the key in a Windows user environment variable or in the provider's Environment section in Provider tools (with the secret switch on), never in project files, documentation, or prompts.

Verify

From a new PowerShell window:

cursor-agent --version
cursor-agent status
cursor-agent models

Then start Cursor Agent in a disposable repository:

cd C:\path\to\test-repository
cursor-agent

Ask a harmless read-only question. This verifies the executable, account, model service, and repository access before Tejus is involved.

Connect to Tejus

Enable Cursor

Open Settings → Agent providers and confirm that Cursor is enabled under Provider activity. Click Refresh status after installing or signing in.

Confirm the executable

Tejus prefers cursor-agent. The Cursor binary path field also accepts the cursor editor command-line launcher; Tejus then uses the Cursor Agent installed next to it. Leave the field blank to use cursor-agent from your PATH.

Check provider status

Tejus runs cursor-agent status and cursor-agent models without opening a browser. A ready status means the account is signed in and at least one model is available.

Start a bounded task

Use a clean test repository and review the selected model, permissions, and environment before sending the first objective.

The optional Cursor API endpoint field passes a different Cursor API endpoint to cursor-agent -e. Leave it blank unless your organization tells you otherwise.

Capabilities in Tejus

Cursor sessions can expose:

Cursor's available models, with effort and other options where Cursor reports them
Model changes inside a running session
Plan, Ask, and Agent modes
Tool calls, terminal commands, and file changes
Approval and permission events supported by the runtime
Subagent runs started by Cursor's Task tool
Cursor usage limits where Tejus can read them
Task-level Git, terminal, browser, diff, and pull-request workflows

Tejus does not support live steering of a running Cursor turn. Use the controls shown in the active task rather than assuming a follow-up can always be injected into a turn that is still running.

Cursor's own rules, MCP configuration, permissions, and account settings remain provider-owned and can change session behavior.

Follow subagent work

Cursor Task tool calls appear as subagent runs in the transcript, with their running and completed states. A subagent card reports delegated activity; review the parent task's result and actual checks before treating the overall objective as complete.

Updating

Cursor Agent tries to update itself. You can also update it explicitly:

cursor-agent update

Cursor manages its own releases, so Tejus cannot tell whether a newer version exists. Expand Cursor under Settings → Agent providers → Provider tools and use Update to run cursor-agent update for you. Restart Tejus after replacing the executable.

Troubleshooting

Cursor is not detected

Tejus shows “Cursor Agent CLI (cursor-agent) is not installed or not on PATH.”

Run cursor-agent --version from a new PowerShell window.
Confirm the installer folder (%LOCALAPPDATA%\cursor-agent) exists or that cursor-agent is on PATH.
Check that Tejus is not pointing at an old custom path.
Restart Tejus after installation or PATH changes.

Cursor is detected but not authenticated

Tejus shows “Cursor Agent is not authenticated. Run cursor-agent login and try again.” Use Sign in in Settings → Agent providers, or run cursor-agent status and then cursor-agent login. For API-key sign-in, confirm that CURSOR_API_KEY reaches Tejus (restart Tejus after setting a Windows variable).

Cursor