Provide Feedback

Your feedback and contributions help shape the future of AI-assisted development. Learn how to report issues, suggest features, contribute code, and help improve documentation.

Quick Feedback Options

Report a Bug Found an issue? Report it to help us fix it

Request a Feature Have an idea? Share it with the community

Improve Documentation Help make our guides clearer and more helpful

Share Your Experience Tell us what works and what doesn't

Reporting Bugs

Before Reporting

Search existing issues to avoid duplicates
- Cursor Issues
- Claude Code Issues
Verify the issue is reproducible
- Try in a fresh environment
- Disable extensions/plugins
- Update to latest version
Gather information
- Error messages (full text)
- Steps to reproduce
- System information
- Screenshots/recordings if applicable

Bug Report Template

## Bug Description
[Clear, concise description of the issue]

## Steps to Reproduce
1. [First step]
2. [Second step]
3. [See error]

## Expected Behavior
[What should happen]

## Actual Behavior
[What actually happens]

## Environment
- Tool: [Cursor/Claude Code]
- Version: [e.g., 1.2.4]
- OS: [e.g., macOS 14.5]
- Other: [relevant details]

## Additional Context
[Screenshots, logs, related issues]

Where to Report

Cursor Bugs

In-app: Help → Report Issue
GitHub: cursor/cursor
Forum: Bug Reports
Urgent: support@cursor.com

Claude Code Bugs

GitHub: anthropics/claude-code
In-tool: /feedback command
Discord: #bug-reports channel
Email: claude-code@anthropic.com

Requesting Features

Effective Feature Requests

DO:

Explain the problem you’re trying to solve
Provide concrete use cases
Suggest implementation approaches
Link to similar features in other tools
Gauge community interest first

DON’T:

Demand immediate implementation
Duplicate existing requests
Bundle multiple features in one request
Assume your workflow is universal

Feature Request Template

## Feature Description
[What you want to add/change]

## Problem Statement
[What problem does this solve?]

## Use Cases
1. [Specific scenario 1]
2. [Specific scenario 2]

## Proposed Solution
[How might this work?]

## Alternatives Considered
[Other ways to solve this]

## Additional Context
[Mockups, examples, references]

Feature Request Channels

Official Channels
- Cursor: Feature Requests Forum
- Claude Code: GitHub Discussions
Community Voting
- Upvote existing requests
- Comment with additional use cases
- Share in social media for support

Documentation Contributions

Ways to Contribute

Fix Typos & Errors

Correct spelling/grammar
Fix broken links
Update outdated information
Clarify confusing sections

Add Examples

Real-world use cases
Code snippets
Screenshots/GIFs
Video tutorials

Translate Content

Translate to new languages
Review existing translations
Localize examples
Cultural adaptations

Create Tutorials

Step-by-step guides
Best practices
Workflow examples
Tips and tricks

Documentation Process

Fork the repository

git clone https://github.com/[repo]/[project]
cd [project]

Create a branch

git checkout -b docs/improve-setup-guide

Make your changes
- Follow style guide
- Test all examples
- Preview locally
Submit pull request
- Clear description
- Reference issues
- Screenshots if UI changes

Style Guidelines

Writing Style:

Clear and concise
Active voice
Present tense
Second person (“you”)

Technical Style:

Use code blocks with syntax highlighting
Include file paths and line numbers
Test all code examples
Provide both simple and advanced examples

Code Contributions

Getting Started

Read contributing guidelines
- Check CONTRIBUTING.md
- Review code style guide
- Understand project structure
Start small
- Fix a bug
- Improve tests
- Enhance documentation
- Then tackle features
Communicate first
- Discuss major changes
- Get feedback on approach
- Coordinate with maintainers

Pull Request Best Practices

Good PR Checklist:

PR Template Example:

## Description
[What does this PR do?]

## Type of Change
- [ ] Bug fix
- [ ] New feature
- [ ] Breaking change
- [ ] Documentation

## Testing
[How has this been tested?]

## Checklist
- [ ] Tests pass
- [ ] Documentation updated
- [ ] Code follows style guide

User Feedback

Feedback Forums:

Success stories
Workflow improvements
Pain points
Feature discoveries

Channels:

Community forums
Social media (#CursorIDE #ClaudeCode)
Blog posts
Conference talks

User Surveys

Participate in:

Quarterly user surveys
Feature priority polls
Usability studies
Beta testing programs

Case Studies

Share detailed experiences:

Project Overview: What you built
Challenges: Problems faced
Solutions: How AI helped
Results: Outcomes achieved
Lessons: What you learned

Beta Testing

Join Beta Programs

Cursor Beta

Settings → Update → Beta Channel

Early access to features
Direct feedback channel
Influence development

Claude Code Beta

npm install -g @anthropic-ai/claude-code@beta

Test new capabilities
Report beta-specific issues

Beta Tester Responsibilities

Test thoroughly: Use in real projects
Report issues: With detailed reproduction steps
Provide feedback: Both positive and negative
Stay engaged: Participate in discussions
Be patient: Expect bugs and changes

Contributing to This Guide

Improve This Documentation

This guide itself is open for contributions:

Fork the repository

git clone https://github.com/[your-username]/developer-toolkit

Make improvements
- Fix errors
- Add examples
- Enhance explanations
- Update for new features
Submit changes
- Create pull request
- Explain improvements
- Link to sources

Areas Needing Help

Current priorities:

More real-world examples
Video tutorial scripts
Translations
Advanced use cases
Troubleshooting scenarios

Recognition & Rewards

Community Recognition

Active contributors receive:

Contributor badges on forums
Credits in release notes
Early access to features
Direct communication with teams
Conference tickets (top contributors)

Open Source Credits

Your contributions are permanently recorded:

Git history
Contributors page
Release notes
Annual reports

Feedback Ethics

Constructive Feedback Guidelines

Be Respectful:

Criticize ideas, not people
Assume good intentions
Acknowledge current limitations
Suggest improvements

Be Specific:

Provide concrete examples
Explain impact
Suggest solutions
Include context

Be Professional:

Use appropriate language
Stay on topic
Avoid heated debates
Focus on improvements

Contact Information

Direct Feedback Channels

Cursor:

Claude Code:

Response Times

Critical bugs: 24-48 hours
Feature requests: Reviewed monthly
Documentation: 1-2 weeks
General feedback: Best effort

Quick Action Buttons

Report Cursor Bug Open a new issue for Cursor

Report Claude Code Bug Open a new issue for Claude Code

Join Discord Connect with the community

Contribute to Docs Improve this guide

Thank you for helping make AI-assisted development better for everyone! 🙏