Guidelines - Cursor - Community Forum

Who is this community for?

This is where Cursor users and team members come together to share knowledge, solve problems, and learn from each other. Whether you’re debugging an issue or exploring what’s possible with Cursor, this is the place!

Be excellent to each other

Be kind. Everyone’s learning something. Everyone makes mistakes. Respond the way you’d want someone to respond to you.
Be respectful. Disagree with ideas, not people. Keep it constructive.
Be welcoming. No harassment, no hate speech, no personal attacks, no trolling.
Keep it clean. Nothing obscene, nothing spammy.

Please avoid:

Name-calling or ad hominem attacks
Responding to a post’s tone instead of its actual content
Knee-jerk contradiction

If you’re not sure whether something crosses a line, it probably does.

No Rants

Complaints and criticism are welcomed and encouraged when specific and constructive in where Cursor could improve. Explain what’s not working with clear feedback. Vague rants without substance will be removed. Please phrase your feedback in a solution-oriented manner. Posts that consist solely of low-quality content will be removed.

No Misinformation

Don’t spread false or misleading claims about Cursor or competitors. Claims about functionality, pricing, or performance should be accurate and verifiable. This is a public forum, and search engines index these discussions.

No Rage-bait

Don’t post inflammatory content designed to provoke outrage rather than start a real conversation. This includes sensationalized titles, exaggerated claims, or framing issues in the most divisive way possible. If you have a genuine concern, share it honestly without the drama.

No (completely) AI-Generated Posts

Posts generated entirely by AI will likely be removed. While AI tools can help you draft or refine your writing, posts should reflect your own thoughts and understanding. Automated bots will be silenced.

See something off?

Don’t engage with bad behavior, just flag it. Replying only encourages it and wastes everyone’s time. If enough flags pile up, a Cursor staff member will take action.

Cursor reserves the right to remove content or accounts to keep this space healthy.

Making great contributions

Search first

Somebody may have run into your issue before. A quick search might save everyone some time. If you do post, mentioning what you’ve already found helps avoid duplicate suggestions.

Help others help you

The more context you give, the better others can help. What are you trying to do? What have you tried? What happened instead?

A few things that make a big difference:

A clear, specific title
Relevant tags (having an issue with Bugbot? Add the bugbot tag)
Version numbers, logs, and steps to reproduce
What you’ve already tried or ruled out

Dumping a wall of logs without context usually doesn’t get much traction. Take a few minutes to explain what’s going on.

Choosing the right category

Take a moment to pick the correct category for your post. This will help the right people find it. The pinned topic in each category explains what belongs there.

One topic per thread

Keep threads focused on a single issue. If topics need merging, a Cursor staff member will handle that. Don’t bump old threads with unrelated problems, and try not to derail a conversation midstream.

Adding to existing threads

Got a tip that might help someone? Add it to their thread.

Think you’re hitting the same issue as an existing thread? If it’s recent and unsolved, your details might help uncover the root cause. Jump in!

If it’s older than a couple of months, start a fresh thread with your own details. A lot can change quickly, and “me too” on an old thread doesn’t give anyone much to work with. Feel free to link to related threads if you create a new topic, though!

Response times

This is a community of people helping each other out.

Be patient. Give it a few days before bumping. Don’t @mention people who aren’t already in the conversation.
Give back. If you’ve learned something here, stick around and help someone else. That’s how communities thrive!

About @mentions

When you @mention someone, they get a notification (and maybe an email). Use it thoughtfully.

Generally, don’t @mention people who aren’t already in the thread. It can feel demanding, and active community members already watch for new posts. A good title and the correct category will get more attention than pinging individuals.

When it makes sense: clarifying who you’re responding to in a busy thread, or crediting someone whose solution you’re building on.

Keep it confidential

If something’s confidential, don’t post it. You can edit your own posts for a while after submitting, so if you accidentally share something you shouldn’t have, fix it quickly. If you can’t edit anymore, reach out, and somebody will help.

Don’t share:

Passwords, access credentials, or sensitive secrets
API keys and tokens for third-party services
Internal documentation that could pose a security risk
Personal information