--- title: The best communities for developers using AI tools | daily.dev description: One live chat, one searchable subreddit, and one forum give fast debugging, durable fixes, and deep technical discussion for AI developers. canonical: https://daily.dev/blog/best-communities-developers-using-ai-tools/ og:type: article og:url: https://daily.dev/blog/best-communities-developers-using-ai-tools/ og:title: The best communities for developers using AI tools | daily.dev og:description: One live chat, one searchable subreddit, and one forum give fast debugging, durable fixes, and deep technical discussion for AI developers. og:image: https://media.daily.dev/image/upload/s--Db8YrFg0--/f_auto,q_auto/v1/recruiter-landing/6aa0bc190c48544c3db2c566_1788938577538_892d069644?_a=BAMAMiB80 og:site_name: daily.dev og:locale: en_US article:published_time: 2026-09-09 article:modified_time: 2026-09-09T07:51:26.545Z article:author: Daniela Torres twitter:card: summary_large_image twitter:site: @dailydotdev twitter:creator: @dailydotdev twitter:title: The best communities for developers using AI tools | daily.dev twitter:description: One live chat, one searchable subreddit, and one forum give fast debugging, durable fixes, and deep technical discussion for AI developers. twitter:image: https://media.daily.dev/image/upload/s--Db8YrFg0--/f_auto,q_auto/v1/recruiter-landing/6aa0bc190c48544c3db2c566_1788938577538_892d069644?_a=BAMAMiB80 --- **If I had to cut this list down to one rule, it would be this: pick _one live chat_, _one searchable Reddit community_, and _one forum_.** That setup gives you help now, answers you can find later, and room for deeper posts when chat threads move too fast. Here’s the short version of the article: - I’d use **[Discord](https://discord.com/)** for live debugging and back-and-forth help - I’d use **Reddit** for searchable fixes, benchmarks, and workflow notes - I’d use **forums** for longer posts about APIs, agents, [RAG](https://daily.dev/blog/ragflow-revolutionizing-retrieval-augmented-generation-for-ai), and architecture - I’d pick communities based on my stack: - **Cursor users:** Cursor Discord + **r/cursor** - **Claude / Claude Code users:** Anthropic Discord + **r/ClaudeAI** or **r/ClaudeCode** - **OpenAI API users:** OpenAI Discord + OpenAI Developer Forum - **Local model users:** **r/LocalLLaMA** - **Cross-tool AI coding users:** **r/vibecoding**, **r/ChatGPTCoding**, and **r/AI\_Agents** **The main point is simple:** big communities are not always the best ones. In most cases, a smaller, focused group is more useful than a huge chat room full of mixed topics. A few fast takeaways from the full piece: - **12 community picks** made the final list - The article breaks them into **Discord servers, subreddits, forums, and feed-style platforms** - The best use case changes by need: _live help_, _searchable archive_, _hardware benchmarks_, _agent workflows_, or _tool-specific support_ - Some spaces lean toward **API and IDE debugging** - Others lean toward **quantization, VRAM limits, local inference, MCP, and agent setup** ::: @figure {Best AI Developer Communities: Discord vs Reddit vs Forums Compared} ## Quick comparison | Community | Best for | Format | Best when | | --- | --- | --- | --- | | Cursor Discord | Cursor help | Discord | You need an answer right away | | Anthropic Discord | Claude Code, API, MCP | Discord | You’re stuck in Claude workflows | | OpenAI Discord | OpenAI API issues | Discord | You need live support | | OpenAI Developer Forum | API patterns, archived fixes | Forum | You want answers you can find later | | r/LocalLLaMA | Local models, VRAM, quantization | Reddit | You run models on your own hardware | | r/cursor | Cursor fixes and prompt setups | Reddit | You want searchable Cursor posts | | r/vibecoding | Cross-tool workflows | Reddit | You want workflow ideas across tools | | r/vibecoding Discord | Live agent build help | Discord | You need fast back-and-forth | | r/ChatGPTCoding | Assistant comparisons | Reddit | You want ChatGPT vs. Claude vs. Copilot talk | | r/ClaudeAI / r/ClaudeCode | Claude prompts or CLI issues | Reddit | You want Claude-focused archived posts | | r/AI\_Agents | Agent architecture and frameworks | Reddit | Your stack spans more than one tool | | [Kaggle](https://www.kaggle.com/) / [DeepLearning.AI](https://www.deeplearning.ai/) / Apple Forums | Benchmarks, learning, Apple ML | Forum | You need depth more than speed | **My takeaway:** most developers do **better with 2 to 3 high-signal communities** than with a long list of tabs they never check. So I’d keep the stack small, post early, and use each place for one clear job. The rest of the article explains which community fits which workflow, and where each one is weak. ## What makes a strong AI developer community in 2026 A good AI developer community should help you **solve problems**, not bury you in chatter. Four simple lenses make it easier to tell the difference. The first is **live chat vs. searchable archive**. Discord servers like the [Cursor](https://cursor.com/) or [Anthropic](https://www.anthropic.com/) communities are great when you need help fast and want quick back-and-forth. The tradeoff is simple: useful answers can disappear into the scroll and be tough to find later. [Reddit](https://www.reddit.com/) threads and developer forums work better when you want fixes and discussions that stay searchable and still make sense months later. The second filter is **vendor-specific vs. tool-agnostic**. Official Discord servers for [OpenAI](https://openai.com/), [Anthropic](https://www.anthropic.com/), and [Cursor](https://cursor.com/) are great for API-specific troubleshooting and for spotting official updates early. But, of course, they tend to center their own products. Broader spaces like [r/LocalLLaMA](https://www.reddit.com/r/LocalLLaMA/) are often better if your setup spans multiple tools and you want honest tradeoff discussions instead of one-product answers. Then there’s **technical depth**. Not every community goes equally deep. Some spend their time on quantization, VRAM, and model architecture. Others lean more toward IDE setup, prompt help, and agent workflows. (For example, you might explore [AI automation agents](https://daily.dev/blog/learn-about-harpa-the-ai-automation-agent-for-chrome) to streamline your browser tasks.) That difference matters more than people think. If you’re building apps, retrieval and orchestration communities tend to be the best fit. If you run local LLMs, you’ll get more from groups focused on hardware and quantization. And if you’re vibe coding, you’ll want spaces that can help with IDEs and agents without turning every question into a research paper. Use the table below to match each platform type to your workflow. | Platform type | Best for | Pace | Searchability | | --- | --- | --- | --- | | Discord | Live debugging, fast back-and-forth | High | Low | | Reddit | Benchmarks, fixes, practical Q&A | Medium | High | | Developer forums | Structured Q&A, long-form solutions | Low | High | | News feeds | Ecosystem tracking, staying current | Low | Medium | ## 1\. [Cursor Discord](https://discord.com/invite/cursor) The [Cursor Discord](https://discord.com/invite/cursor) is the fastest place to get help if you use [Cursor](https://cursor.com/). Because the server is centered on one tool, the replies tend to stay on topic. Your question is also more likely to reach people who know Cursor well and can answer on the spot. That makes it the best first stop for live troubleshooting. ### Real-time vs. archive-friendly format Cursor Discord is fast, but it isn't very searchable. If you want something you can look up later, [r/cursor](https://www.reddit.com/r/cursor/) on Reddit is a better option. Discord works well for in-the-moment help. Reddit works better when you need an answer that sticks around. ### Best fit by workflow Cursor Discord makes the most sense when you need a quick reply from someone who hit the same problem recently. Think of it less like a [developer knowledge base](https://daily.dev/blog/developer-knowledge-base-for-remote-teams) and more like a live debugging room. Use Cursor Discord for urgent help, and use r/cursor for searchable fixes. ## 2\. [Anthropic Discord](https://www.anthropic.com/discord) The [Anthropic Discord](https://www.anthropic.com/discord) is a focused place for [Claude](https://www.anthropic.com/claude) and [Claude Code](https://www.anthropic.com/claude-code) developers who need fast, technical help. That matters most when you're stuck on Claude Code, agent workflows, or API issues and don't want to wait around for a forum reply. ### Real-time vs. archive-friendly format Discord is built for live back-and-forth. You ask a question, someone replies, and you can keep digging from there. [r/ClaudeAI](https://www.reddit.com/r/ClaudeAI/), on the other hand, works better for answers you may want to search for later. It's a better home for longer-lived discussions that don't disappear into a fast-moving chat. ### Claude Code focus and technical depth The server has dedicated channels for Claude Code, which makes it easier to get straight to the point. And because traffic is lower, conversations are usually easier to follow. That makes the Discord especially useful for developers working on agent engineering and API troubleshooting. If you need help _right now_, this setup tends to work well. ### Best fit by workflow For most developers, the split is simple: use Discord when speed matters, and use Reddit for anything you may want to revisit later. | Workflow | Best platform | | --- | --- | | Live Claude and API debugging | Anthropic Discord | | Searchable workflows and benchmarks | r/ClaudeAI | ## 3\. [OpenAI Discord](https://discord.com/invite/openai) The [OpenAI Discord](https://discord.com/invite/openai) is the fastest place to get live help inside OpenAI's ecosystem. It's also one of the busiest spots for developers using OpenAI tools, which makes it a smart first stop when you need to get unstuck fast. Use it for live debugging. Use the [OpenAI Developer Forum](https://community.openai.com/) for answers you may want to save, revisit, and search later. ### Technical depth for coding workflows Discord works best for narrow API issues, like a failed API call or a setup bug in Responses, function calling, or structured outputs. The more specific you are, the better your odds of getting a useful reply. When you post, include: - Your [OpenAI model](https://daily.dev/blog/openais-gpt-4o-everything-you-need-to-know-in-one-place) - Your endpoint - Your SDK version - The exact error message That gives people enough context to help faster. If the issue needs an answer you can come back to later, move it to the OpenAI Developer Forum in the next section. ### Best fit by workflow | Workflow | Best platform | | --- | --- | | Live API debugging and quick unblocking | OpenAI Discord | | Searchable fixes for rate limits and API quirks | OpenAI Developer Forum | | Searchable fixes for API issues and prompts | [r/ChatGPTCoding](https://www.reddit.com/r/ChatGPTCoding/) | ## 4\. [OpenAI Developer Forum](https://community.openai.com/) After live troubleshooting in the [OpenAI Discord](https://discord.com/invite/openai), the forum is where the answer sticks around. Use the [OpenAI Developer Forum](https://community.openai.com/) for durable, searchable answers to API and workflow questions. Threads are indexed and easy to search, which makes past fixes much easier to find when the same issue shows up again. ### Real-time vs. archive-friendly format Use Discord for live debugging. Use the forum for architecture decisions, implementation notes, and repeatable patterns you may want to revisit later. ### Technical depth for coding workflows The forum works well for deeper topics like function calling, tool schemas, agent orchestration, and memory handling. These workflows usually need more space, more context, and a thread you can return to instead of a fast-moving chat. ### Best fit by workflow Use the forum when the question needs a permanent record. | Workflow | Best platform | | --- | --- | | Live API debugging | OpenAI Discord | | Researching function calling or tool use logic | OpenAI Developer Forum | | Documenting agent orchestration patterns | OpenAI Developer Forum | | Long-form questions about API changes | OpenAI Developer Forum | ## 5\. [r/LocalLLaMA](https://www.reddit.com/r/LocalLLaMA/) If you run models on your own hardware, [r/LocalLLaMA](https://www.reddit.com/r/LocalLLaMA/) is the place to go for hardware limits, quantization, local inference stacks like [Ollama](https://ollama.com/) and [vLLM](https://github.com/vllm-project/vllm), and privacy-focused setups. The subreddit is known for strict benchmarking and blunt feedback on model performance and hardware efficiency. So if you're spending time there, two things matter most: **searchability** and **benchmark data**. ### Archive-friendly format Unlike Discord, r/LocalLLaMA is searchable. That means setup notes don't vanish once a chat scrolls away. Old threads can still help weeks or months later, which is a big deal when you're comparing hardware, testing model behavior, or trying to remember which config actually worked. ### Technical depth for coding workflows If you're evaluating open-source models, this is where you'll find benchmark comparisons, hardware limits, and setup fixes. That makes it useful when you want a private, repeatable local workflow instead of bouncing between scattered chat messages. The table below shows where the subreddit fits best. ### Best fit by workflow | Workflow | Best platform | | --- | --- | | Choosing hardware for local inference | r/LocalLLaMA | | Comparing quantization formats | r/LocalLLaMA | | Benchmarking open-source models | r/LocalLLaMA | ## 6\. [r/cursor](https://www.reddit.com/r/cursor/) If Cursor Discord is the place for live help, [r/cursor](https://www.reddit.com/r/cursor/) is where those fixes tend to stick around. It’s the searchable home for [Cursor AI](https://daily.dev/blog/cursor-ai-everything-you-should-know-about-the-new-ai-code-editor-in-one-place) fixes and workflow notes, with developers sharing detailed posts about what works in day-to-day use. That makes it a better fit for issues you may want to look up again later. ### Technical depth for coding workflows Most discussions here center on setup and debugging. You’ll see threads about rules files, Agent mode prompts, and extension setups that hold up in active projects. ### Best fit by workflow | Workflow | Best platform | | --- | --- | | Debugging Cursor-specific IDE behavior | r/cursor | | Tuning Composer and Agent mode prompts | r/cursor | | Finding rules file examples | r/cursor | ## 7\. [r/vibecoding](https://www.reddit.com/r/vibecoding/) [r/vibecoding](https://www.reddit.com/r/vibecoding/) is where developers talk about AI coding workflows _across_ tools, not just inside one product. You’ll find prompt ideas, agent setups, benchmarks, and workflow notes from people using [Cursor](https://www.cursor.com/), [Claude Code](https://claude.ai/code), and [GitHub Copilot](https://github.com/features/copilot). Its strong point is simple: **cross-tool comparison**. If you want practical notes on how people move between tools in actual projects, this is usually a better place to look than a product-specific forum. It’s less about one-off fixes and more about patterns you can reuse. People tend to share what’s working in live projects with Cursor, Claude Code, and GitHub Copilot. So the subreddit is better for searchable workflow discussion than back-and-forth troubleshooting. The table below helps split broad workflow talk from tool-specific debugging. ### Best fit by workflow | Workflow | Best platform | | --- | --- | | Sharing prompts, agent setups, and benchmarks | r/vibecoding | | Reading candid, searchable workflow discussions | r/vibecoding | | Debugging a specific Cursor or Claude Code issue | [r/cursor](https://www.reddit.com/r/cursor/) or [r/ClaudeCode](https://www.reddit.com/r/ClaudeCode/) | | Live, tool-specific debugging | Discord | ## 8\. [r/vibecoding Discord](https://discord.gg/vibecoding) The r/vibecoding Discord is the live chat version of the [r/vibecoding](https://www.reddit.com/r/vibecoding/) subreddit. Use the subreddit for saved workflows. Jump into Discord when you need fast back-and-forth. ### Real-time vs. archive-friendly format Discord works best for live debugging. The subreddit works better as a searchable reference you can come back to later. ### Technical depth for coding workflows When you're in the middle of a build, speed usually matters more than permanence. That's where the r/vibecoding Discord shines. It's a good place to get live help during active agent builds, especially when you're trying to fix something NOW instead of writing up a polished post. The community leans into agent-based coding, shipping products, and creator build logs. You'll see practical discussion around [Cursor](https://www.cursor.com/), [Claude Code](https://claude.ai/code), and multi-agent workflows. Unlike [r/LocalLLaMA](https://www.reddit.com/r/LocalLLaMA/), which leans more toward hardware topics, this Discord is centered on shipping workflows. ### Best fit by workflow | Workflow | Best platform | | --- | --- | | Getting unstuck fast on a live agent build | r/vibecoding Discord | | Comparing Claude Code and Cursor workflows | r/vibecoding subreddit | | Searchable reference for future teammates | r/vibecoding subreddit | | Local model tuning and hardware questions | r/LocalLLaMA | ## 9\. [r/ChatGPTCoding](https://www.reddit.com/r/ChatGPTCoding/) If you want a broader Reddit community for comparing [the best AI tools for developers](https://daily.dev/blog/the-best-ai-tools-for-developers-in-2024), instead of sticking to one vendor, **r/ChatGPTCoding** is a strong pick. It centers on coding with ChatGPT and other assistants, so it’s a useful place to spot side-by-side discussion of tools like [Cursor](https://www.cursor.com/), [GitHub Copilot](https://github.com/features/copilot/), and [Claude](https://claude.ai/). Reddit works well when you want searchable posts and examples you can come back to later. Discord is usually better when you need live back-and-forth debugging. Unlike more tool-specific communities such as [r/cursor](https://www.reddit.com/r/cursor/) or [r/ClaudeCode](https://www.reddit.com/r/ClaudeCode/), this subreddit tends to bring up edge cases and failures across multiple assistants in a direct, practical way. Use **r/ChatGPTCoding** when you want assistant comparisons. Use [r/vibecoding](https://www.reddit.com/r/vibecoding/) when the discussion is more about agents and workflow setup. ### Best fit by workflow | Workflow | Best platform | | --- | --- | | Comparing ChatGPT vs. Claude for a coding task | r/ChatGPTCoding | | Comparing workflows across assistants | r/ChatGPTCoding | | Finding a reusable prompt pattern for code review | r/ChatGPTCoding | | Deep bug reports tied to a specific tool | r/cursor or OpenAI Developer Forum | That makes **r/ChatGPTCoding** a solid bridge between product-specific subreddits and the broader AI coding conversation. ## 10\. [r/ClaudeAI](https://www.reddit.com/r/ClaudeAI/) and [r/ClaudeCode](https://www.reddit.com/r/ClaudeCode/) [r/ClaudeAI](https://www.reddit.com/r/ClaudeAI/) is the place for broader Claude prompting, model updates, and agent workflows. [r/ClaudeCode](https://www.reddit.com/r/ClaudeCode/) is more focused. It leans into the [Claude Code](https://claude.ai/code) CLI, terminal setups, and troubleshooting. Here’s the simple way to think about it: if you need live back-and-forth help, [Anthropic Discord](https://discord.com/invite/anthropic) is usually faster. But if you want answers you can come back to later, these subreddits do that job better. Use r/ClaudeAI for prompt patterns and task-level behavior. Use r/ClaudeCode for CLI, subagent, and MCP troubleshooting. ### Real-time vs. archive-friendly format Both subreddits are asynchronous and searchable, which makes them handy for fixes and examples you may want to find again later. That matters more than people think. A fast chat can solve your issue in the moment, but a Reddit thread often helps the next time the same thing breaks. As one AI builder community put it: > "Reddit is searchable, asynchronous, and brutally honest - the best free layer for staying current." - AI Builder Club [\[1\]](https://www.aibuilderclub.com/blog/best-ai-communities-2026) ### Best fit by workflow The split is pretty straightforward: general Claude questions go to r/ClaudeAI, while Claude Code issues fit better in r/ClaudeCode. | Workflow | Best platform | | --- | --- | | Researching Claude prompting patterns | r/ClaudeAI | | Debugging Claude Code CLI or MCP workflows | r/ClaudeCode | | Finding subagent orchestration examples | r/ClaudeCode | | Getting unstuck on a setup error right now | Anthropic Discord | Use the subreddit that matches the scope of the problem. ## 11\. [r/AI\_Agents](https://www.reddit.com/r/AI_Agents/) If the earlier subreddits focus on single tools, [r/AI\_Agents](https://www.reddit.com/r/AI_Agents/) is the broader home for agent architecture, framework comparisons, and MCP workflows. You’ll see discussions about [CrewAI](https://www.crewai.com/), [LangChain](https://www.langchain.com/), the [Model Context Protocol (MCP)](https://modelcontextprotocol.io/) ecosystem, and other agentic workflows. In plain English: this is where people go when their stack stretches across more than one framework. It sits in that middle ground between vendor-specific channels and narrow tool subreddits. ### Technical depth for coding workflows That makes it a good place for cross-framework tradeoffs, not just one-off bug fixes. The tone tends to be blunt and analytical. The strongest threads usually lay things out plainly: what broke, what changed, and what worked. ### Best fit by workflow Use r/AI\_Agents when you want feedback on agent architecture and MCP integration. For syntax errors or tool-specific issues, the earlier Discord communities will usually get you unstuck faster. ## 12\. Kaggle Discussions, [DeepLearning.AI Community](https://community.deeplearning.ai/), and [Apple Developer Forums AI & ML](https://developer.apple.com/forums/tags/machine-learning) Use these communities when you need durable references, benchmark notes, or platform-specific ML guidance. They make the most sense when speed matters less than depth, repeatability, and ecosystem fit. ### Tool specificity and technical depth for coding workflows Each community has a different job. The table below separates research-heavy, learning-focused, and Apple-specific spaces. | Community | Tool Focus | Depth | Best For | | --- | --- | --- | --- | | Kaggle Discussions | Notebooks, datasets, model evaluation | High | Data scientists and ML researchers | | DeepLearning.AI Community | LLM APIs, RAG, AI frameworks | High | AI engineers learning to ship products | | Apple Developer Forums AI & ML | [CoreML](https://developer.apple.com/documentation/coreml), on-device ML, Apple APIs | High | Apple ecosystem developers | **Kaggle Discussions** is where benchmarking culture shows up most clearly. If you need to compare model performance or find a notebook that actually works, this is usually the first place to check. It’s especially useful when you want less theory and more proof. **DeepLearning.AI Community** is a strong home base if you want structured courses and feedback from people building things as you build. It helps bridge the gap between learning concepts and getting a product out the door. **Apple Developer Forums AI & ML** is the right fit for on-device ML, CoreML integration, and Apple-specific APIs. If your issue lives inside the Apple stack, this forum is often far more useful than a general ML community. ### Best fit by workflow Use Kaggle for benchmarking, DeepLearning.AI for structured learning, and Apple Developer Forums for CoreML and on-device debugging. The quick comparison tables below make the tradeoffs easy to scan. ## Quick comparison tables Use these tables to scan by platform type and pick the community that fits your workflow. If you want just one fast reference point, start with the platform type that lines up with how you work: live chat, search, or long-form support. ### [Discord](https://discord.com/) communities | Community | Best Use Case | Depth | Tone | | --- | --- | --- | --- | | **[Cursor](https://discord.com/invite/cursor)** | IDE-specific features, `.cursorrules` | Medium-high | Tool-specific, fast | | **[Anthropic](https://www.anthropic.com/discord)** | Claude Code, MCP, agent workflows | High | Focused, technical | | **[OpenAI](https://discord.com/invite/openai)** | OpenAI API support, official tool support | Medium-high | Busy, fast-moving | | **[r/vibecoding](https://discord.gg/vibecoding)** | Live agent builds, shipping workflows | Medium-high | Practical, creator-focused | ### Subreddits | Community | Best Use Case | Depth | Tone | | --- | --- | --- | --- | | **[r/LocalLLaMA](https://www.reddit.com/r/LocalLLaMA/)** | Local inference, quantization, hardware benchmarks | Very High | Benchmark-driven | | **[r/cursor](https://www.reddit.com/r/cursor/)** | Cursor IDE fixes, rules files, Agent mode prompts | Medium-high | Practical, searchable | | **[r/vibecoding](https://www.reddit.com/r/vibecoding/)** | Cross-tool workflows, prompt patterns, agent setups | Medium | Workflow-centric | | **[r/ChatGPTCoding](https://www.reddit.com/r/ChatGPTCoding/)** | Cross-tool comparisons (Cursor vs. Copilot) | Medium | Cross-tool comparisons | | **[r/ClaudeAI](https://www.reddit.com/r/ClaudeAI/)** | Claude prompting and model updates | Medium-high | Workflow-centric, practical | | **[r/ClaudeCode](https://www.reddit.com/r/ClaudeCode/)** | Claude Code CLI, subagent troubleshooting, MCP | High | Technical, troubleshooting-focused | | **[r/AI\_Agents](https://www.reddit.com/r/AI_Agents/)** | Agent failure threads, autonomous workflow reports | High | Experimental, troubleshooting-heavy | ### Forum-style spaces | Community | Best Use Case | Depth | Tone | | --- | --- | --- | --- | | **[OpenAI Developer Forum](https://community.openai.com/)** | Official API support, searchable fixes | High | Structured, archival | | **[DeepLearning.AI Community](https://community.deeplearning.ai/)** | Structured learning, LLM APIs, RAG | Medium-high | Educational, supportive | | **Kaggle Discussions** | Model benchmarking, notebooks, dataset evaluation | High | Rigorous, proof-focused | | **[Apple Developer Forums AI & ML](https://developer.apple.com/forums/tags/machine-learning)** | CoreML, on-device ML, Apple APIs | High | Platform-specific, technical | Use **High** and **Very High** communities when you're debugging production issues. Those spaces tend to be better when you need sharp answers, edge-case reports, or posts you can trace back later. Use **Medium**\-depth communities when you're exploring ideas, testing prompt patterns, or working through early drafts. A simple way to use this table: pick **one live channel** and **one searchable archive** so you can move fast now and still have something you can look up later. ## How to choose the right mix of communities Once you’ve picked a few communities from the list above, use one simple rule: **don’t spread yourself too thin**. Stick to **2 to 3 high-signal spaces**. A good way to think about it is **anchor plus feed**. Your **anchor** is the place where you post real problems and get deeper feedback. Your **feed** is where you scan for fast fixes, fresh examples, and what people are running into right now. Here’s a quick map based on your goal: | Goal | Anchor (Post Here) | Real-Time Help | Async Signal | | --- | --- | --- | --- | | **Building production agents** | [DeepLearning.AI Community](https://community.deeplearning.ai/) | [Anthropic Discord](https://www.anthropic.com/discord) | [r/AI\_Agents](https://www.reddit.com/r/AI_Agents/) | | **Experimenting with vibecoding** | [r/vibecoding](https://www.reddit.com/r/vibecoding/) | [Cursor Discord](https://discord.com/invite/cursor) | [r/ChatGPTCoding](https://www.reddit.com/r/ChatGPTCoding/) | Post within your first week. Lurking helps you learn the vibe, the common questions, and the kinds of posts that get replies. But posting is what gets you feedback, connections, and faster answers. Over time, people who contribute tend to get better replies too. ## Where [daily.dev](https://daily.dev/) fits If you want a lighter, feed-based layer alongside the live communities above, daily.dev fits that role well. It’s best for **discovery and context**. The personalized feed brings up articles and discussions based on your stack, so you can keep up without hopping across a bunch of tabs. For developers, the main draw is seeing relevant AI writing and topic-focused discussion in one place. [Squads](https://daily.dev/squads) gives you a way to talk about specific subjects tied to what you’re already reading, and the AI Squad is a good place to start if you want more on AI tooling. The downside is simple: discussion moves slower there, so it’s not the best place when you need a fast answer. Use daily.dev to follow AI tooling news and get context in a single feed. It works best as a companion to the communities above, especially when you want a better sense of the topic before you post. ## Conclusion For most people, the best [setup of dev resources](https://daily.dev/blog/dev-resources-top-community-picks) is simple: **one live chat, one searchable archive, and one structured forum**. Each one does a different job well. Use live chat for fast debugging, searchable threads for past fixes and benchmarks, and forums for deeper write-ups that need more context. The practical takeaway is straightforward: **pick one vendor Discord, one active subreddit with searchable threads, and one searchable forum or structured community** - then stick with that setup. That gives you live help, searchable benchmarks, and longer discussions when you need more detail. If your main tool is Cursor or Claude, a good starting setup is the Anthropic or Cursor Discord for live questions, [r/ClaudeAI](https://www.reddit.com/r/ClaudeAI/) or [r/ChatGPTCoding](https://www.reddit.com/r/ChatGPTCoding/) for searchable threads, and a structured community when you need something more formal. If you work with local models, swap in [r/LocalLLaMA](https://www.reddit.com/r/LocalLLaMA/). Keep it small. Use the communities you already check on a regular basis. ## FAQs ### How do I pick my first three communities? Pick your first three communities based on your goals. Don't join everything at once. A smart mix looks like this: - One asynchronous space for discussion - One real-time hub for troubleshooting - One centralized feed for AI updates For most developers, that usually means **one subreddit**, **one Discord** like **Cursor** or **Anthropic**, and **daily.dev** for a high-level view of AI news. ### Which community is best for local LLMs? For local LLMs, **r/LocalLLaMA** is the best community. It’s the main hub for people running models on their own hardware, with practical discussion around quantization, VRAM limits, GPU offloading, and edge deployment. If you need quick setup help, the **Ollama Discord** is a practical, hardware-focused place to ask about local model setup and performance limits. ### When should I use Discord instead of Reddit or forums? Use **Discord** when you need live help with debugging or troubleshooting. It's best for fast back-and-forth on error messages, hardware limits, or setup problems. Use **Reddit** when you want discussions you can search later and come back to, especially for benchmarks, practical Q&A, and blunt takes on new tools. **daily.dev** helps you follow both in one feed. ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/og-image.png?v=a830cdf1","width":1200,"height":630},"sameAs":["https://twitter.com/dailydotdev","https://www.linkedin.com/company/dailydotdev","https://github.com/dailydotdev","https://www.instagram.com/dailydotdev"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","description":"Free, personalized developer news aggregator. Stay on top of software development news, AI coding tools, and web dev - curated daily from trusted sources.","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}},{"@type":"WebPage","@id":"https://daily.dev/blog/best-communities-developers-using-ai-tools/","url":"https://daily.dev/blog/best-communities-developers-using-ai-tools/","name":"The best communities for developers using AI tools | daily.dev","description":"One live chat, one searchable subreddit, and one forum give fast debugging, durable fixes, and deep technical discussion for AI developers.","inLanguage":"en-US","isPartOf":{"@id":"https://daily.dev/#website"},"timeRequired":"PT18M"},{"@type":"Article","@id":"https://daily.dev/blog/best-communities-developers-using-ai-tools/#article","headline":"The best communities for developers using AI tools","url":"https://daily.dev/blog/best-communities-developers-using-ai-tools/","datePublished":"2026-09-09","dateModified":"2026-09-09T07:51:26.545Z","isPartOf":{"@id":"https://daily.dev/#website"},"publisher":{"@id":"https://daily.dev/#organization"},"mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/blog/best-communities-developers-using-ai-tools/"},"description":"One live chat, one searchable subreddit, and one forum give fast debugging, durable fixes, and deep technical discussion for AI developers.","image":{"@type":"ImageObject","url":"https://media.daily.dev/image/upload/s--Db8YrFg0--/f_auto,q_auto/v1/recruiter-landing/6aa0bc190c48544c3db2c566_1788938577538_892d069644?_a=BAMAMiB80"},"author":{"@type":"Person","name":"Daniela Torres"},"timeRequired":"PT18M","potentialAction":{"@type":"ReadAction","target":"https://daily.dev/blog/best-communities-developers-using-ai-tools/"}},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev/"},{"@type":"ListItem","position":2,"name":"Blog","item":"https://daily.dev/blog/"},{"@type":"ListItem","position":3,"name":"Trends","item":"https://daily.dev/categories/trends/"},{"@type":"ListItem","position":4,"name":"The best communities for developers using AI tools","item":"https://daily.dev/blog/best-communities-developers-using-ai-tools/"}]},{"@type":"FAQPage","@context":"https://schema.org","mainEntity":[{"name":"How do I pick my first three communities?","@type":"Question","acceptedAnswer":{"text":"Pick your first three communities based on your goals. Don't join everything at once. A smart mix looks like this: One asynchronous space for discussion. One real-time hub for troubleshooting. One centralized feed for AI updates. For most developers, that usually means one subreddit, one Discord like Cursor or Anthropic, and daily.dev for a high-level view of AI news.","@type":"Answer"}},{"name":"Which community is best for local LLMs?","@type":"Question","acceptedAnswer":{"text":"For local LLMs, r/LocalLLaMA is the best community. It’s the main hub for people running models on their own hardware, with practical discussion around quantization, VRAM limits, GPU offloading, and edge deployment. If you need quick setup help, the Ollama Discord is a practical, hardware-focused place to ask about local model setup and performance limits.","@type":"Answer"}},{"name":"When should I use Discord instead of Reddit or forums?","@type":"Question","acceptedAnswer":{"text":"Use Discord when you need live help with debugging or troubleshooting. It's best for fast back-and-forth on error messages, hardware limits, or setup problems. Use Reddit when you want discussions you can search later and come back to, especially for benchmarks, practical Q&A, and blunt takes on new tools. daily.dev helps you follow both in one feed.","@type":"Answer"}}]}]} ```