Skip to main content
Welcome! Thank you for your interest in contributing. LangChain has helped form the largest developer community in generative AI, and we’re always open to new contributors. Whether you’re fixing bugs, adding features, improving documentation, or sharing feedback, your involvement helps make LangChain and LangGraph better for everyone 🦜❤️

​
Ways to contribute

Found a bug? Please help us fix it by following these steps:
1

Search

Check if the issue already exists in our GitHub Issues for the respective repo:

LangChain

Issues

LangGraph

Issues

Deep Agents

Issues
2

Create issue

If no issue exists, create a new one. When writing, be sure to follow the template provided and to include a minimal, reproducible, example. Attach any relevant labels to the final issue once created. If a project maintainer is unable to reproduce the issue, it is unlikely to be addressed in a timely manner.
3

Wait

A project maintainer will triage the issue and may ask for additional information. Please be patient as we manage a high volume of issues. Do not bump the issue unless you have new information to provide.
If you are adding an issue, please try to keep it focused on a single topic. If two issues are related, or blocking, please link them rather than combining them. For example:
This issue is blocked by #123 and related to #456.
Have an idea for a new feature or enhancement?
1

Search

Search the issues for the respective repository for existing feature requests:

LangChain

Issues

LangGraph

Issues

Deep Agents

Issues
2

Discuss

If no requests exist, start a new discussion under the relevant category so that project maintainers and the community can provide feedback.
3

Describe

Be sure to describe the use case and why it would be valuable to others. If possible, provide examples or mockups where applicable. Outline test cases that should pass.
Documentation improvements are welcome! We strive to keep our docs clear and comprehensive, and your perspective can make a big difference.

How to propose changes to the documentation

Guide
With a large userbase, it can be hard for our small team to keep up with all the feature requests and bug fixes. If you have the skills and time, we would love your help!

How to make your first Pull Request

Guide
If you start working on an issue, please assign it to yourself or ask a maintainer to do so. This helps avoid duplicate work.If you are looking for something to work on, check out the issues labeled “good first issue” or “help wanted” in our repos:

LangChain

Labels

LangGraph

Labels

Deep Agents

Labels

​
Pull request requirements

All pull requests must link to an issue or discussion where a solution has been approved by a maintainer. PRs without prior approval will be closed.
All pull requests should demonstrate meaningful effort and contextual understanding. If the effort required to create a pull request is less than the effort required for maintainers to review it, that contribution should not be submitted. Low-effort drive-by contributions—regardless of how they are produced—often miss the mark in terms of contextual relevance, accuracy, and quality. Mass automated contributions represent a denial-of-service attack on our human effort. The following requirements must be met for all external pull requests:
  • The pull request must link to an issue or discussion where a solution has been approved by a maintainer.
  • The pull request must fill in the repository’s pull request template.
Maintainers reserve the right to close PRs without comment if these requirements are not met. We will close pull requests and issues that appear to be low-effort spam.

​
Language policy

All contributions—issues, pull requests, code reviews, and discussions—must be in English. This keeps communications accessible and searchable across our global contributor base. If English isn’t your first language, don’t worry. We value clear communication over perfect grammar, and translation tools are welcome.
Edit this page on GitHub or file an issue.
Connect these docs to Claude, VSCode, and more via MCP for real-time answers.