Where to get help
- GitHub repository — report bugs, request features, or submit pull requests.
- Discord — join real-time discussions, troubleshooting, and quick help.
- KodeKloud community — course-related questions, instructor support, and study help.

Quick reference table
Best practices: filing an effective GitHub issue
A well-structured issue speeds up triage and fixes. When creating a GitHub issue, include:- A concise, descriptive title.
- A short summary of the problem.
- Steps to reproduce (exact commands or actions).
- Expected behavior vs actual behavior.
- Environment details (OS, Cline version, editor/version, any extensions).
- Relevant logs, stack traces, or error messages.
- Screenshots, minimal reproducible example, or a small repository that demonstrates the issue.
- Any temporary workarounds you tried.
Example log snippet
When diagnosing issues, including the extension or tool logs is very helpful. Example:When asking for help, include your environment (OS, tool versions), exact steps to reproduce, and any logs or error messages. This information speeds up troubleshooting.
Do not paste sensitive data (API keys, private tokens, or personal credentials) into public issues or chat. Redact or remove secrets before sharing logs or screenshots.
Discord — real-time help and community channels
For faster, conversational help, join the Cline Discord: https://discord.com/invite/cline. Common channels include:- general — community conversation
- prompts — examples and prompt engineering help
- MCP — feature-specific discussion
- new-coders — beginner help and learning tips
- tech-support — troubleshooting and practical fixes