landing page#789
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR updates the main documentation landing page to reorganize the structure and content presentation. The changes shift from a framework/platform-based organization to a more user-focused structure that emphasizes open-source frameworks and LangSmith offerings.
- Reorganized the main sections from "Frameworks", "Platforms", "Experimental" to "Open-source frameworks" and "LangSmith offerings"
- Updated card descriptions to be more descriptive and user-focused
- Modified the layout mode from "wide" to "custom" and updated the page description
Reviewed Changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/index.mdx | Complete restructure of the landing page with new section organization, updated card content, and layout changes |
| src/docs.json | Removed the logo href redirect to allow the logo to link to the current landing page |
| mode: "custom" | ||
| --- | ||
|
|
||
| [NEED COPY FOR HERE] |
There was a problem hiding this comment.
There's a placeholder comment that needs to be replaced with actual content. This should contain introductory text for the landing page.
| [NEED COPY FOR HERE] | |
| Welcome to the LangChain documentation hub! Here you'll find resources, guides, and reference materials for building, evaluating, and deploying reliable AI agents and applications using LangChain and LangSmith. Explore our open-source frameworks and platform offerings to accelerate your agent engineering journey. |
| href="/langsmith/prompt-engineering" | ||
| icon="terminal" | ||
| > | ||
| Iterate on prompts with automatic version contol and collaboration features. |
There was a problem hiding this comment.
Corrected spelling of 'contol' to 'control'.
| Iterate on prompts with automatic version contol and collaboration features. | |
| Iterate on prompts with automatic version control and collaboration features. |
|
Preview ID generated: preview-landin-1759943050-adc3cb2 |
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
|
Preview ID generated: preview-landin-1759948704-0733793 |
Co-authored-by: Hunter Lovell <40191806+hntrl@users.noreply.github.com>
| href="/langsmith/prompt-engineering" | ||
| icon="terminal" | ||
| > | ||
| Iterate on prompts with automatic version contol and collaboration features. |
There was a problem hiding this comment.
Corrected spelling of 'contol' to 'control'.
| Iterate on prompts with automatic version contol and collaboration features. | |
| Iterate on prompts with automatic version control and collaboration features. |
|
Preview ID generated: preview-landin-1759950247-cb3cc3b |
|
Preview ID generated: preview-landin-1759953108-c21f414 |
| # The agent engineering platform for developers building reliable agents | ||
|
|
||
| # Frameworks | ||
| [NEED COPY FOR HERE] |
There was a problem hiding this comment.
Placeholder text should be replaced with actual content before merging.
| [NEED COPY FOR HERE] | |
| Build, evaluate, and deploy robust AI agents with our open-source frameworks and LangSmith platform. Explore tools and resources to accelerate your agent development journey. |
|
Preview ID generated: preview-landin-1759953209-2b315e2 |
|
Preview ID generated: preview-landin-1759959035-8289a15 |
| sidebarTitle: Home | ||
| description: "The platform for reliable agents" | ||
| mode: "wide" | ||
| title: |
There was a problem hiding this comment.
The title field in the frontmatter is empty. This should contain a descriptive title for the homepage, such as 'LangChain Documentation Home' or 'LangChain Platform'.
| title: | |
| title: LangChain Platform |
| # The platform for developers building reliable agents | ||
|
|
||
| # Frameworks | ||
| Tools for every step of the agent development lifecycle-- built to unlock powerful AI in production. |
There was a problem hiding this comment.
Replace double dash '--' with proper em dash '—' for better typography.
| Tools for every step of the agent development lifecycle-- built to unlock powerful AI in production. | |
| Tools for every step of the agent development lifecycle— built to unlock powerful AI in production. |
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview Add guide to trouble datadog instrumentation ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
The execution of the full example failed; the graphBuilder approval node is missing edge dependencies. ## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview move DD troubleshooting instruction from note to main paragraph ## Type of change **Type:** formatting ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes #123" or "fixes #123" or "resolves #123" For regular references without auto-closing, just use: - "#123" or "See issue #123" Examples: - closes #456 (will auto-close issue #456 when PR is merged) - See #789 for context (will reference but not auto-close issue #789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview - Edited prose / format of LangChain overview, Install, Quickstart, Philosophy, and Agents pages ## Type of change **Type:** Update existing ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - [x] I have gotten approval from the relevant reviewers - [x] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
## Overview - removing an incorrect assertion ## Type of change **Type:** Fix typo ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - [ ] I have gotten approval from the relevant reviewers - [ ] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: langchain-ai/langchainjs#8963 <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - [ ] I have gotten approval from the relevant reviewers - [ ] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> --------- Co-authored-by: Lauren Hirata Singh <lauren@langchain.dev>
## Overview Added banner for Academy course publicity ## Type of change **Type:** Added banner for Academy course publicity ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - [ ] I have gotten approval from the relevant reviewers - [ ] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview - Update Copilot instructions for better reviews - Move conceptual guides to `/oss/concepts` dir and update cross-references - Add info the the README about code language fences ## Type of change **Type:** Update existing docs ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - [x] I have gotten approval from the relevant reviewers - [x] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
…n-ai#584) ## Overview <!-- Brief description of what documentation is being added/updated --> * update usage instructions to account for new organization-scoped API keys:  ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: ent-114 - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - [ ] I have gotten approval from the relevant reviewers - [x] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> --------- Co-authored-by: Kathryn May <44557882+katmayb@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
## Overview - Move Production content into snippets where possible to reduce duplicated content - Preview: https://langchain-5e9cc07a-preview-produc-1758226889-031b27c.mintlify.app/oss/python/langchain/overview ## Type of change **Type:** Update existing ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - [ ] I have gotten approval from the relevant reviewers - [x] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview <!-- Brief description of what documentation is being added/updated --> Fix typos in context-engineering.mdx under OSS LangChain ## Type of change **Type:** Fix typo ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: N/A - Feature PR: N/A <!-- For LangChain employees, if applicable: --> - Linear issue: N/A - Slack thread: N/A ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - [ ] I have gotten approval from the relevant reviewers - [ ] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
…ai#602) ## Overview Changed in helm, need to match ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - [ ] I have gotten approval from the relevant reviewers - [ ] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview <!-- Brief description of what documentation is being added/updated --> Fixed uv command. `uv add langchain@pre` seems to be an incorrect command, and the uv equivalent of `pip install --pre` appears to be `uv add --prerelease=allow`. ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - [x] I have gotten approval from the relevant reviewers - [ ] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** New documentation page ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: fixes langchain-ai#544 ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - [ ] I have gotten approval from the relevant reviewers - [ ] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> This PR adds Moorcheh as a supported vector store integration, providing users with documentation on how to: - Install and configure Moorcheh - Use Moorcheh for vector storage and retrieval - Integrate Moorcheh with LangChain workflows Co-authored-by: Lauren Hirata Singh <lauren@langchain.dev>
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
…ai#628) ## Overview Update langsmith self hosted documentation with a troubleshooting guide when running in environments with AquaSec. ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> --------- Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: Kathryn May <44557882+katmayb@users.noreply.github.com>
## Overview <!-- Brief description of what documentation is being added/updated --> * Feedback from OIN review: be explicit about which fields are optional based on whether or not the application is for SCIM, SAML, OIDC, or a combination ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: part of ent-100 - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> --------- Co-authored-by: Kathryn May <44557882+katmayb@users.noreply.github.com>
## Overview <!-- Brief description of what documentation is being added/updated --> Fix typos in rag.mdx under OSS LangChain ## Type of change **Type:** Fix typo ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: N/A - Feature PR: N/A <!-- For LangChain employees, if applicable: --> - Linear issue: N/A - Slack thread: N/A ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - [ ] I have gotten approval from the relevant reviewers - [ ] (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview Fix subset of broken links. Still 368 to go ## Type of change **Type:** Bug fix ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview <!-- Brief description of what documentation is being added/updated --> Add the documentation for the new [perigon-langchain](https://github.com/goperigon/langchain-perigon) integration. The Perigon API suite provides fast, structured access to global news and events, helping you build real-time, data-driven products. Whether you're tracking emerging risks, surfacing relevant articles, or uncovering key insights, Perigon gives you the tools to do it programmatically. ## Type of change **Type:** New documentation page ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> You can learn more about Perigon from the following links: 1. Perigon workspace: https://perigon.io 2. Perigon for developers: https://dev.perigon.io
## Overview <!-- Brief description of what documentation is being added/updated --> ## Type of change **Type:** [Replace with: New documentation page / Update existing documentation / Fix typo/bug/link/formatting / Remove outdated content / Other] ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers -->
## Overview <!-- Brief description of what documentation is being added/updated --> Update Okta OIDC configuration section to make it clear it is through Helm/Docker ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - GitHub issue: - Feature PR: <!-- For LangChain employees, if applicable: --> - Linear issue: part of ent-100 - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [ ] I have read the [contributing guidelines](README.md) - [ ] I have tested my changes locally using `docs dev` - [ ] All code examples have been tested and work correctly - [ ] I have used **root relative** paths for internal links - [ ] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml) ## Additional notes <!-- Any other information that would be helpful for reviewers --> --------- Co-authored-by: Kathryn May <44557882+katmayb@users.noreply.github.com>
## Overview Fix the perigon langchain docs internal links. ## Type of change **Type:** Update existing documentation ## Related issues/PRs <!-- Link to related issues, feature PRs, or discussions (if applicable) To automatically close an issue when this PR is merged, use closing keywords: - "closes langchain-ai#123" or "fixes langchain-ai#123" or "resolves langchain-ai#123" For regular references without auto-closing, just use: - "langchain-ai#123" or "See issue langchain-ai#123" Examples: - closes langchain-ai#456 (will auto-close issue langchain-ai#456 when PR is merged) - See langchain-ai#789 for context (will reference but not auto-close issue langchain-ai#789) --> - See langchain-ai#627 <!-- For LangChain employees, if applicable: --> - Linear issue: - Slack thread: ## Checklist <!-- Put an 'x' in all boxes that apply --> - [x] I have read the [contributing guidelines](README.md) - [x] I have tested my changes locally using `docs dev` - [x] All code examples have been tested and work correctly - [x] I have used **root relative** paths for internal links - [x] I have updated navigation in `src/docs.json` if needed - I have gotten approval from the relevant reviewers - (Internal team members only / optional) I have created a preview deployment using the [Create Preview Branch workflow](https://github.com/langchain-ai/docs/actions/workflows/create-preview-branch.yml)
Overview
Adds a general Home page
Type of change
Type: Fix
Checklist
docs devsrc/docs.jsonif neededAdditional notes