/code @devintern/pm DevIntern + Cursor
Use the Cursor agent as your implementation and planning backend. DevIntern invokes it headlessly with -p so ticket runs complete without an IDE session open.
How it works
What DevIntern does with Cursor
Each product path keeps Cursor as the handoff surface. No rip-and-replace, no new dashboard.
/code Implement with Cursor agent
- 1 Install the Cursor CLI and set AGENT_HARNESS=cursor.
- 2 DevIntern runs cursor-agent -p with task context and permission flags.
- 3 Changes commit locally; --create-pr opens a draft on your repo host.
/pm Draft specs with Cursor agent
- 1 PM interactive mode uses the same Cursor harness.
- 2 Generate a spec from rough input grounded in your repo.
- 3 Review and file to your tracker.
Capabilities
Built for real Cursor workflows
Headless Cursor agent via -p (print mode)
Optional --force, --trust, and --approve-mcps for unattended runs
Model override through harness configuration
Works with every supported task tracker on the Code side
Same self-hosted security model as other harnesses
Get connected
Setup guides and configuration
Credentials stay in project-local .env files. DevIntern runs on your machine or server, not a shared implementation cloud.
FAQ
Common questions about Cursor
Do I need Cursor IDE open?
No. DevIntern uses the Cursor CLI in non-interactive mode. Runs complete from the terminal or a server cron/systemd job.
How is Cursor different from Claude Code in DevIntern?
Only the harness changes. Set AGENT_HARNESS=cursor and configure Cursor CLI auth. Trackers, repos, and PR flows stay identical.
Does --max-turns apply to Cursor CLI?
No. The turn limit is passed to harnesses that support it; Cursor's headless CLI ignores it, so bound long runs with your ticket scope instead.
Can Cursor CLI run in a sandbox?
Yes. Docker Sandboxes support the cursor harness. With AGENT_SANDBOX=auto the worker picks an available sandbox backend for you.
Can I fail over between Cursor and another agent?
Yes. List harnesses in order, for example AGENT_HARNESS=opencode,cursor, and the worker falls back to the next one when the first is unavailable or rate limited.
Try DevIntern with Cursor
Connect Cursor, run your first workflow, and keep the trackers, repos, and reviewers your team already trusts.
Free for interactive use · FSL source-available · BYO model keys