Skip to content

Appendix

Cheatsheet · Cursor

Structural reference, not a tutorial — dense, lookup-first. Cursor is IDE-first, CLI- second — some of this course's loop mechanics map less directly…

Structural reference, not a tutorial — dense, lookup-first. Cursor is IDE-first, CLI- second — some of this course's loop mechanics map less directly here than onto a terminal-native tool. Confirm against the live docs when something here feels stale.

Entry points

SurfaceDoes
Cursor IDE — Agent/Composer modein-editor agentic session, tightly integrated with the file tree and diff view
cursor-agent (CLI)headless invocation outside the IDE — the primitive to wrap for a loop
Background Agentscloud-run agent sessions kicked off from the IDE, closer in shape to this course's Routines than to a local /loop

Config file shapes

FileRole
.cursor/rules/*.mdc (or legacy .cursorrules)the rules file — context layer, scoped rules per glob pattern
.cursor/mcp.jsonMCP server declarations
workspace settingsmodel choice, agent permissions, per-project

The loop primitives

MechanismShape
A capped shell wrapper around cursor-agentconditional/run-until-done, same pattern as the terminal-native tools
Background Agents on a schedule/triggerclosest built-in match to a Routine — verify current scheduling support before relying on it
CI calling cursor-agent headlesslythe unattended-schedule shape

Permissions & harness guarantees

DirectiveEffect
Agent mode's file-write scopewhich directories/files the agent may touch without per-edit confirmation
Command-execution approvalwhether shell commands run automatically or need a click — the IDE's version of the autonomy ladder
.cursor/rules glob scopingrules apply only within matched paths — a context-layer tool, not a harness guarantee on its own

Gotchas

  • .cursor/rules files are context, exactly like CLAUDE.md — a rule that says "never touch legacy/" there is a request; enforce it via the agent's actual write scope/permissions instead.
  • Background Agents run unattended by design — treat your first one exactly like this course treats a first Routine: narrow scope, notifications on, a tested kill switch, before you trust it overnight.
  • IDE-integrated diff review is a strong human gate mechanism — use it deliberately as the review step in your loop design, not as an incidental side effect of using the IDE.

Sources: this cheatsheet is original reference material for this course, written per the attribution policy's rule that tool mechanics are framed as pointers to live documentation rather than authoritative references. Live reference: docs.cursor.com. Cross-referenced against this course's tool-agnostic rules in safety.md. Full attribution: resources/sources.md.