-
Notifications
You must be signed in to change notification settings - Fork 2.3k
change langchain quickstart #3531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 5 commits
ce2d9d0
917d447
71e7e9e
98a4101
3e82a6b
28e2ac3
78bdc45
4ae5151
db9e102
c6b8f51
50d7109
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -12,6 +12,8 @@ LangChain is driven by a few core beliefs: | |
| - It is still very early on in that transformation. | ||
| - While it's easy to build a prototype of those agentic applications, it's still really hard to build agents that are reliable enough to put into production. | ||
|
|
||
| Today developers can choose how they build agents: [LangChain](/oss/langchain/overview) for flexibility and control, or [Deep Agents](/oss/langchain/overview) for a batteries-included experience with built-in planning, filesystem tools, subagents, and context management. Both are built on [LangGraph](/oss/langgraph/overview). | ||
|
|
||
| With LangChain, we have two core focuses: | ||
|
|
||
| <Steps> | ||
|
|
@@ -129,3 +131,9 @@ Given the constant rate of change in the field, LangChain has also evolved over | |
|
|
||
| 2. A standard message content format: Model APIs evolved from returning messages with a simple content string to more complex output types - reasoning blocks, citations, server-side tool calls, etc. LangChain evolved its message formats to standardize these across providers. | ||
| </Update> | ||
|
|
||
| <Update label="2026-03-15"> | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This date is incorrect; 0.0.1 was published Jul 29, 2025
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I based this on when we announced it to the world. Though it's also possible we don't want this here at all until v1.0. vivek (@vtrivedy) what do you think? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. i think fine to remove date
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. vivek (@vtrivedy) that's not an option, the page uses dates in this timeline.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. we can
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'll put 0.5.3 with it, I think that makes most sense
npentrel marked this conversation as resolved.
Outdated
|
||
| **Deep Agents is released** as an open-source agent harness built on LangGraph. | ||
|
|
||
| While LangChain provides flexible building blocks for custom agent architectures, [Deep Agents](/oss/langchain/overview) offers a batteries-included option for complex, long-running tasks like research and coding. It adds built-in planning tools, a virtual filesystem with pluggable backends (in-memory, disk, LangGraph store, sandboxes), subagent spawning for context isolation, and a terminal CLI. Use Deep Agents for more autonomous agents with predefined tools; use LangChain for full control over your agent architecture. | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not sure we should mention CLI
npentrel marked this conversation as resolved.
Outdated
|
||
| </Update> | ||
Uh oh!
There was an error while loading. Please reload this page.