r/LangChain: rules, karma requirements and posting culture

Who posts here

Posts assume you can write Python and already know what RAG, tool calling, MCP, checkpoints and rerankers are. Nobody stops to define them. Beginner questions are allowed and answered without hostility, and a what should I learn next thread was among the most upvoted recent posts, but the replies still come in working developer vocabulary.

• Developers building agents and RAG pipelines at work, asking how others handle failures, retries, evals and cost.
• Open source authors and early-stage founders announcing a library, a CLI or a platform.
• Students, interns and career changers asking what to learn or build to get hired.
• Engineers from nearby jobs, such as SRE or data, trying to decide whether a framework fits their internal tooling.
• People who used the framework early, left, and are back to ask whether it is worth it now.

Karma and account requirements

What it takes to get a post through in r/LangChain.

What you can post

What happens to a new post

Where the most recent posts ended up. Sample size: 400.

• Stayed up80%
• Removed by Reddit's filters10%
• Held by AutoModerator9%
• Removed by moderators<1%
• Deleted by the author<1%

Reddit counts a removal by the subreddit's own AutoModerator rules as a moderator removal, so that share is not all human. Held by AutoModerator means the post is waiting in the mod queue.

What happened when we posted here

We have posted here ourselves. This is how our own posts and comments fared.

Stayed up

100%

Removed by Reddit's filters

<1%

Removed by moderators

0%

Period

July 2026 to August 2026

The rules, in the mods' words

1. 1

   Keep posts relevant

   Posts should be relevant to LangChain or related topics. Spam will be removed. Habitual spam may result in the suspension or removal of your posting privileges.

2. 2

   No NSFW/explicit content

   Posts and comments cannot contain NSFW content.

3. 3

   Be nice

   Users are expected to act in good faith. Treat other users the way you want to be treated. Please follow Reddit's Content Policy. Posts from users with negative karma are automoderated.

These are the rules as archived in January 2025. Rules change. Check the sidebar before you post.

The culture

r/LangChain has about 108,000 members and has drifted well past its name. It is a general room for people building LLM applications: agents, LangGraph workflows, retrieval pipelines, MCP servers, evals. There are only three rules, and moderators removed about half a percent of posts in our sample. What filtering exists is automatic: around 10% of posts were caught by Reddit's filters and a further 9% or so were held by AutoModerator.

Because so little is removed, the feed is a mix of two things. One is real engineering questions, usually text posts of around 190 words with the stack and the failure described. The other is a steady stream of I built this announcements for open source tools and agent platforms, often under the Discussion flair instead of Projects. The typical post gets about three comments, and the announcements are the ones that sit near zero.

The live argument is whether the framework is still needed. Threads asking if vendor agent products make it obsolete, whether a coding agent with a harness beats a graph workflow, and why the documentation is so hard to follow all pull more replies than any launch. Criticism of LangChain itself is welcome here and gets upvoted.

What lands

• A specific production problem with numbers, such as a model-as-judge setup that gives different verdicts on the same input, or an agent run that fails halfway and has to be resumed.
• Framework comparisons argued from your own pain point, like how two agent frameworks handle handoffs between agents.
• Learning path questions from someone who has already covered the basics and lists what they know.
• Honest complaints about the framework, such as the state of the documentation for local models.
• Design questions with no product attached, for example where fixed orchestration should end and model reasoning should begin.

What gets removed or ignored

• Very little is removed by hand. Only two posts in our sample were moderator removals, one a tutorial for connecting a third-party automation product and one a write-up about model-generated SQL.
• Posts from accounts with negative karma, which the rules say are automoderated.
• Spam and off-topic posts. The rules say habitual spam can cost you posting privileges.
• NSFW content, in posts or comments.
• Posts caught by Reddit's own filters or held by AutoModerator, together close to a fifth of the sample. No removal messages are published, so the reasons are not visible.

The unwritten rules

• Staying up is not the same as being read. Launch posts survive moderation and then get one or two comments. Questions get the replies.
• Give the stack. Posts that name the model, the vector store, the retrieval steps and what broke get detailed answers.
• Comments are long for Reddit, around 55 words, and about 9% carry a link. Replies that end by plugging the commenter's own product are common, and they read as plugs.
• If you are sharing a project, use the Projects flair and lead with the failure that made you build it. Posts that open with the feature list look like every other launch in the feed.
• Machine-written replies show up often enough that some now carry a disclosure line. Stiff, over-structured text is noticed.

Self-promotion

There is no self-promotion rule. The only relevant line is that spam will be removed and habitual spam can lead to suspension or removal of posting privileges. In practice project posts are tolerated in volume: Projects is the third most used flair, and tool announcements make up a large part of what stays up. The limit is attention, not moderation. A launch post without a concrete problem, a benchmark or code people can run tends to get no replies, and posting the same tool repeatedly is the pattern the spam rule is written for.

How people write here

Typical post length

187 words

Typical title length

14 words

Titles phrased as a question

27%

Typical comment length

56 words

Comments that include a link

9%

Posts that carry a flair

84%

Top keywords

The words and phrases that show up far more often here than in other communities, from recent posts in r/LangChain.

• langchain 75 posts
• agent 163 posts
• langgraph 67 posts
• agents 125 posts
• llm 70 posts
• rag 47 posts
• tool 96 posts
• model 88 posts
• python 45 posts
• graph 32 posts
• production 52 posts
• layer 42 posts
• tool calls 27 posts
• prompt 48 posts
• mcp 37 posts
• langsmith 14 posts
• retrieval 28 posts
• state 50 posts
• pip install 19 posts
• context 54 posts
• memory 40 posts
• langchain agents 12 posts
• ai agents 35 posts
• open-source 31 posts
• semantic 20 posts
• api 42 posts
• runtime 25 posts
• langchain langgraph 14 posts
• execution 33 posts
• boundary 22 posts
• calls 39 posts
• tools 53 posts
• workflow 39 posts
• code 53 posts
• call 44 posts
• latency 21 posts
• instead 55 posts
• sdk 17 posts
• github 29 posts
• architecture 27 posts

Common questions