《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》-Work with Grok Bot
Everything about working with Bots day to day: creating and managing them, messaging and collaborating, the computer they share, and turning finished work into skills and routines.
Read More《Cursor Docs》-Grok Bot use cases
The best Bot roles own a repeatable outcome, not a loose category of questions. Start each role with read and prepare work, review the result, and only then add approved actions or a routine.
Read More《Cursor Docs》-Grok Bot for Teams and Enterprise
Grok Bot gives each person on your team standing Bots for everyday work: research, operations, documents, browsing, and automations. This page is for team and organization admins rolling Grok Bot out. Security reviewers should start with Grok Bot security and the Grok Bot security FAQ. Members who want the approval model should start there too.
Read More《Cursor Docs》-Settings and notifications
Grok Bot settings cover app wide and desktop local behavior. Each Bot's profile and notification preference live in its conversation details. Open settings from the account menu or with Cmd+,.
Read More《Cursor Docs》-Grok Bot security FAQ
These are the questions security reviews ask most often. The controls behind each answer are on Grok Bot security. Dashboard settings and rollout steps are on Grok Bot for Teams and Enterprise.
Read More《Cursor Docs》-Grok Bot security
Use these controls and deployment details to decide whether Grok Bot is allowed in, and to limit what Bots can access, change, and retain. Rollout steps and the dashboard settings list live on Grok Bot for Teams and Enterprise. Common review questions are on Grok Bot security FAQ.
Read More《Cursor Docs》-Configure TLS-inspecting proxies
The Grok Bot desktop app connects from each member's device to two places: Cursor's API at .cursor.sh for chat, sign in, and approvals, and the member's hosted computer at a nested . .cursorvm.com hostname for computer setup, screen, and shell. Secure web gateways that inspect TLS often let the first through and break the second. The desktop app then hangs or errors during computer setup; in some setups chat keeps working while the computer never connects. Zscaler is the most common example, and this page uses it for specifics; the same steps apply to any gateway that re signs TLS or buffers responses. This page is for the IT team that runs your gateway. The shared domain list and streaming tests live on Enterprise network configuration; this page covers what Grok Bot adds.
Read More《Cursor Docs》-Connect to private networks
Grok Bot computers run in Cursor's cloud and reach the internet through shared static egress IP addresses. If the systems your Bots need, such as internal APIs, source control, databases, or staging environments, live on a private network, you can connect by installing your organization's networking client on every team computer through Team Setup . Tailscale and Cloudflare Tunnel are common choices, and this page has a worked example for each. Other VPN, zero trust, or mesh clients that run on Linux follow the same pattern. Your services stay off the public internet, and access is governed by the access controls and identity provider you already use.
Read More《Cursor Docs》-Configure identity and access
This guide is for admins running Okta or Microsoft Entra ID. It covers giving people outside your engineering organization access to Grok Bot through your Cursor team, and letting members sign in to IdP provisioned apps from the Bot's computer. For the broader security model, see Grok Bot security.
Read More《Cursor Docs》-Get started with Grok Bot
This guide takes you from install to your first finished task. You'll set up the desktop app, create a Bot with a clear job, and review its work.
Read More《Cursor Docs》-Grok Bot
Grok Bot gives you Bots you can keep around: AI teammates with names, jobs, and context that compounds over time. Each Bot works on a persistent cloud computer with a browser, filesystem, and terminal, so tasks finish in your real tools instead of as chat drafts. Get started with your first Bot, or read how teams roll it out.
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