# Billing Source: https://docs.cursor.com/account/billing Complete guide to managing Cursor billing: subscriptions, refunds, cycles and access through Stripe portal We use Stripe as our billing and payments provider ### How do I access billing settings? The billing portal is where you'll manage all aspects of your subscription. You can access it through the [dashboard](https://cursor.com/settings) by clicking the "Billing" button in your account settings. This takes you to a secure portal where you can handle all billing-related tasks. ### What are Cursor's billing cycles? Billing cycles run on either a monthly or annual basis, starting on the day you subscribe. For Business accounts with multiple seats, we use prorated billing when your team size changes. This means you only pay for the actual time each seat is used within a billing cycle. ### How do team seats work for Business accounts? Business accounts use a per-seat billing model where each team member requires one seat license. When adding new members mid-cycle, you're only charged for their remaining time in that billing period. Team admins can manage seats directly through the dashboard. ### Can I switch between monthly and annual billing? Yes you can! Here's how: **Pro plan** 1. Go to [settings](https://cursor.com/settings) 2. Click on "Manage subscription" and you will be taken to the billing portal 3. Click on "Update subscription" 4. From here you can switch between monthly and annual billing 5. Select "Yearly" or "Monthly", then click on "Continue" **Business plan** 1. Go to [settings](https://cursor.com/settings) 2. In the account section, click on "Advanced" then "Upgrade to yearly billing" Please note that you can only switch from monthly to yearly billing self-serve. To switch from yearly to monthly billing, please contact us at [hi@cursor.com](mailto:hi@cursor.com). ### Where can I find my invoices? All your billing history is available in the billing portal, where you can view and download both current and past invoices. ### Can I get invoices automatically emailed to me? Currently, invoices need to be downloaded manually from the billing portal. We know this is a hassle, so we're developing automatic invoice emails as a new feature, and once available, you'll be able to opt-in! ### How do I update my billing information? You can update your payment method, company name, address, and tax information through the billing portal. We use Stripe as our payment processor to ensure secure transactions. Please note that changes to billing information will only affect future invoices - we cannot modify historical invoices. ### How do I cancel my subscription? You can cancel your subscription directly through the billing portal using the "Cancel subscription" button. Your access will continue until the end of your current billing period. ### I'm having other billing issues. How can I get help? For any billing-related questions not covered here, please email us at [hi@cursor.com](mailto:hi@cursor.com). Include your account details and specific concerns, and our team will help you resolve them quickly! ### Can I get a refund? You can self-serve a refund by going to the billing portal and clicking on the `Cancel subscription` button. Our self-serve refund policy is as follows: **EU, UK or Turkey customers** * Eligible for a refund if you cancel your subscription within 14 days of purchase. **All other customers (US + rest of world)** * Monthly subscriptions: Refundable within 24 hours after purchase. * Annual subscriptions: Refundable within 72 hours after purchase If you're not in the window of self-serve refunds, reach out to us at [hi@cursor.com](mailto:hi@cursor.com) and we'll help you! # Dashboard Source: https://docs.cursor.com/account/dashboard Learn how to manage billing, usage pricing, and team settings in the dashboard for different plans You can view the Cursor dashboard by going to [cursor.com/settings](https://cursor.com/settings) From the dashboard you can access billing portal, setup usage based pricing and manage your team. Depending on if you're on Free, Pro or Business, you'll see different sections. ## Pro From here you can access billing portal, setup usage based pricing and see how many requests you have left. ## Business Business will have a section for teams. ### Team Read more about how to manage teams in [members](/account/teams/members) ### Metrics Read more in [team analytics](/account/teams/analytics). This is only available for teams ### Usage based pricing This is where you can toggle usage based pricing and set spending limits. Read more about [usage based pricing](/account/plans-and-usage) and how to configure it # Plans & Usage Source: https://docs.cursor.com/account/plans-and-usage Guide to Cursor usage tiers, request types, quotas, and billing options for premium models and team accounts To view your current usage, you can visit the dashboard at [cursor.com/settings](https://cursor.com/settings) ## Available Plans
  • 14 days Pro Trial
  • 150 `premium` model uses
  • Unlimited [completions](/tab/overview)
For costs and more pricing info, please visit the [Cursor Pricing](https://cursor.com/pricing) page. ## Understanding Usage ### Fast and Slow Requests There are two types of requests in Cursor, **slow** and **fast** that has its own pool. By default, Cursor servers try to give all users fast `premium` model requests. However, when users run out of fast `premium` credits, they are moved to a slow pool. Wait times in the slow pool are calculated proportionally to how many slow requests you've used, so they generally remain manageable unless you're well over your fast request limit. To bypass wait times entirely, you can enable usage-based pricing (you'll only be charged for requests beyond your included fast requests). See [models](/settings/models) for an overview of which models are `premium` and their alternatives. ### Included Requests Every subscription includes a set amount of fast requests. The number of included requests depends on your plan as shown in the plan comparison above. ### Additional Requests We offer usage-based pricing for additional requests beyond your plan's included quota: #### Usage-based Pricing You may opt in to usage-based pricing for requests that go beyond what is included in your Pro or Business plan from your [dashboard](/account/dashboard). Usage-based pricing is only available with a paid subscription. From the dashboard, you can toggle usage based pricing for `premium` models and `other` models (see [models](/settings/models) to understand which model is which). You can also configure a spend limit in USD to make sure you never go over that. Once the spending limit is hit, slow requests will be used. We will bill for additional fast requests when you've made requests totaling \$20, **or** on the 2nd or 3rd day of the month, whichever comes first. 375 fast requests made with a `premium` model (\$15) will be billed at the beginning of the next month since the total value is under \$20

1150 fast requests made with a `premium` (\$46) will be billed 3 times:

1. When first batch of 500 requests has been made (\$20)

2. When second batch of 500 requests has been made (also \$20)

3. Beginning of next month (remaining \$6)

For team accounts, administrators can restrict usage-based pricing settings to admin-only access. Cost per request for each model can be found on the [models](/settings/models) page. #### Fast Requests Packages Fast requests packages have been deprecated in favor of usage-based pricing. Existing users with additional packages can continue to use them and have the option to remove them, but new packages cannot be purchased. Fast Request Packages were bundles of 500 requests that could be purchased in addition to your plan's included quota. These have been replaced by usage-based pricing for fast requests, as purchasing them in bundles often meant users would pay for requests they didn't use. ### FAQ #### When do my fast requests reset? Your Fast Requests reset on a fixed monthly date based on when you first set up your plan. If you purchase additional requests (for example, upgrading from 500 to 1000 requests), the reset date remains unchanged. For instance, if your plan started on the 23rd, your requests will always reset on the 23rd of each month, regardless of when you purchase additional requests. #### What does "500 premium requests" mean for teams? Each user gets their own quota of 500 fast requests for premium models per month. These requests are not pooled across the team - every team member gets their own fresh 500 requests when their personal monthly cycle resets. # Pricing Source: https://docs.cursor.com/account/pricing # Privacy & Security Source: https://docs.cursor.com/account/privacy Guide to Cursor's privacy settings, data handling, and code indexing with Privacy Mode option Cursor is built with privacy and security at its core. We have built Cursor from the ground up to give you the peace of mind that your code and data is private and secure. ## Quick Links To learn more about Cursor's privacy and security practices, please see the following links: Read our comprehensive privacy policy to understand how we handle your data Learn about our security practices and how we protect your code View our Trust Center to learn more about our security practices and to access our SOC2 certification. security reports and annual penetration testing reports. ## Privacy FAQs ### What is Privacy Mode? With `Privacy Mode` enabled, none of your code will ever be stored by us or any third-party. Otherwise, we may collect prompts, code snippets and telemetry data to improve Cursor. You can [read more about Privacy Mode here](https://cursor.com/privacy). Privacy mode is enforced for Business plans You can enable `Privacy Mode` at onboarding or under `Cursor Settings` > `General` > `Privacy Mode`. Privacy Mode ### Are requests always routed through the Cursor backend? Yes! Even if you use your API key, your requests will still go through our backend. That's where we do our final prompt building. ### Does indexing the codebase require storing code? It does not! If you choose to index your codebase, Cursor will upload your codebase in small chunks to our server to compute embeddings, but all plaintext code ceases to exist after the life of the request. The embeddings and metadata about your codebase (hashes, obfuscated file names) are stored in our database, but none of your code is. You can read more about this on our [security page](https://cursor.com/security). # Analytics Source: https://docs.cursor.com/account/teams/analytics Track team metrics including usage stats, per-user activity, and active user counts from the dashboard Team admins can track metrics for their team from the [dashboard](/account/dashboard). A new and upgraded metrics page is currently in development, including an API for programmatic data retrieval and will be available soon. The metrics dashboard shows usage statistics for your team over the last 30 days: ### Total Usage View aggregate metrics across your entire team, including total tabs and premium requests used. For teams less than 30 days old, metrics reflect actual usage since team creation, including activity from team members' individual accounts prior to joining. ### Per Active User See average usage metrics per active user, including tabs accepted, lines of code, and premium requests. ### User Activity Track both weekly and monthly active user counts. ## FAQ The difference in numbers you're seeing is because the team tab shows requests for the current billing period, while the metrics page shows a rolling 30-day window. We know is can be confusing - we're working on making this clearer in the dashboard. # Members + Roles Source: https://docs.cursor.com/account/teams/members Learn about team roles, member management, SSO options, usage controls and billing for organizational teams Within a Cursor team, you can have three different roles. **Click on a role below to learn more about it.** Standard team member with access to all Business features Full team management and security control capabilities Admin capabilities without using a paid seat ## Roles ### Member Members are the default role for team members with access to Cursor's Pro features. Full access to all **Pro features** including 500 premium requests and unlimited completions Each member uses **one billable seat** and counts towards the total renewal of your team each month / year Members have **no access** to the billing settings or the admin dashboard. ### Admins Admins have comprehensive control over team management and security settings to ensure smooth team operations. Full access to all **Pro features** as normal members Add and remove members, modify roles, and setup SSO Configure usage-based pricing and set spending limits for the team ### Unpaid Admin Unpaid Admins manage the team without using a paid seat - ideal for IT or finance staff, who don't need Cursor access. Unpaid Admins are **not billable**, and do not have any Pro features Add and remove members, modify roles, and setup SSO Configure usage-based pricing and set spending limits for the team Unpaid Admins are required to have at least one paid user on the team. ## Role Comparison
| Capability | Member | Admin | Unpaid Admin | | ---------------------- | :----: | :---: | :----------: | | Use Cursor features | ✓ | ✓ | | | Invite members | ✓ | ✓ | ✓ | | Remove members | | ✓ | ✓ | | Change user role | | ✓ | ✓ | | Admin dashboard | | ✓ | ✓ | | Configure SSO/Security | | ✓ | ✓ | | Manage Billing | | ✓ | ✓ | | Set usage controls | ✓ | ✓ | ✓ | | Requires paid seat | ✓ | ✓ | |
## Managing members All members in the team can invite other members. We currently do not have any way to control invites. ### Add member Members can be added in three ways: \- Click the `Invite Members` button
\- Enter email addresses
\- Users will receive an email invite to join the team
\- Click the `Invite Members` button
\- Copy the `Invite Link`
\- Share with team members
\- Configure SSO in the [admin dashboard](/account/teams/sso)
\- Users will be automatically added to the team when they login via their SSO-enabled email address
Invite links do not expire and anyone who gets access to the link can join a team.
You can prevent this by setting up [SSO](/account/teams/sso)
### Remove member Admins can remove members at any time by clicking the context menu and then "Remove". We'll only charge for time the member was in the team, and any pro-rated credit earned from removing a member mid-plan will be applied to your next invoice. ### Change role Admins can change roles for other members by clicking the context menu and then use the "Change role" option.
There must be at least one Admin, and one paid member on the team at all times. ## Security & SSO SAML 2.0 Single Sign-On (SSO) is available on Business and Enterprise plans. Key features: * Configure SSO connections ([learn more about SSO setup](/account/teams/sso)) * Set up domain verification * Automatic user enrollment through SSO * SSO enforcement options * Identity provider integration (Okta, etc) ## Usage Controls Access usage settings to: * Enable usage-based pricing * Enable for usage-based for premium models * Set admin-only modifications for usage-based pricing settings * Set monthly spending limits * Monitor team-wide usage ## Billing When adding new team members: * Each new member or admin adds a billable seat (see [pricing](https://cursor.com/pricing)) * Seat changes are prorated for your billing period * Unpaid admin seats are not counted When adding new team members in the middle of a month, we'll only charge you for the days they actually use. Similarly, if someone leaves the team, we'll credit your account for any unused days. If you change someone's role (e.g from Admin to Unpaid Admin), we'll automatically adjust the billing from the day of the change. You can choose to be billed either monthly or yearly - both options are available to suit your needs. Your monthly or yearly renewal will always occur on the same day as when you first signed up, regardless of additional or removed members. ### Switch to Yearly billing You can save **20%** of the Business plan by switching from monthly to yearly billing. This can be done from the [dashboard](/account/dashboard) 1. Go to [settings](https://cursor.com/settings) 2. In the account section, click on "Advanced" then "Upgrade to yearly billing" Please note that you can only switch from monthly to yearly billing via the dashboard. To switch from yearly to monthly billing, please contact us at [hi@cursor.com](mailto:hi@cursor.com). # Get Started Source: https://docs.cursor.com/account/teams/setup Guide to create and manage Cursor business teams with SSO, enterprise features, and MDM deployment options ## Cursor for Business Cursor was built with versatility in mind, and can be used from hobby projects to large scale enterprise applications. For the best experience, we have built a Business plan that enhances the Cursor application for teams! Alongside the Cursor application, we have built a suite of tools to help you manage your team, including SSO, team management, and more. ## Creating a Team To get started with Cursor for your team, you can create a team by following the steps below. To create a team, you need to be on the [Business plan](/account/plans-and-usage). To get started, you can choose one of the following options: If you are new to Cursor, click here to create a new account and team If you are already on a Pro plan, you can click the "Upgrade to Business" button in dashboard After clicking "New Team", enter the details for the team. You will have to select name and billing cycle for the team After the team is created, you can start inviting members to the team. All changes to users are prorated, meaning that we will only charge for the time that a user has been a member of the team After the team is created, you can enable [SSO](/account/teams/sso) for the team for additional security and easy onboarding for new members of your team. ## FAQ ### My team uses ZScalar / a proxy / a VPN, will Cursor work properly? Cursor uses HTTP/2 to provide the best experience, and unfortunately some proxies and VPNs block this. To resolve this, you can enable the HTTP/1.1 fallback in the app settings. This will force Cursor to use HTTP/1.1, which is not blocked by most proxies and VPNs. We hope to add automatic detection and fallback in the future! ### How can I purchase licenses for my company? Cursor is billed on a per-user basis, and does not have a fixed amount of seats. You can invite as many or as few users as you'd like to your team, and you will only be charged for the amount of users in your team. If you add or remove users from your team, the billing will be updated immediately, and you will either be charged or refunded accordingly. Refunds are done as account credit, so will be automatically applied to your next invoice. For simplicity, we keep your renewal date on the same day each month/year, and any mid-plan changes are prorated. ### How can I set up a team when I'm not going to use Cursor myself? As part of our business management tools, you can now set members of your team to be [Unpaid Admins](/account/teams/members). This allows members of your team to administrate the team and it's billing, without being charged for a Cursor license themselves. Business plan teams always require at least one paid member. However, invoices for team changes are not billed immediately, so you can set up a team, invite a member and change your own role without being charged. ### How can I add Cursor to my company's MDM? Use these permanent URLs that will always download the latest stable version of Cursor: Download for all Macs Download for all Macs Download for Intel Macs Download for Apple Silicon Macs Download for 64-bit Windows Download for ARM Windows Download for 64-bit Windows Download for ARM Windows Download for 64-bit Windows Download for ARM Windows Download for 64-bit Linux Download for ARM Linux Then follow the instructions for your MDM: formally VMware Windows application management macOS application management Kandji custom app deployment # SSO Source: https://docs.cursor.com/account/teams/sso Guide to setting up SAML 2.0 SSO authentication with your identity provider in Cursor for team accounts ## Overview SAML 2.0 Single Sign-On (SSO) is available at no additional cost on the Cursor Business plan. This enables you to use your existing identity provider (IdP) to authenticate your team members, avoiding the need for your team members to have a Cursor account, and remember another password. ## Prerequisites * A Cursor Business plan * Admin access to your identity provider (e.g., Okta) * Admin access to your Cursor organization ## Configuration Steps Navigate to [cursor.com/settings](http://cursor.com/settings) and sign in with an admin account. Find the "Configure SSO" button in the bottom left of the settings page Click the button to start the SSO setup process, and follow the setup wizard to configure your identity provider. In your identity provider (e.g., Okta): * Create a new SAML application * Configure the SAML settings using the information provided in Cursor * Set up Just-in-Time (JIT) provisioning for seamless user access ### Identity Provider Setup Guides For detailed setup instructions specific to your identity provider, refer to the guides below: Access comprehensive setup instructions for all major identity providers including Okta, Azure AD, Google Workspace, and more. SCIM provisioning coming H1 2025 ## Additional Settings * SSO enforcement is managed through the admin dashboard * New users are automatically enrolled in your organization when they sign in through SSO * User management can be handled directly through your identity provider ## Troubleshooting If you encounter issues during setup: * Verify your domain has been verified in Cursor * Ensure all required SAML attributes are properly mapped * Check that the SSO configuration is enabled in your admin dashboard * If a user is unable to authenticate, ensure the first and last name set in the identity provider matches their name in Cursor * Check the guides above for detailed setup instructions specific to your identity provider * If you continue to experience issues, please reach out to us at [hi@cursor.com](mailto:hi@cursor.com) # Notepads (Beta) Source: https://docs.cursor.com/beta/notepads A guide to using Notepads in Cursor for sharing context between Composers and Chat interactions Notepads are currently in beta and subject to be deprecated in the future. # Overview Notepads are powerful context-sharing tools in Cursor that bridge the gap between composers and chat interactions. Think of them as enhanced reference documents that go beyond the capabilities of `.cursorrules`, allowing you to create reusable contexts for your development workflow. Notepads serve as collections of thoughts, rules, and documentation that can be: * Shared between different parts of your development environment * Referenced using the `@` syntax * Enhanced with file attachments * Used as dynamic templates for various development scenarios ## Getting started 1. Click the "+" button in the Notepads section 2. Give your notepad a meaningful name 3. Add your content, context, files and other relevant information the same way you would in composer or chat. 4. Reference it in composers or chat using `@` # Key features * **Context Sharing**: Seamlessly share context between composers and chat * **File Attachments**: Attach documentation and reference files (not possible in `.cursorrules`) * **Dynamic References**: Use `@` mentions to link to other resources * **Flexible Content**: Write and structure information in a way that suits your needs # Common use cases 1. **Dynamic Boilerplate Generation** * Create templates for common code patterns * Store project-specific scaffolding rules * Maintain consistent code structure across your team 2. **Architecture Documentation** * Frontend specifications * Backend design patterns * Data model documentation * System architecture guidelines 3. **Development Guidelines** * Coding standards * Project-specific rules * Best practices * Team conventions ## FAQ ### What should I write in Notepads? Notepads are ideal for: * Project architecture decisions * Development guidelines and standards * Reusable code templates * Documentation that needs to be referenced frequently * Team-specific conventions and rules ### What should not be written in Notepads? Avoid using Notepads for: * Temporary notes or scratch work * Information that belongs in version control (like git) * Sensitive data or credentials * Highly volatile information that changes frequently ### Should I follow a particular format or structure? While Notepads are flexible, we recommend: * Using clear headings and sections * Including examples where relevant * Keeping content focused and organized * Using markdown formatting for better readability * Adding relevant file attachments when necessary ### Example Notepad Here's a typical example of a Notepad for a web application project: ```md Notepad example # API Development Guidelines ## Endpoint Structure - Use RESTful conventions - Base URL: `/api/v1` - Resource naming in plural form ## Authentication - JWT-based authentication - Token format: Bearer {token} - Refresh token mechanism required ## Response Format { "status": "success|error", "data": {}, "message": "Optional message" } ## Attached References @api-specs.yaml @auth-flow.md ``` # Agent Mode Source: https://docs.cursor.com/chat/agent Autonomous AI coding agent that independently explores, plans, and executes complex codebase changes with full tools Agent is the default and most autonomous mode in Cursor, designed to handle complex coding tasks with minimal guidance. It has all [tools](/chat/tools) enabled to autonomously explore your codebase, read documentation, browse the web, edit files, and run terminal commands to complete tasks efficiently. ## Agent's Capabilities Independently explores your codebase, identifies relevant files, and makes necessary changes Uses all available tools to search, edit, create files, and run terminal commands Builds a comprehensive understanding of your project structure and dependencies Breaks complex tasks into manageable steps and executes them in sequence Make sure to read [chat overview](/chat/overview) to learn more about how modes work in Cursor. ## Agent's Workflow Much like a human, Agent mode follows a systematic approach to completing tasks: Agent mode analyzes your request, and the context of the codebase to fully comprehend the task requirements and goals. The agent may search through your codebase, documentation, and the web to identify relevant files and understand the current implementation. Based on the analysis, the agent breaks down the task into smaller steps and plans the changes, learning from the available context as it goes. The agent makes the necessary code modifications according to the plan across your entire codebase, also potentially suggesting new libraries, terminal commands to run or steps you should make outside of Cursor. The agent will confirm the changes look correct after being made by [applying them](/chat/apply). If it notices any issues or linter errors (when supported by the language), it will attempt to fix them. Once the agent is happy, it yields back and summarizes the changes it made. Agent mode creates checkpoints before making changes, allowing you to revert if needed.
Learn more about [checkpoints](/chat/overview#checkpoints).
## Example Use Cases For best results, be specific about what you want to accomplish, but you don't need to specify how the agent should approach the task. ```md "Add a dark mode toggle to my React application" ``` Agent mode will: 1. Identify your application's styling approach 2. Add necessary theme state management 3. Create toggle component 4. Update styling across relevant components 5. Add persistence if appropriate ```md "Optimize my API calls to implement caching and reduce redundant requests" ``` Agent mode will: 1. Find all API call locations 2. Implement appropriate caching strategy 3. Add cache invalidation logic 4. Update components to use cached data ## Configuration Options * **Select a Model**: Pre-select a model for agent mode * **Edit Keybindings**: Set keybindings for agent mode * **Toggle Available Tools**: Toggle available tools * **Enable Auto-run and Auto-fix Errors**: Enable auto-run and auto-fix errors (read more about [tool settings](/chat/tools#advanced-options)) When using Agent mode with auto-run enabled, review proposed changes carefully before confirming major modifications. # Apply Source: https://docs.cursor.com/chat/apply Learn how to apply, accept, or reject code suggestions from chat using Cursor's Apply feature Cursor's `Apply` allows you to quickly integrate a codeblock suggestion from the chat into your code. ## How Apply Works Apply is a specialized model we've developed specifically for rapid code application. It's designed to efficiently handle large-scale code changes while maintaining precision and reliability. The key advantage of Apply is its focused purpose - it doesn't need to understand or generate code itself. Instead, it works in tandem with your chosen Cursor model, which handles the intelligent code generation. Apply then takes those changes and efficiently applies them across thousands of lines of code in seconds, making it perfect for large-scale refactoring and updates. ## Apply Code Blocks To apply a code block suggestion, you can press on the play button in the top right corner of each chat code block. This will edit your file to incorporate the code produced by Chat. Since you can add the most context and have the most back-and-forth with the model in Chat, we recommend Chat + Apply for more complex AI-driven code changes. ## Accept or Reject Once you have applied a code block, you can go through the diffs and accept or reject the changes. You can also click on the "Accept" or "Reject" buttons in the top right corner of the chat code block. `Ctrl/⌘ Enter` to accept, `Ctrl/⌘ Backspace` to reject. # Ask mode Source: https://docs.cursor.com/chat/ask Ask mode lets you explore and learn about codebases through AI search and queries without making changes Ask is a "read-only" mode for the [Chat](/chat/overview) made to ask questions, explore, and learn about a codebase. It is a built-in mode in Cursor that has [search tools](/chat/tools#search) enabled by default. Make sure to read [chat overview](/chat/overview) to learn more about how modes work in Cursor. ## Difference to Other Modes Ask is unique to the other default modes (Agent and Manual) as it does not apply any suggested changes by default - this makes it a sort of "read only" mode, having the full ability to read files and other context, but without the ability to make any changes on its own. This can be great for learning about a codebase you may not want to make changes to, or to plan out a solution with the AI before implementing it! ## Configuration Options * **Model** - Pre-select a model that should be the default for Ask * **Keybinding** - Set a keybinding to switch to the Ask mode * **Search Codebase** - Allow Cursor to search for it's own context, instead of you having to manually @ files as context when you want the AI to see them ![](https://mintlify.s3.us-west-1.amazonaws.com/cursor/images/chat/ask.png) # Custom Modes Source: https://docs.cursor.com/chat/custom-modes Create custom Cursor modes with tailored tools and prompts to personalize AI assistance for specific workflows Custom modes allows you to compose new modes with tools and prompts that fits your workflow. These are in addition to [Agent](/chat/agent.mdx), [Ask](/chat/ask.mdx), and [Manual](/chat/manual.mdx) mode which are built-in. Custom modes are currently in beta.
You can enable custom modes from `Settings` → `Features` → `Chat` → `Custom modes`
## Creating a Custom Mode To create a custom mode, you can open the mode menu and click `Add custom mode`. From there, you will have the option to select name, icon, shortcut as well as enabled tools and custom instructions. ![Create custom mode](https://mintlify.s3.us-west-1.amazonaws.com/cursor/images/chat/custom-modes.png) We're considering adding a `.cursor/modes.json` file to your project to make it easier to create and share custom modes. ## Example Modes While you can make a mode with any combination of tools and instructions, here are some examples of modes that you might find useful. Encourages detailed explanations and frequent clarifying questions, without automatically applying edits or running tools.

**Tools:**
All `Search`
**Custom Instructions:**
Focus on explaining concepts thoroughly and ask clarifying questions before providing solutions
Focuses exclusively on enhancing existing code structure, without introducing new functionality or reading additional files.

**Tools:**
`Edit & Reapply`
**Custom Instructions:**
Focus solely on improving existing code structure without adding new functionality
Generates comprehensive implementation plans without directly modifying code, documenting the approach clearly in a `plan.md` file.

**Tools:**
`Codebase`, `Read file`, `Terminal`
**Custom Instructions:**
Create detailed implementation plans without making direct code changes. Write it to `plan.md`
Collects extensive information from various sources, including web searches and codebase exploration, before recommending solutions.

**Tools:**
`Codebase`, `Web`, `Read file`, `Search files`
**Custom Instructions:**
Gather comprehensive information from multiple sources before suggesting solutions
Aggressively applies all available tools, making bold changes proactively with minimal user confirmation.

**Tools:**
All tools with `Auto-apply edits` and `Auto-run` enabled
**Custom Instructions:**
Take initiative and make bold changes with minimal confirmation
Conducts an in-depth investigation by gathering extensive context from source files and terminal outputs, then proposes precise, targeted fixes.

**Tools:**
All `Search`, `Terminal`, `Edit & Reapply`
**Custom Instructions:**
Thoroughly investigate issues by gathering extensive context before proposing targeted fixes
## Custom Mode Setting Cursor provides a powerful set of tools that you can use to customize your chat experience. Learn about all the available tools that can be used in Chat. ## Resources Alongside the above list, there are also a number of community resources available with ideas and suggestions for custom modes that have proven effective for other users. Explore a curated collection of custom modes submitted by the community! # Manual Mode Source: https://docs.cursor.com/chat/manual Make precise code changes with explicit file targeting - a focused editing mode with user-controlled tooling Manual mode is designed for making targeted code modifications when you know exactly what changes are needed and where. Unlike Agent mode, it does not explore the codebase or run terminal commands; it relies entirely on your specific instructions and the context you provide (e.g., via `@`-mentioning files). ## Manual's Capabilities Applies specific code changes exactly as instructed by the user. Follows user commands without autonomous exploration or planning. Can make coordinated changes across multiple specified files. Primarily uses file editing capabilities; lacks search and terminal tools. Make sure to read [chat overview](/chat/overview) to learn more about how modes work in Cursor. ## Using Manual Mode Manual mode allows for a more precise and targeted approach to code editing. It is designed for making targeted code modifications when you know exactly what changes are needed and where. To make use of Manual mode, you need to explicitly mention the files you want to edit using the `@` symbol. Create your request as you normally would in the chat. Add context to your request by mentioning the files you want to edit using the `@` symbol. After applying, you can review the changes. Manual mode may flag potential issues if linters are configured. Once edits are applied, the task is considered complete. Manual mode excels when you need control and precision, acting as an AI pair programmer executing your specific plan. Provide clear context and instructions for best results. ## Example Use Cases Provide explicit file paths (using `@`) and clear descriptions of the changes you want. **Refactoring Specific Functions** "In @src/utils/helpers.ts and @src/components/UserProfile.tsx,rename the function `getUserData` to `fetchUserProfile` and update all call sites within these files." Manual mode will: 1. Locate `getUserData` function definitions and calls *only within the specified files*. 2. Rename the function and update the call sites as instructed. **Applying Boilerplate** "Add the standard copyright header comment to the top of @src/newModule.js and @src/newService.java" Manual mode will: 1. Open the specified files. 2. Insert the provided header comment at the beginning of each file. ## Configuration Options * **Select a Model**: Pre-select a model specifically for Manual mode. * **Edit Keybindings**: Set custom keybindings to quickly activate Manual mode. * **Available Tools**: Manual mode primarily uses the file editing tool. Search and terminal tools are disabled. # Overview Source: https://docs.cursor.com/chat/overview Natural language interface for exploring, editing, and managing code with contextual AI assistance in Chat mode ## What is Chat? Chat (previously "Composer") is Cursor's AI assistant that lives in your sidebar, letting you interact with your codebase through natural language. You can ask questions, request code edits, get terminal command suggestions, and more - all without switching context.