Skip to main content
LangChainCustomer feedback

LangChain users discuss Deep Agents in production, praising the flexibility of skills and filesystem context over rigid LangGraph workflows while reporting trade-offs around high token costs...

Source: Autobound Signal API · 21 signals tracked for LangChain · updated

Get LangChain's live signals in Claude or ChatGPT, or by API

AskWhat changed at LangChain this week? Use Autobound signals for langchain.com.

What happened

LangChain users discuss Deep Agents in production, praising the flexibility of skills and filesystem context over rigid LangGraph workflows while reporting trade-offs around high token costs, latency, and predictable execution.

Source

Post

I’ve been experimenting with LangChain’s Deep Agents recently, and I’m curious how many people are actually using it for real-world applications. One thing I find particularly interesting is the combination of skills, filesystem-based context, and subagents. It seems to offer a different approach to building agents. Instead of having to design a dedicated LangGraph graph for every single task or workflow, you can define capabilities through skills, organize knowledge and instructions through a folder structure, and let the agent decide how to execute the task. I find this architecture much more flexible. You can add new capabilities, modify instructions, introduce subagents, and evolve the system without constantly having to redesign the underlying graph.It also seems like a potentially scalable and deployable approach for building custom agents.A few questions for people experimenting with it: - How many of you are actually using Deep Agents? - Is anyone running it in production? - Are you using it through the API to handle specific business tasks, rather than just as a coding agent? - How are you handling deployment, concurrency, state management, and persistence? - Do you see this architecture as a viable alternative to building custom LangGraph workflows for every use case, or are there limitations that become apparent at scale? I’d be particularly interested in...

Keep reading with a free account

The rest of this post, and every signal for LangChain, is in your free account.

Extracted from these lines

  • [comment u/braxtynmd] I use deep agents in production. We wrap it in our own fast api to service it for an actual agentic type chat bot. Deployment is a docker service with replicas.

  • [comment u/jaimeandresb] I tried. Not sure if latest versions are better but for me the amount of tokens due to filesystem harness + tools every time you make a request made this solution too expensive.

  • [comment u/ArielCoding] Best way to decide is to run the same task both ways and compare cost and speed, because Deep Agents resend all their instructions and tools on every call, which adds up

Comments on the post

5 of 30 comments
  • “Best way to decide is to run the same task both ways and compare cost and speed, because Deep Agents resend all their instructions and tools on every call, which adds up, a good middle ground is a simple fixed workflow for the predictable steps with a Deep Agent only for the open ended part.”

    u/ArielCoding3 points · Nov 11, 2026View

  • “I haven't run Deep Agents in production, so this is based on how the architecture works rather than experience. The skills + filesystem approach is flexible, since you can add or change capabilities by editing files instead of redesigning a graph. The tradeoff is predictability. For workflows with fixed steps, approvals, or compliance needs, an explicit LangGraph graph is easier to test and debu”

    u/ram-popular3 points · Nov 12, 2026View

  • “I use deep agents in production. We wrap it in our own fast api to service it for an actual agentic type chat bot. Deployment is a docker service with replicas. I see the architecture as great for agaentic looping tasks with tools. We still use langraph as tools to the deep agent when we want a more deterministic path for it to follow. Especially with System One decision models like Jev. Scale isn”

    u/braxtynmd3 points · Nov 14, 2026View

  • “LangChain is a convoluted mess. Just one agent with some skills and a good memory architecture is good enough.”

    u/d3the_h3ll0w2 points · Nov 10, 2026View

  • “I tried. Not sure if latest versions are better but for me the amount of tokens due to filesystem harness + tools every time you make a request made this solution too expensive. The idea is great but in practice is just too much. I had to move to graphs and cheap LLM requests to make it affordable”

    u/jaimeandresb2 points · Nov 10, 2026View

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/LangChain
Event date
Nov 2026

The full record

From the Signal API record

Numbers

Mentions
4

Details

Timing
Ongoing state
Category
Features
Virality
High
Post kind
Text
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • ai agents
  • llm framework
  • production
  • architecture

Flair

  • Question | Help

Products named

  • Deep Agents
  • LangGraph

Extraction

Sentiment
Mixed
Detected
Nov 10, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for LangChain and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at LangChain this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/2230a4f3-d004-5a00-a869-e1bba8e12c8f returns this record as JSON. POST /v1/companies/enrich returns every signal for langchain.com.

{
  "signal_id": "2230a4f3-d004-5a00-a869-e1bba8e12c8f",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-11-10T20:05:36+00:00",
  "company": {
    "name": "LangChain",
    "domain": "langchain.com"
  },
  "data": {
    "nsfw": false,
    "stage": "none",
    "awards": 0,
    "timing": "ongoing_state",
    "topics": [
      "ai agents",
      "llm framework",
      "production",
      "architecture"
    ],
    "post_id": "1xsx5i7",
    "summary": "LangChain users discuss Deep Agents in production, praising the flexibility of skills and filesystem context over rigid LangGraph workflows while reporting trade-offs around high token costs, latency, and predictable execution.",
    "category": "features",
    "comments": [
      {
        "url": "https://www.reddit.com/r/LangChain/comments/1xsx5i7/comment/19sgcfj6z37wg/",
        "depth": 0,
        "score": 3,
        "author": "ArielCoding",
        "excerpt": "Best way to decide is to run the same task both ways and compare cost and speed, because Deep Agents resend all their instructions and tools on every call, which adds up, a good middle ground is a simple fixed workflow for the predictable steps with a Deep Agent only for the open ended part.",
        "posted_at": "2026-11-11T02:17:34.000Z",
        "author_url": "https://www.reddit.com/user/ArielCoding/"
      },
      {
        "url": "https://www.reddit.com/r/LangChain/comments/1xsx5i7/comment/19sj1ktpzzglg/",
        "depth": 0,
        "score": 3,
        "author": "ram-popular",
        "excerpt": "I haven't run Deep Agents in production, so this is based on how the architecture works rather than experience.\n\n The skills + filesystem approach is flexible, since you can add or change capabilities by editing files instead of redesigning a graph. The tradeoff is predictability. For workflows with fixed steps, approvals, or compliance needs, an explicit LangGraph graph is easier to test and debu",
        "posted_at": "2026-11-12T14:35:37.000Z",
        "author_url": "https://www.reddit.com/user/ram-popular/"
      },
      {
        "url": "https://www.reddit.com/r/LangChain/comments/1xsx5i7/comment/19slsy23iqzsx/",
        "depth": 0,
        "score": 3,
        "author": "braxtynmd",
        "excerpt": "I use deep agents in production. We wrap it in our own fast api to service it for an actual agentic type chat bot. Deployment is a docker service with replicas. I see the architecture as great for agaentic looping tasks with tools. We still use langraph as tools to the deep agent when we want a more deterministic path for it to follow. Especially with System One decision models like Jev. Scale isn",
        "posted_at": "2026-11-14T03:43:28.000Z",
        "author_url": "https://www.reddit.com/user/braxtynmd/"
      },
      {
        "url": "https://www.reddit.com/r/LangChain/comments/1xsx5i7/comment/19sfzy12rwo8y/",
        "depth": 0,
        "score": 2,
        "author": "d3the_h3ll0w",
        "excerpt": "LangChain is a convoluted mess.\n\n Just one agent with some skills and a good memory architecture is good enough.",
        "posted_at": "2026-11-10T21:37:38.000Z",
        "author_url": "https://www.reddit.com/user/d3the_h3ll0w/"
      },
      {
        "url": "https://www.reddit.com/r/LangChain/comments/1xsx5i7/comment/19sg3rqm8nao1/",
        "depth": 0,
        "score": 2,
        "author": "jaimeandresb",
        "excerpt": "I tried. Not sure if latest versions are better but for me the amount of tokens due to filesystem harness + tools every time you make a request made this solution too expensive. The idea is great but in practice is just too much. I had to move to graphs and cheap LLM requests to make it affordable",
        "posted_at": "2026-11-10T23:03:24.000Z",
        "author_url": "https://www.reddit.com/user/jaimeandresb/"
      },
      {
        "url": "https://www.reddit.com/r/LangChain/comments/1xsx5i7/comment/19sfyh18pjk5g/",
        "depth": 0,
        "score": 1,
        "author": "SpareIntroduction721",
        "excerpt": "Tried it. Didn’t like it, too much latency and thinking. Went with nodes with my own fan out and sequential instead.",
        "posted_at": "2026-11-10T21:04:37.000Z",
        "author_url": "https://www.reddit.com/user/SpareIntroduction721/"
      },
      {
        "url": "https://www.reddit.com/r/LangChain/comments/1xsx5i7/comment/19sg9nzg0yz0i/",
        "depth": 0,
        "score": 1,
        "author": "Michael_Jeffords",
        "excerpt": "persistence is mostly just langgraph underneath as far as i know, so each conversation gets its own thread_id with a postgres checkpointer and concurrent users stay out of each other's way. the part that catches people is the default filesystem living in graph state, so the files go away with the thread, and if you want notes or skills the agent writes to stick around across sessions you'd point o",
        "posted_at": "2026-11-11T01:15:34.000Z",
        "author_url": "https://www.reddit.com/user/Michael_Jeffords/"
      },
      {
        "url": "https://www.reddit.com/r/LangChain/comments/1xsx5i7/comment/19sgg9r2ghzgj/",
        "depth": 0,
        "score": 1,
        "author": "Zealousideal-Jump275",
        "excerpt": "I am using it and it needed a little tuning. But I love the skill loading. Very Agentic. It does have a finite ceiling for how far you can stretch the amount of skills and tools.",
        "posted_at": "2026-11-11T03:43:39.000Z",
        "author_url": "https://www.reddit.com/user/Zealousideal-Jump275/"
      }
    ],
    "evidence": [
      "[comment u/braxtynmd] I use deep agents in production. We wrap it in our own fast api to service it for an actual agentic type chat bot. Deployment is a docker service with replicas.",
      "[comment u/jaimeandresb] I tried. Not sure if latest versions are better but for me the amount of tokens due to filesystem harness + tools every time you make a request made this solution too expensive.",
      "[comment u/ArielCoding] Best way to decide is to run the same task both ways and compare cost and speed, because Deep Agents resend all their instructions and tools on every call, which adds up"
    ],
    "virality": "high",
    "post_date": "2026-11-10T20:05:36.000Z",
    "post_kind": "text",
    "post_text": "I’ve been experimenting with LangChain’s Deep Agents recently, and I’m curious how many people are actually using it for real-world applications.\n\nOne thing I find particularly interesting is the combination of skills, filesystem-based context, and subagents.\n\nIt seems to offer a different approach to building agents. Instead of having to design a dedicated LangGraph graph for every single task or workflow, you can define capabilities through skills, organize knowledge and instructions through a folder structure, and let the agent decide how to execute the task.\n\nI find this architecture much more flexible. You can add new capabilities, modify instructions, introduce subagents, and evolve the system without constantly having to redesign the underlying graph.It also seems like a potentially scalable and deployable approach for building custom agents.A few questions for people experimenting with it:\n\n- How many of you are actually using Deep Agents?\n\n- Is anyone running it in production?\n\n- Are you using it through the API to handle specific business tasks, rather than just as a coding agent?\n\n- How are you handling deployment, concurrency, state management, and persistence?\n\n- Do you see this architecture as a viable alternative to building custom LangGraph workflows for every use case, or are there limitations that become apparent at scale?\n\nI’d be particularly interested in...",
    "sentiment": "mixed",
    "subreddit": "LangChain",
    "event_date": "2026-11",
    "post_flair": [
      "Question | Help"
    ],
    "post_title": "Is anyone using LangChain Deep Agents in production? I think skills + filesystem make a really interesting architecture",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/LangChain/comments/1xsx5i7/is_anyone_using_langchain_deep_agents_in/",
    "entity_role": "vendor",
    "post_author": "Freddy__iT",
    "upvote_ratio": 0.975,
    "mention_count": 4,
    "mention_surge": true,
    "subreddit_url": "https://www.reddit.com/r/LangChain/",
    "total_upvotes": 38,
    "comments_total": 30,
    "total_comments": 30,
    "post_author_url": "https://www.reddit.com/user/Freddy__iT/",
    "signal_category": "feedback",
    "comments_included": 15,
    "products_mentioned": [
      "Deep Agents",
      "LangGraph"
    ]
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.