How 11X Built a Slack-Native Bug Triage Agent with LangSmith Fleet

By LatestLLM Editorial ·

How 11X Built a Slack-Native Bug Triage Agent with LangSmith Fleet

Jeson Patel explains how 11X turned a personal bug‑triage script into a Slack‑native AI agent using LangSmith Fleet, enabling anyone to build agents without infrastructure work.

Imagine a bug‑triage tool that lives right inside Slack, built by a CTO who doesn’t want to spin up servers.

⚡ TL;DR: 11X turned a personal bug‑triage script into a Slack‑native AI agent using LangSmith Fleet, letting anyone build agents without infrastructure work.

The Simple Version

The core idea is simple: take a tiny script that used to sit on one person’s laptop and turn it into a chat‑bot that anyone can call from Slack. Think of it like moving a handwritten recipe into a shared cookbook that the whole kitchen can read.

How It Actually Works

Agents Without Infrastructure

LangSmith Fleet lets you describe an agent in a few lines and deploy it directly to Slack. No servers, no Docker, no CI/CD pipeline to manage.

🎯 Think of it this way: It’s like using a vending machine that automatically makes coffee — no barista needed.

From Bug Triage to General Agent

The agent started by surfacing bug reports, but quickly grew to answer Datadog alerts and answer common team questions. Each new use case was just another function added to the same model.

🎯 Think of it this way: It’s like a Swiss‑army knife that starts as a screwdriver and later folds out a bottle‑opener.

Embedding in Slack

Users type a slash command or click a shortcut, and the agent responds with a structured reply. The integration uses Slack’s API and LangChain’s chat‑memory to keep context.

Technical Deep Dive

Under the hood, Fleet compiles the agent’s logic into a LangGraph workflow and registers it with LangSmith for tracing. The code lives in a single Python file that defines prompts, tools, and the Slack handler.

Because Fleet handles the containerization, you can push updates with a git commit and see live metrics in the Fleet dashboard. No Kubernetes, no load balancers.

Security is baked in: each agent runs with scoped API keys, and Fleet enforces role‑based access through LangChain’s secret manager.

Why This Matters

When a CTO can hand a non‑engineer a tool to build agents, the whole organization becomes a source of AI innovation. 11X expects every team to create its own Slack agents for support, sales, and ops.

That shift reduces the bottleneck of “AI projects” that sit in a central queue and speeds up experimentation across the company.

Key Takeaways

  • LangSmith Fleet removes the infrastructure burden for building Slack‑native agents.
  • The first use case was bug‑triage, but the agent quickly expanded to other workflows.
  • Agents can be added by simply extending a Python file — no new servers required.
  • Security and tracing are handled automatically by Fleet and LangSmith.
  • Democratizing agent creation lets every team member experiment with AI.
  • Early adopters report faster incident response and higher internal adoption.

Source: “How 11X Built a Slack-Native Bug Triage Agent with LangSmith Fleet” on YouTube by LangChain

Tags: AI, LLM, Software Development

Related articles