[//]: # (dependabot-start) ⚠️ **Dependabot is rebasing this PR** ⚠️ Rebasing might not happen immediately, so don't worry if this takes some time. Note: if you make any changes to this PR yourself, they will take precedence over the rebase. --- [//]: # (dependabot-end) Bumps [filelock](https://github.com/tox-dev/py-filelock) from 3.20.3 to 3.32.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/tox-dev/py-filelock/releases">filelock's releases</a>.</em></p> <blockquote> <h2>3.32.5</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <ul> <li>🧪 test(fork): report where a stalled fork stops by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/715">tox-dev/filelock#715</a></li> <li>📝 docs: say that mode is read-only in the thread-local section by <a href="https://github.com/Gares95"><code>@Gares95</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/716">tox-dev/filelock#716</a></li> <li>🐛 fix(lease): clear token after failed acquire by <a href="https://github.com/lprnmns"><code>@lprnmns</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/721">tox-dev/filelock#721</a></li> </ul> <h2>New Contributors</h2> <ul> <li><a href="https://github.com/lprnmns"><code>@lprnmns</code></a> made their first contribution in <a href="https://redirect.github.com/tox-dev/filelock/pull/721">tox-dev/filelock#721</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/tox-dev/filelock/compare/3.32.4...3.32.5">https://github.com/tox-dev/filelock/compare/3.32.4...3.32.5</a></p> <h2>3.32.4</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <ul> <li>🐛 fix: retry transient denials on open and claim read by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/705">tox-dev/filelock#705</a></li> <li>🧪 test: deflake six scheduled-run failures by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/704">tox-dev/filelock#704</a></li> <li>🧪 test: cover a reclaimed private record for real by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/706">tox-dev/filelock#706</a></li> <li>🧪 test(fork): fork once the event loop has closed by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/714">tox-dev/filelock#714</a></li> <li>🔧 chore: batch dependency updates weekly on Tuesday by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/713">tox-dev/filelock#713</a></li> <li>escape the hostname every marker publishes by <a href="https://github.com/dxbjavid"><code>@dxbjavid</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/709">tox-dev/filelock#709</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/tox-dev/filelock/compare/3.32.3...3.32.4">https://github.com/tox-dev/filelock/compare/3.32.3...3.32.4</a></p> <h2>3.32.3</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <ul> <li>🧪 test(strict): deflake close-fault injections on graalpy by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/697">tox-dev/filelock#697</a></li> <li>📄 docs: publish llms.txt from the docs build by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/700">tox-dev/filelock#700</a></li> <li>🐛 fix(fork): survive audit events during interpreter shutdown by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/703">tox-dev/filelock#703</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/tox-dev/filelock/compare/3.32.2...3.32.3">https://github.com/tox-dev/filelock/compare/3.32.2...3.32.3</a></p> <h2>3.32.2</h2> <!-- raw HTML omitted --> <h2>What's Changed</h2> <ul> <li>Fix test failures on NetBSD (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/689">#689</a>) by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/693">tox-dev/filelock#693</a></li> <li>🧪 test(soft-rw): deflake writer phase-2 peer-marker test by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/694">tox-dev/filelock#694</a></li> <li>hand back the claim when a heartbeat thread fails to start by <a href="https://github.com/dxbjavid"><code>@dxbjavid</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/691">tox-dev/filelock#691</a></li> <li>🧪 test(unix): deflake sticky-bit concurrent-unlink on graalpy by <a href="https://github.com/gaborbernat"><code>@gaborbernat</code></a> in <a href="https://redirect.github.com/tox-dev/filelock/pull/695">tox-dev/filelock#695</a></li> </ul> <p><strong>Full Changelog</strong>: <a href="https://github.com/tox-dev/filelock/compare/3.32.1...3.32.2">https://github.com/tox-dev/filelock/compare/3.32.1...3.32.2</a></p> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/tox-dev/filelock/blob/main/docs/changelog.rst">filelock's changelog</a>.</em></p> <blockquote> <p>########### Changelog ###########</p> <p>.. towncrier-draft-entries:: Unreleased</p> <p>.. towncrier release notes start</p> <hr /> <p>3.32.5 (2026-08-31)</p> <hr /> <ul> <li><code>SoftFileLease.token</code> and <code>AsyncSoftFileLease.token</code> now read <code>None</code> after a failed acquisition, so a contender turned away by a live holder no longer reports a token for a claim it never published. :pr:<code>721</code></li> <li>Document that <code>mode</code> has no setter: unlike <code>poll_interval</code>, <code>timeout</code>, <code>blocking</code> and <code>lifetime</code>, it is fixed at construction and <code>lock.mode = ...</code> raises <code>AttributeError</code>. :pr:<code>716</code></li> </ul> <hr /> <p>3.32.4 (2026-08-23)</p> <hr /> <ul> <li><code>StrictSoftFileLock</code> always retries a claim read whose first attempt reports the claim as pending, so a first read that itself outlasts the retry grace no longer fails closed on a claim it could have read. :pr:<code>705</code></li> <li><code>WindowsFileLock</code> waits out a transient <code>STATUS_ACCESS_DENIED</code> from <code>NtCreateFile</code> for up to half a second before raising <code>PermissionError</code>, since a peer unlinking the lock file as it releases can answer that for a moment; a real denial still fails fast. :pr:<code>705</code></li> <li>Every lock class now escapes the hostname it publishes, so a host whose <code>socket.gethostname()</code> carries a space, a newline or a byte outside UTF-8 no longer writes a marker it reads back as malformed. Such a host used to lose a held <code>SoftReadWriteLock</code> read slot to a peer and could not take a write slot or a <code>StrictSoftFileLock</code> at all. :pr:<code>709</code></li> </ul> <hr /> <p>3.32.3 (2026-08-13)</p> <hr /> <ul> <li>The fork-safety audit hook no longer prints <code>Exception ignored in audit hook</code> with a <code>TypeError</code> when an audit event fires during interpreter shutdown, after CPython has already cleared the module globals. :pr:<code>701</code></li> </ul> <hr /> <p>3.32.2 (2026-07-29)</p> <hr /> <ul> <li>A <code>SoftReadWriteLock</code> or <code>SoftFileLease</code> acquire whose heartbeat thread fails to start now unlinks its marker and hands the claim back, instead of leaving an unrefreshed marker a peer takes while the caller believes it still holds the lock. :pr:<code>691</code></li> </ul> <hr /> <p>3.32.1 (2026-07-26)</p> <hr /> <ul> <li>Canceling an <code>AsyncSoftReadWriteLock</code> acquire now releases the claim instead of leaking a marker whose heartbeat wedges every contender. :pr:<code>686</code></li> </ul> <!-- raw HTML omitted --> </blockquote> <p>... (truncated)</p> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/tox-dev/filelock/commit/1585dfef9355a5c77d4a9498cc34d3a98056fdb9"><code>1585dfe</code></a> Release 3.32.5</li> <li><a href="https://github.com/tox-dev/filelock/commit/00177c32686e60bc5ef9875b5841867ea08d4558"><code>00177c3</code></a> 🐛 fix(lease): clear token after failed acquire (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/721">#721</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/5aeb9b6a5fe1e86dcb1c44a927aefffd607b17b0"><code>5aeb9b6</code></a> 📝 docs: say that mode is read-only in the thread-local section (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/716">#716</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/2634dd1dcc597b319770df027491f16d07662952"><code>2634dd1</code></a> [pre-commit.ci] pre-commit autoupdate (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/720">#720</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/37dccf0276f6db1520db9e3482fdf0446c14276e"><code>37dccf0</code></a> 🧪 test(fork): report where a stalled fork stops (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/715">#715</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/cb493d6684ed5d2f923384633c86fef12e29bce2"><code>cb493d6</code></a> Release 3.32.4</li> <li><a href="https://github.com/tox-dev/filelock/commit/fe07a11a7133ddd104322eb79d3c59f966b4ba15"><code>fe07a11</code></a> escape the hostname every marker publishes (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/709">#709</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/232732f49ed9d230802f527ad60b5d5ad1202a56"><code>232732f</code></a> 🔧 chore: batch dependency updates weekly on Tuesday (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/713">#713</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/2966eb51431ff8ac19eb2bec4e0b67c328437c48"><code>2966eb5</code></a> 🧪 test(fork): fork once the event loop has closed (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/714">#714</a>)</li> <li><a href="https://github.com/tox-dev/filelock/commit/61511ebc1cc5d40b28f8584f1078e63f2d63fb02"><code>61511eb</code></a> build(deps): bump astral-sh/setup-uv from 10.0.0 to 10.0.1 (<a href="https://redirect.github.com/tox-dev/py-filelock/issues/712">#712</a>)</li> <li>Additional commits viewable in <a href="https://github.com/tox-dev/py-filelock/compare/3.20.3...3.32.5">compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/langchain-ai/langchain/network/alerts). </details> Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
The agent engineering platform.
LangChain is a framework for building agents and LLM-powered applications. It helps you chain together interoperable components and third-party integrations to simplify AI application development — all while future-proofing decisions as the underlying technology evolves.
Tip
Just getting started? Check out Deep Agents — a higher-level package built on LangChain for agents that have built-in capabilities for common usage patterns such as planning, subagents, file system usage, and more.
Quickstart
uv add langchain
from langchain.chat_models import init_chat_model
model = init_chat_model("openai:gpt-5.5")
result = model.invoke("Hello, world!")
If you're looking for more advanced customization or agent orchestration, check out LangGraph, our framework for building controllable agent workflows.
For an equivalent JS/TS library, check out LangChain.js.
Tip
For developing, debugging, and deploying AI agents and LLM applications, see LangSmith.
LangChain ecosystem
While the LangChain framework can be used standalone, it also integrates seamlessly with any LangChain product, giving developers a full suite of tools when building LLM applications.
- Deep Agents — Build agents that can plan, use subagents, and leverage file systems for complex tasks
- LangGraph — Build agents that can reliably handle complex tasks with our low-level agent orchestration framework
- Integrations — Chat & embedding models, tools & toolkits, and more
- LangSmith — Agent evals, observability, and debugging for LLM apps
- LangSmith Deployment — Deploy and scale agents with a purpose-built platform for long-running, stateful workflows
Why use LangChain?
LangChain helps developers build applications powered by LLMs through a standard interface for models, embeddings, vector stores, and more.
- Real-time data augmentation — Easily connect LLMs to diverse data sources and external/internal systems, drawing from LangChain's vast library of integrations with model providers, tools, vector stores, retrievers, and more
- Model interoperability — Swap models in and out as your engineering team experiments to find the best choice for your application's needs. As the industry frontier evolves, adapt quickly — LangChain's abstractions keep you moving without losing momentum
- Rapid prototyping — Quickly build and iterate on LLM applications with LangChain's modular, component-based architecture. Test different approaches and workflows without rebuilding from scratch, accelerating your development cycle
- Production-ready features — Deploy reliable applications with built-in support for monitoring, evaluation, and debugging through integrations like LangSmith. Scale with confidence using battle-tested patterns and best practices
- Vibrant community and ecosystem — Leverage a rich ecosystem of integrations, templates, and community-contributed components. Benefit from continuous improvements and stay up-to-date with the latest AI developments through an active open-source community
- Flexible abstraction layers — Work at the level of abstraction that suits your needs — from high-level chains for quick starts to low-level components for fine-grained control. LangChain grows with your application's complexity
Resources
- Documentation — conceptual overviews and guides
- LangChain ecosystem overview — how LangChain, LangGraph, and Deep Agents fit together
- API reference — complete reference for all public classes, functions, and types
- Discussions — community forum for technical questions, ideas, and feedback
- LangChain Academy — comprehensive, free courses on LangChain libraries and products, made by the LangChain team
- Contributing Guide — how to contribute and find good first issues
- Code of Conduct — community guidelines and standards