Agents

cursor-agent

Run Cursor CLI on a canvas.

Run the Cursor agent outside the editor: several cursor-agent sessions in real terminals on one canvas, on your own Cursor plan, with its usage in the rail.

v1.0.4 · Apple silicon · free for 3 days · no account

The Starkomand canvas with several agent windows, a hand-drawn diagram beside one of them and a browser preview beside another.

What Cursor CLI gets on the canvas.

How Starkomand launches Cursor CLI and what it can show you about each window.

Launches as cursor-agent
Canvas tools One starkomand-canvas entry in ~/.cursor/mcp.jsonCursor has no launch-scoped MCP flag, so a global entry routes by window.
Canvas instructions MCP server instructions only
Window’s back Request and turn state onlyThe CLI does not report tool steps to Starkomand.
Usage Plan usage ring in the railOpt in under Settings → Usage meters.
Expired sign-in Restart other windows with ⟳ after signing inCursor cannot resume one session out of several, so Starkomand never resets a window for you.

Same for every agent. A real terminal signed in as you, diagrams and browser previews beside the window, issue notes you drop onto it, handoffs with a brief to any other agent, a spoken “done” when a turn ends, and persistent windows through Herdr.

Read from Starkomand’s launch code on 28 September 2026. Product names belong to their owners; Starkomand is not affiliated with them. Spotted a change? Tell us.

Set up in a minute.

  1. Install Cursor CLI

    Follow the Cursor CLI guide. Starkomand finds cursor-agent on your PATH.

  2. Sign in once

    Run cursor-agent login.

  3. Open it on the canvas

    ⌘-click the canvas and pick Cursor CLI. Every window you open after that starts signed in.

Worth knowing.

  • Cursor has no flag for adding to its system prompt, so the canvas instructions arrive with the MCP server.

Questions.

Can I run multiple Cursor CLI sessions at once?

Yes. Each window runs its own cursor-agent in a real terminal, so open as many as your plan allows, side by side or in separate workspaces, next to any other agent.

Does Starkomand change my Cursor CLI configuration?

One namespaced starkomand-canvas entry in ~/.cursor/mcp.json, merged atomically with a one-time backup. An entry of your own under that name is left alone.

Do I need an API key for Cursor CLI?

Starkomand never asks for one. Run cursor-agent login. Your plan and usage stay with the provider; Starkomand does not resell tokens.

Bring the agents you already pay for.

Every agent, every feature, free for 3 days. Your CLIs are already installed; the canvas takes a minute.

v1.0.4 · Apple silicon · no account