Skip to content

landing page#789

Merged
Lauren Hirata Singh (lnhsingh) merged 11 commits intomainfrom
landing
Oct 9, 2025
Merged

landing page#789
Lauren Hirata Singh (lnhsingh) merged 11 commits intomainfrom
landing

Conversation

@lnhsingh
Copy link
Copy Markdown
Collaborator

@lnhsingh Lauren Hirata Singh (lnhsingh) commented Oct 8, 2025

Overview

Adds a general Home page

Type of change

Type: Fix

Checklist

  • I have read the contributing guidelines
  • 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

Additional notes

Copilot AI review requested due to automatic review settings October 8, 2025 17:03
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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
Comment thread src/index.mdx Outdated
mode: "custom"
---

[NEED COPY FOR HERE]
Copy link

Copilot AI Oct 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's a placeholder comment that needs to be replaced with actual content. This should contain introductory text for the landing page.

Suggested change
[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.
Copilot uses AI. Check for mistakes.
Comment thread src/index.mdx Outdated
href="/langsmith/prompt-engineering"
icon="terminal"
>
Iterate on prompts with automatic version contol and collaboration features.
Copy link

Copilot AI Oct 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Corrected spelling of 'contol' to 'control'.

Suggested change
Iterate on prompts with automatic version contol and collaboration features.
Iterate on prompts with automatic version control and collaboration features.
Copilot uses AI. Check for mistakes.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Oct 8, 2025

Preview ID generated: preview-landin-1759943050-adc3cb2

Copy link
Copy Markdown
Collaborator

@eyurtsev Eugene Yurtsev (eyurtsev) left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice

Eugene Yurtsev (eyurtsev) added a commit that referenced this pull request Oct 8, 2025
## 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 -->
@github-actions github-actions Bot added python For content related to the Python version of LangChain projects javascript docs-infra labels Oct 8, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Oct 8, 2025

Preview ID generated: preview-landin-1759948704-0733793

Comment thread src/smart-logo-navigation.js Outdated
Co-authored-by: Hunter Lovell <40191806+hntrl@users.noreply.github.com>
Copilot AI review requested due to automatic review settings October 8, 2025 19:03
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

Comment thread src/index.mdx Outdated
href="/langsmith/prompt-engineering"
icon="terminal"
>
Iterate on prompts with automatic version contol and collaboration features.
Copy link

Copilot AI Oct 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Corrected spelling of 'contol' to 'control'.

Suggested change
Iterate on prompts with automatic version contol and collaboration features.
Iterate on prompts with automatic version control and collaboration features.
Copilot uses AI. Check for mistakes.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Oct 8, 2025

Preview ID generated: preview-landin-1759950247-cb3cc3b

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Oct 8, 2025

Preview ID generated: preview-landin-1759953108-c21f414

Copilot AI review requested due to automatic review settings October 8, 2025 19:52
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Comment thread src/index.mdx Outdated
# The agent engineering platform for developers building reliable agents

# Frameworks
[NEED COPY FOR HERE]
Copy link

Copilot AI Oct 8, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Placeholder text should be replaced with actual content before merging.

Suggested change
[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.
Copilot uses AI. Check for mistakes.
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Oct 8, 2025

Preview ID generated: preview-landin-1759953209-2b315e2

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Oct 8, 2025

Preview ID generated: preview-landin-1759959035-8289a15

Copilot AI review requested due to automatic review settings October 9, 2025 16:16
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

Comment thread src/index.mdx
sidebarTitle: Home
description: "The platform for reliable agents"
mode: "wide"
title:
Copy link

Copilot AI Oct 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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'.

Suggested change
title:
title: LangChain Platform
Copilot uses AI. Check for mistakes.
Comment thread src/index.mdx Outdated
# The platform for developers building reliable agents

# Frameworks
Tools for every step of the agent development lifecycle-- built to unlock powerful AI in production.
Copy link

Copilot AI Oct 9, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Replace double dash '--' with proper em dash '—' for better typography.

Suggested change
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.
Copilot uses AI. Check for mistakes.
Mason Daugherty (mdrxy) pushed a commit that referenced this pull request Oct 14, 2025
## 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 -->
Mason Daugherty (mdrxy) pushed a commit that referenced this pull request Oct 14, 2025
## 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 -->
Lauren Hirata Singh (lnhsingh) added a commit that referenced this pull request Oct 14, 2025
## 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 -->
Lauren Hirata Singh (lnhsingh) added a commit that referenced this pull request Oct 15, 2025
## 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 -->
Asamu David (phvash) added a commit that referenced this pull request Oct 15, 2025
## 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 -->
Eugene Yurtsev (eyurtsev) pushed a commit that referenced this pull request Oct 15, 2025
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 -->
Asamu David (phvash) added a commit that referenced this pull request Oct 15, 2025
## 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 -->
Lauren Hirata Singh (lnhsingh) added a commit that referenced this pull request Oct 15, 2025
## 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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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>
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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>
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
…n-ai#584)

## Overview
<!-- Brief description of what documentation is being added/updated -->
* update usage instructions to account for new organization-scoped API
keys:

![Org-Scoped-API-2](https://github.com/user-attachments/assets/004fb25f-ca5d-486d-bb5f-52c54fd722a2)

## 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>
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
…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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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>
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
…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>
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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>
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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 -->
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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>
YongJie Wu (TBice123123) pushed a commit to TBice123123/docs that referenced this pull request Oct 16, 2025
## 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)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-infra javascript labs langchain For docs changes to LangChain langgraph For docs changes to LangGraph oss python For content related to the Python version of LangChain projects

4 participants