《Cursor Docs》-Linear
Use Cloud Agents directly from Linear by delegating issues to Cursor or mentioning @Cursor in comments.
Read More《Cursor Docs》-Jira
With Cursor's integration for Jira, you can use Cloud Agents to work on Jira work items by assigning them to Cursor or mentioning @Cursor in Jira.
Read More《Cursor Docs》-JetBrains
Use Cursor's AI agent in IntelliJ IDEA, PyCharm, WebStorm, and other JetBrains IDEs through the Agent Client Protocol (ACP).
Read More《Cursor Docs》-GitLab
The GitLab integration connects your repositories so you can use features like Cloud Agents and Bugbot.
Read More《Cursor Docs》-GitHub
The Cursor GitHub app connects your repositories so you can use features like Cloud Agents and Bugbot.
Read More《Cursor Docs》-Cursor Blame
Understanding how AI contributed to your codebase helps with review, compliance, and debugging. This page covers how Cursor Blame surfaces AI versus human authorship in git history.
Read More《Cursor Docs》-Bitbucket
Connect Bitbucket Cloud repositories to Cloud Agents and Bugbot. Connect Bitbucket Data Center repositories to Bugbot.
Read More《Cursor Docs》-Azure DevOps
The Azure DevOps integration connects Azure DevOps Services repositories to Cloud Agents and Bugbot.
Read More《Cursor Docs》-Hooks
Hooks let you observe, control, and extend the agent loop using custom scripts. Define hooks in hooks.json files at the project or user level, or install them through plugins from Customize . Hooks are spawned processes that communicate over stdio using JSON in both directions. They run before or after defined stages of the agent loop and can observe, block, or modify behavior.
Read More《Cursor Docs》-Quickstart
This guide gets you from install to your first useful change in Cursor. You'll sign in, ask Cursor to explain your codebase, make a small edit, and review the result.
Read More《Cursor Docs》-Extension API reference
Cursor exposes extension APIs under vscode.cursor for programmatic configuration. Use these APIs from VS Code extensions to register MCP servers and plugin paths without editing config files.
Read More《Cursor Docs》-Run Cursor in your evals
Use the Cursor SDK to run Cursor's agent loop inside your own eval harness. The same agent that powers the Cursor IDE, CLI, and web app is scriptable from TypeScript, so you can score Grok 4.6 (and other models we support) on your benchmarks.
Read More《Cursor Docs》-Security and Privacy Hardening
This page consolidates the security and privacy guidance spread across the Cursor docs into one reference, so teams configuring Cursor can review and apply the right controls without hunting through every page. Each item links to its source doc for the full detail.
Read More《Cursor Docs》-Privacy and Data Governance
Understanding how data flows through Cursor is critical for security reviews and compliance assessments. This documentation explains what data goes where, what guarantees you have, and where that data lives geographically.
Read More《Cursor Docs》-Pooled usage
Pooled usage gives your Enterprise team a shared usage pool instead of fixed per user allocations. Everyone draws from a single committed amount that spans your contract period, so agent usage is available wherever it's needed most.
Read More《Cursor Docs》-Organizations
Organizations are the top level container for Enterprise customers. They sit above teams and give you one place to manage shared identity, administration, and organization wide settings.
Read More《Cursor Docs》-Organization Groups
Organization Groups are org level cohorts in Cursor Enterprise, such as Engineering, Contractors, or Pilot Users. Members can come from any team in your Organization, and a user can belong to many groups at once.
Read More《Cursor Docs》-OpenTelemetry Export Wire Reference
Companion to OpenTelemetry Export. Full wire surface: every metric, log event, attribute, enum, and presence rule.
Read More《Cursor Docs》-OpenTelemetry Export
OpenTelemetry Export streams Cursor usage data for your team to a collector you run. Cursor sends metrics (tokens, tool calls, best effort cost) and logs (API requests, errors, corrections, skills, hooks, plugins, and cloud agent lifecycle events) to one team managed destination. Export runs server side.
Read More《Cursor Docs》-Network Configuration
Cursor needs to communicate with backend services and AI providers. This documentation covers how to configure Cursor to work within your network infrastructure, including proxies, firewalls, and encryption requirements.
Read More《Cursor Docs》-Model and Integration Management
Your team can access multiple AI models and integrate Cursor with various services. This documentation covers how to control which models are available, manage MCP server trust, and set up integrations with tools like Slack, GitHub, and Linear.
Read More《Cursor Docs》-LLM Safety and Controls
AI models can behave unexpectedly. This documentation covers how to control what agents can do, set up safety guardrails, and guide LLM behavior toward desired outcomes.
Read More《Cursor Docs》-Identity and Access Management
Identity and access management controls who can use Cursor in your organization and what they can do. You'll set up authentication, automate user provisioning, and enforce policies through device management.
Read More《Cursor Docs》-Endpoint Security Configuration
Cursor loads JavaScript modules and performs file I/O during startup. Endpoint security software that intercepts file operations or injects into processes can slow startup past internal timeouts, causing features like Agent to fail. This page covers how to configure exclusions so Cursor works alongside your security stack.
Read More《Cursor Docs》-Deployment Patterns
This guide covers how to deploy the Cursor editor and CLI tools to developer machines in your organization. Most organizations deploy both the editor (for daily development work) and the CLI (for automation, CI/CD, and scripting).
Read More