langchain 1.0 – Feedback Wanted!

[eyurtsev]

(Originally posted to the new LangChain forum! -- Join the discussion here)

Hey everyone,

We’re getting ready to release version 1.0 of the langchain package, and we’d love your input before it goes live.

Over the past few months, we’ve been rethinking the structure of the package to make it simpler, more focused, and easier to use—especially as agentic workflows become more common in real-world applications.

💡 Here’s What We’re Thinking

We want langchain 1.0 to offer a clean, intuitive starting point focused on the most-used patterns and abstractions:

• Re-export core primitives like messages, tools, and prompts from langchain_core so users don’t need to learn multiple packages up front.

• Expose common building blocks—agents, chains, mcp (model-context-protocol), retrievers—at the top level to make discovery and usage easier.

• Simplified onboarding with:

  • Streamlined access to models and embeddings through universal init helpers:

    • init_chat_model to quickly get a chat model running
    • init_embeddings to easily configure embeddings

  • Prebuilt workflows for common use cases like RAG, summarization, SQL, and more — so you can hit the ground running

We’re also removing deprecated modules to reduce clutter and improve usability.

🔧 Adding LangGraph as a dependency

The langchain package will depend on:

• langchain-core – for core abstractions like chat models, messages, tools, and prompts
• langgraph – for agent workflow support

📚 Docs

We’re actively working on improving the documentation experience across our open-source ecosystem—including langchain, langgraph, and more.

Our goals are to:

• Consolidate documentation to reduce duplication and minimize the number of separate docs sites
• Improve global navigation so it's easier to find relevant content—see the updated layout in langgraph
• Unify documentation across packages to better reflect real-world, end-to-end workflows that span multiple components

Some of this work is already live, and we’ll continue rolling out improvements across the ecosystem.

🧹 Cleaning House

We’re retiring many legacy or unused modules (e.g., adapters, docstore).

Integrations now live in dedicated third-party packages—such as langchain_openai, langchain_anthropic, langchain_google—or in the community-maintained langchain_community. The main langchain package will no longer proxy imports from them.

To support existing projects that may still rely on deprecated functionality provided by langchain, we’ll publish a langchain-legacy package that retains the current structure and functionality.

🧠 We’d Love Your Feedback

We’re working to make langchain 1.0 both powerful and ergonomic—and your input is key to getting it right.

We’re especially interested in:

• Any pain points you've run into with the current package structure
• Features or workflows you’d like to see added or improved
• Deprecated functionality you’re still relying on or unsure how to replace

Feel free to reply on the forum with thoughts, questions, or concerns.

Thanks for building with us!
—The LangChain Team

[aperez900907]

Will all features be supported on Typescript? Thanks, best regards to the team!!!!!!

[eyurtsev]

Yes! We want the js and python implementation on feature parity

[Sooowayydh]

Looks like a meaningful step toward a leaner, more discoverable package!

[GMartin-dev]

Langraph and Langchain-core are pretty distinct things with diff scope and functions. What happens with projects using langchain-core abstractions and not using Langgraph, will this force langgraph as a dependency?
What about the langchain-core agent abstractions are those going to be replaced by langraph's? --> terrible idea if you ask me
There are projects that intentionally avoid langraph abstractions and for sake of minimalism prefer the simple core abstractions.