Skip to content

Framework

LangGraph

LangGraph is an open-source framework for building stateful, multi-agent LLM applications, modeling workflows as graphs with persistent state and checkpointing.

Known aliases

  • create_supervisor
  • LangGraph Cloud
  • StateGraph

Current stories

buildOne report1 publisher

Six of the eight frameworks in Microsoft's agent-hooks demo have no conformance claim on file

A dev.to author running Microsoft's agent-hooks conformance kit got 69 passes, 4 skips and 0 failures on its reference harness. That covers one host, while the launch demo names eight frameworks and the claims table has three rows.

Publishers:dev.to

Reality

Evidence62
Adoption25
Hype gap+35
Incentives
Not scored
Confidence58
buildOne report1 publisher

AutoGen tops three agent frameworks on GitHub stars and ranks last on monthly PyPI installs

AutoGen has about 60,400 GitHub stars, the most of three leading agent frameworks, but its own README puts it in maintenance mode. A dev.to audit verified on 2026-08-16 says to weigh installs and release history before stars when starting a new project.

Publishers:dev.to

Reality

Evidence58
Adoption62
Hype gap+12
Incentives
Not scored
Confidence55
buildOne report1 publisher

Decepticon runs an autonomous red team as a LangGraph state machine

Decepticon, an autonomous red-team agent built on LangChain and LangGraph, reached #13 on GitHub Trending for Python with 5,825 stars and 1,100 forks. Its write-up details how a state machine runs offensive tools end to end while leaving an audit trail.

Publishers:dev.to

Reality

Evidence30
Adoption25
Hype gap+30
Incentives
Not scored
Confidence30
buildOne report1 publisher

Docker Sandbox kit confines a DeepAgents agent to one local model port

DeepAgents runs in a four-file Docker Sandbox kit whose agent can reach only a local Model Runner on port 12434, with no cloud keys. The egress policy is careful work, and exact reproduction still rests on what PyPI serves when each sandbox is created.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+15
Incentives
Not scored
Confidence40
investConfirmed2 publishers

Bank AI job postings climb 49% to 139,819 as agent orchestration grows fastest

AI-related job postings at banks such as JPMorgan Chase, Citigroup and Capital One rose 49% this year to 139,819, according to Draup. Most of the growth is in staff who connect teams of AI agents to business lines and staff who keep those agents in check.

Perspective Coverage

3 publishers
Builder
Builder 25%
Operator
Operator 43%
Investor
Investor 32%

Reality

Evidence40
Adoption30
Hype gap+35
Incentives60
Confidence45
buildOne report1 publisher

Strands and CrewAI agents reported success on runs where verification never executed

Strands and CrewAI agents exited 0 on all six runs where a broken verification tool checked nothing, a recorded-proxy test on dev.to found. Only tool-call traffic captured outside the framework showed the failures.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+10
Incentives
Not scored
Confidence40
buildOne report1 publisher

LLM-dependent agents flipped HivePlane's certification verdicts between runs

Debashish Ghosal got HivePlane's agent certification to repeat across three runs by swapping in deterministic agents and a mocked judge. The stable verdict covers the control plane's plumbing, and whether an LLM-driven agent answers correctly is now outside the certificate.

Publishers:dev.to

Reality

Evidence35
Adoption
Not scored
Hype gap+5
Incentives45
Confidence40
buildOne report1 publisher

Google's open-source AX checkpoints idle AI agents so dozens can share a host worker

Google open-sourced AX, an Apache 2.0 runtime on Kubernetes that checkpoints idle agents and is designed to resume them in under a second. Its savings depend on how long each agent waits on models, tools or people.

Publishers:infoq.com

Reality

Evidence40
Adoption
Not scored
Hype gap+25
Incentives
Not scored
Confidence45
buildOne report1 publisher

Agent retries that feed errors back into the prompt make every attempt cost more than the last

Retry math in a dev.to post on agent circuit breakers has a failing agent's calls growing from 2,000 tokens to 20,000 by attempt 50. Summed, that spend rises with the square of the attempts, so the cap belongs in the orchestrator.

Publishers:dev.to

Reality

Evidence30
Adoption
Not scored
Hype gap+40
Incentives
Not scored
Confidence35
buildOne report1 publisher

Harsher tool-schema changes broke Strands, LangGraph and CrewAI in three different ways over 36 runs

Only a renamed tool argument got through Strands, LangGraph and CrewAI cleanly in a 36-run schema-change test posted on dev.to. Harsher changes let Strands and CrewAI exit 0 with nothing verified while LangGraph crashed outright, so each framework needs its own schema-change test.

Publishers:dev.to

Reality

Evidence42
Adoption
Not scored
Hype gap+12
Incentives15
Confidence40
buildOne report1 publisher

A fraud agent built on TigerGraph keeps its verdicts in code that fails the build on any LLM import

Fraudagent, a TigerGraph challenge entry, settles 20 fraud alerts in code whose build fails on any LLM import. Its verdicts match bit for bit with no API key, so the calibration bug its authors blame for clearing fraud lives in code a test can reach.

Publishers:dev.to

Reality

Evidence45
Adoption5
Hype gap+10
Incentives55
Confidence45
buildOne report1 publisher

Hashing the arguments lets a reworded retry fire the destructive call twice

Across 34 runs on three agent frameworks, a recorder proxy shows that what the dedup key names decides whether a retried publish executes once or twice, and that surviving a SIGKILL is a separate question about where state is kept.

Publishers:dev.to

Reality

Evidence46
Adoption
Not scored
Hype gap+18
Incentives36
Confidence52
buildOne report1 publisher

A single supervisor's context saturates after about five worker interactions

An engineer writing on dev.to spent two weeks on prompts and a larger model before concluding that his ten-step agent workflow broke at the fourth handoff because one supervisor was holding every worker's output.

Publishers:dev.to

Reality

Evidence28
Adoption35
Hype gap+32
Incentives30
Confidence38
buildOne report1 publisher

Adding both the guard and sandbox moved measured attack success from 16% to 20%

A LangGraph travel concierge was scored against four prompt-injection defenses, one layer at a time, on 35 prompts. With 25 attack samples in the set, the four-point regression the harness reports is a single prompt flipping.

Publishers:dev.to

Reality

Evidence54
Adoption
Not scored
Hype gap+24
Incentives42
Confidence52
buildOne report1 publisher

Writing the edges in Python takes the routing decision out of the LLM call

A dev.to postmortem of the central orchestrator agent argues for LangGraph's explicit edges, and the 60 percent latency win it cites only adds up once the manager's own turns come off the critical path.

Publishers:dev.to

Reality

Evidence22
Adoption35
Hype gap+38
Incentives52
Confidence30
buildOne report1 publisher

A five-minute function ceiling pushes long agent loops off Vercel's Hobby tier

Fluid compute caps Hobby functions at five minutes and Pro at 800 seconds, so an agent working a long task list needs a queue or a different host. The cheap VPS escape hatches have repriced too.

Publishers:dev.to

Reality

Evidence45
Adoption
Not scored
Hype gap+25
Incentives65
Confidence40
buildOne report1 publisher

An audit of 120 published agent outputs turned up exactly one commitment

COGEXT's author pushed 150 samples from cookbooks, DEV posts and Hacker News through his own extractor. The unbiased 120 yielded one promise, and the 13 in the enriched set averaged 0.79 confidence with a single deadline between them.

Publishers:dev.to

Reality

Evidence38
Adoption10
Hype gap+24
Incentives85
Confidence58
buildOne report1 publisher

A broken three-line duration parser illustrates the limits of prompt-only repairs

In a dev.to walkthrough, miruky uses one bad rstrip call to separate five layers of agent engineering. Which layer do you change when a repair passes all three examples and still accepts 1e3s?

Publishers:dev.to

Reality

Evidence70
Adoption
Not scored
Hype gap−5
Incentives20
Confidence58
buildOne report1 publisher

Taabi's alerting agent compiles an English sentence into a rule document a plain engine executes

On the platform behind taabi Nexus, the model's only output is a validated rule document, and the code that dials a driver's intercom sits behind a seven-day replay, a role check and one person's approval.

Publishers:dev.to

Reality

Evidence58
Adoption24
Hype gap−12
Incentives62
Confidence55
buildOne report1 publisher

Foundry's Toolbox pins the MCP allow-list that a server can otherwise redefine at any time

MCP's discoverability puts the tool schema and the description text on the server side of the connection, so Foundry's Toolbox holds the credentials and the allow-list that decide what an agent accepts.

Publishers:dev.to

Reality

Evidence32
Adoption38
Hype gap+14
Incentives62
Confidence44

Earlier coverage

  1. AWS puts agent evaluation on OpenTelemetry, and on exactly three span roles

    Build · August 26, 2026 · Confirmed2 publishers