Skip to content

Conversation

@sydney-runkle
Copy link
Contributor

@sydney-runkle sydney-runkle commented Dec 11, 2025

  • Rename supervisor to subagents (@sydney-runkle)
  • Review language for each pattern for accuracy / inaccuracy
  • State machine (owner @eugene)
    • More explanation about handoffs
    • Explanation about conversation fluidity
    • Expanation about handoffs from a subagent (i.e., jumping to parent)
    • Relax tip statement
  • Skills potentially include a bit of information about llms.txt (as it's the same idea)
  • Stateless router (owner @sydney-runkle):
    • Explain how to include conversation history as context (this doesn't mean it's stateful)
  • Custom workflow (owner @sydney-runkle)
    • Intro shouldn't suggest it's only for sequential pipelines (explain that branching / loops agentic logic is supported)
    • Refine example as agents typically need tools (otherwise it's just an LLM call)

current preview: https://langchain-5e9cc07a-preview-srtues-1765892940-6d4394f.mintlify.app/oss/python/langchain/multi-agent

@github-actions github-actions bot added ci langchain For docs changes to LangChain oss internal labels Dec 11, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Dec 11, 2025

❌ Import check failed

This PR contains imports from langchain_core that should be imported from langchain instead.

Detailed issues
Analyzing diff for import issues...
 Found 2 import issues:

File: src/oss/langchain/multi-agent.mdx
Line: 581
Issue: Import from langchain.tools instead of langchain_core.tools
Current:   from langchain_core.tools import tool
Suggested: from langchain.tools import tool
--------------------------------------------------------------------------------
File: src/oss/langchain/multi-agent.mdx
Line: 833
Issue: Import from langchain.tools instead of langchain_core.tools
Current:   from langchain_core.tools import tool
Suggested: from langchain.tools import tool
--------------------------------------------------------------------------------

 Found 2 import issues that need to be fixed.

Why this is a problem

The langchain package re-exports many modules and classes from langchain_core. When possible, imports should use langchain instead of langchain_core for:

  • Better user experience (single import source)
  • Consistency across documentation
  • Reduced cognitive load for users

How to fix

Replace the imports as suggested above. For example:

  • from langchain_core.messages import HumanMessage
  • from langchain.messages import HumanMessage

🤖 Automated check

This check is based on the latest analysis of langchain re-exports from langchain_core.

@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765486358-912f048

## 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

(Internal team members only / optional): Create a preview deployment as
necessary 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
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765820423-8931177

Update the skills section
@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765828134-f4149c9

building out a custom rag pipeline that serves as a wnba q&a bot :)

this is not the most realistic rag example ever but more POC re
different node types. also thought about coding agent but oh my gosh we
need some variety in our docs! that's basic!!
@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765828453-2f2ac60

adding generic diagram and incorporating comments from
#1914
@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765833363-d855628

@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765843135-099791e

@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765844199-8abe3a7

## 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

(Internal team members only / optional): Create a preview deployment as
necessary 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
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765856935-95e32b4

* rename state machine -> handoffs
* redesign "why multi agent" section
  * using cards for some visual pop (we have a LOT of text)
  * adding the decision table
* consolidating "context eng" section into a tooltip
* subagents sectio reorg (sync vs async, # tools, inputs/outputs -- aka
context eng)
* collapsed some long code snippets
* we should consolidated content after the "why multi agent" cards,
there's a LOT of info
@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765896742-ef67260

@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765896949-28ad8dd

@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765898309-14ce191

Copy link
Collaborator

@lnhsingh lnhsingh left a comment

Choose a reason for hiding this comment

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

Nice job @sydney-runkle and @eyurtsev !!!!!

Co-authored-by: Lauren Hirata Singh <[email protected]>
@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765901258-9e41223

@github-actions
Copy link
Contributor

Mintlify preview ID generated: preview-srmult-1765902910-57c322e

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci internal langchain For docs changes to LangChain oss

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants