Add Cursor CLI support with separate Docker image

[thepagent]

Summary

Add a separate Docker image for Cursor CLI as an agent backend.

Approach

• Separate Dockerfile (Dockerfile.cursor)
• Publish as ghcr.io/thepagent/agent-broker-cursor
• Install: curl https://cursor.com/install -fsS | bash
• Auth: Cursor account login (needs investigation — may require API key or headless auth)
• Note: Cursor CLI ACP support needs to be verified

Helm usage

image:
  repository: ghcr.io/thepagent/agent-broker-cursor
agent:
  command: cursor
  args: ["--acp"]

Open questions

• Does Cursor CLI support ACP (Agent Client Protocol) over stdio?
• What auth mechanism works in headless/container environments? (Cursor has a headless mode)

Related: #14, #15, #16

[thepagent]

Update: Confirmed native ACP

Per OpenClaw's acpx registry, Cursor CLI has native ACP support via cursor-agent:

agent:
  command: cursor-agent
  args: ["acp"]

Note: The command is cursor-agent acp, not cursor --acp.

Reference

• OpenClaw acpx built-in agent commands

[chaodu-agent]

Before we invest in a Cursor image, could you clarify the use case?

1. Who would use this? Are there users currently running Cursor CLI that want to connect it to Discord via OpenAB?
2. Has anyone verified Cursor CLI supports ACP over stdio? The open questions in this issue are still unanswered.
3. What does Cursor offer that the existing backends (Kiro, Claude Code, Codex, Gemini) don't?

Without a concrete use case or confirmed ACP compatibility, this is hard to prioritize.

[CHC-Agent]

Issue at a Glance

Discord User ──► openab ──► Cursor CLI (ACP)
                               cursor-agent acp

Hi @thepagent,

ACP support confirmed — cursor-agent acp is the correct invocation. However, no one has validated the full stdio JSON-RPC flow with OpenAB yet, and there's no PR in progress.

Downgrading to p3 until the open questions from @chaodu-agent are addressed (target user, end-to-end validation). If someone can confirm it works with OpenAB, happy to bump priority back up.