Skip to main content

Welcome Contributors

Hi there! Thank you for your interest in contributing to LangChain. As an open-source project in a fast developing field, we are extremely open to contributions, whether they involve new features, improved infrastructure, better documentation, or bug fixes.

Tutorials​

More coming soon! We are working on tutorials to help you make your first contribution to the project.

How-to Guides​

  • Documentation: Help improve our docs, including this one!
  • Code: Help us write code, fix bugs, or improve our infrastructure.
  • Integrations: Help us integrate with your favorite vendors and tools.
  • Standard Tests: Ensure your integration passes an expected set of tests.

Reference​

Community​

💭 GitHub Discussions​

We have a discussions page where users can ask usage questions, discuss design decisions, and propose new features.

If you are able to help answer questions, please do so! This will allow the maintainers to spend more time focused on development and bug fixing.

🚩 GitHub Issues​

Our issues page is kept up to date with bugs, improvements, and feature requests.

There is a taxonomy of labels to help with sorting and discovery of issues of interest. Please use these to help organize issues.

If you start working on an issue, please assign it to yourself.

If you are adding an issue, please try to keep it focused on a single, modular bug/improvement/feature. If two issues are related, or blocking, please link them rather than combining them.

We will try to keep these issues as up-to-date as possible, though with the rapid rate of development in this field some may get out of date. If you notice this happening, please let us know.

📢 Community Slack​

We have a community slack where you can ask questions, get help, and discuss the project with other contributors and users.

🙋 Getting Help​

Our goal is to have the simplest developer setup possible. Should you experience any difficulty getting setup, please ask in community slack or open a discussion on GitHub.

In a similar vein, we do enforce certain linting, formatting, and documentation standards in the codebase. If you are finding these difficult (or even just annoying) to work with, feel free to ask in community slack!

Was this page helpful?