Cursor

Home Tools Platforms Cursor

A coding environment that connects agent context, local tools, rules, extensions, and prepared cloud development.

Coding & development · Documented · Documentation checked 2026-10-04

Cursor editor agents and Cloud Agents; Grok Bot has a separate shared-computer boundary.

Installed client, subscription, organization settings, repository access, and cloud environment determine capabilities.

What the platform is for

Cursor helps an agent work through a coding task inside an inspectable development loop. The central components are instructions, tools, and a model. Begin with a sample repository and a concrete failure, then evaluate changed files and real checks rather than the fluency of the explanation.

Know the product boundary

Local Agent, Projects coordination, Cloud Agents, and Grok Bot differ. Cloud tasks run in prepared VMs with source-control access; the local editor uses its own workspace. Bot’s shared computer has a separate authority model. Not every customization applies to every Cursor feature.

How the components connect

Rules and AGENTS.md provide deliberate guidance. Tools search, edit, run commands, or reach external services. Permissions and approvals shape authority. Cloud setup supplies reproducible dependencies. Checkpoints offer limited agent-file recovery; Git and external-service recovery remain separate.

A beginner starting point

Learn Agent context and the diff first. Add a focused project rule, then inspect command and MCP boundaries. Use a prepared cloud environment for a scoped task only after a known check can run there. Keep a human-controlled review and merge path.

Limits and data choices

Workspace edits can trigger code execution through live reload. Command allowlists and classifiers are best-effort, not hard security isolation. Checkpoints are not durable version control. This edition does not cover every Tab / inline-edit behavior, Bugbot configuration, SDK, or cloud automation in depth.

The technical path

Follow current Cursor Docs for extensions, Cloud Agents, environments, integrations, and SDKs. Review account-managed controls and source-provider rights separately. A cloud branch is a handoff; deployment still needs the project’s own authorized process.

Feature map

Agent, codebase context, and checkpoints

Connect instructions, a model, and tools into a local development loop you can inspect.

Explore Agent, codebase context, and checkpoints

Rules and AGENTS.md

Scope reusable project guidance and inspect when it applies.

Explore Rules and AGENTS.md

Plugins, MCP, and permission boundaries

Evaluate external tools and command approvals before extending an agent.

Explore Plugins, MCP, and permission boundaries

Cloud Agents and development environments

Prepare a remote repository workspace and review changes before merging.

Explore Cloud Agents and development environments

Review, recovery, and operational limits

Use diffs, checks, and checkpoints as complementary evidence rather than automatic acceptance.

Explore Review, recovery, and operational limits

Complete workflows

A local UI repair with deliberate recovery

Fix a sample UI problem while preserving unrelated work.

Explore A local UI repair with deliberate recovery

A cloud change with source and environment review

Run a scoped remote task and hand off tested branches or pull requests.

Explore A cloud change with source and environment review

Coverage and availability

Models, modes & conversation

Covered: Agent model / tool relationship; not every Tab or inline-edit mode covered.

Search, research & sources

Covered: Agent can use search; external context needs permissions.

Files, analysis & code

Covered: Local / cloud code work, terminal execution, and checks.

Images, video, audio & voice

Covered: Agent visual / browser capabilities vary; not a general media studio.

Projects, instructions & memory

Covered: Rules, AGENTS.md, and Projects context boundaries.

Editing surfaces & deliverables

Covered: Diffs, checkpoints, and Git; restoration scopes differ.

Agents, skills, plugins & MCP

Covered: Plugins, MCP, and tool permissions; Grok Bot is a separate boundary.

Orchestration & scheduling

Not established: Cloud environment and task handoff; full automation / Bugbot configuration deferred.

APIs, SDKs, deployment & evaluation

Separate product: SDK documentation is a technical path; production deployment is separate.

Sharing, privacy & governance

Covered: Workspace edits, command approvals, external accounts, and best-effort classifiers.

Plans, devices & accessibility

Not established: Account and source-control conditions noted; full billing / accessibility matrix not established.

Sources and verification

Documentation checked 2026-10-04. Examples are illustrative unless described otherwise.

Agent fundamentals and checkpoints · Cursor

Rules and AGENTS.md · Cursor

Agent security and approvals · Cursor

Cloud Agents and environments · Cursor

Share this page