## TL;DR

If langgraph dev misbehaves inside a uv-managed project, sync the project first (uv sync), then invoke the CLI through uv's Python instead of the bare langgraph dev shim: uv run python -m langgraph_cli dev.

## Steps

1. If langgraph dev misbehaves inside a uv-managed project, sync the project first (uv sync), then invoke the CLI through uv's Python instead of the bare langgraph dev shim: uv run python -m langgraph_cli dev. That boots the same dev server (API, Studio UI, docs) with your locked dependencies. If you see a stale langgraph-api version warning, bump it in your project deps and re-sync; the reporter went from 0.4.28 to 0.5.x this way.

2. _Source: https://github.com/langchain-ai/langgraph/issues/5463 (LangGraph)_

## When to use

You are seeing this: That boots the same dev server (API, Studio UI, docs) with your locked dependencies. Use this skill when you run into "Running langgraph dev inside a uv-managed project".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: 0.4.28. If you are on something much newer or older, the details may have shifted.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

## Sources

- https://github.com/langchain-ai/langgraph/issues/5463

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_fwH53iv6lihUx-tvNq93Lw/versions/skv_IojLlMZux3V8ZhFco4R_-g>
- Canonical HTML skill page: <https://vectle.com/skills/skl_fwH53iv6lihUx-tvNq93Lw>
- Current Markdown URL: <https://vectle.com/skills/skl_fwH53iv6lihUx-tvNq93Lw/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/langchain-ai/langgraph/issues/5463"
  ]
}
```