langchain-context

LangChain context navigator

Overview

This navigator covers the LangChain Python ecosystem in depth, plus a thin orientation pointer for the JS port:

• Primary: the langchain-ai/langchain Python monorepo — langchain-core, the new langchain package (v1; built from libs/langchain_v1/), the legacy langchain-classic package (built from libs/langchain/), in-tree partner integrations, and the auxiliary libs (text-splitters, model-profiles, standard-tests).
• Python companion repos: LangGraph (langchain-ai/langgraph), LangSmith SDK (langchain-ai/langsmith-sdk), Deep Agents (langchain-ai/deepagents), and the out-of-tree partner monorepos langchain-ai/langchain-google and langchain-ai/langchain-aws. Plus the docs source at langchain-ai/docs.
• JS port (thin coverage only): langchain-ai/langchainjs is included as a pointer reference for orienting JS questions — full JS depth is out of scope; follow source links into the JS repo for non-trivial questions.

When asked a question this navigator's domain covers:

1. Scan the Catalog below for the matching topic.
2. Follow the link to read the reference file.
3. If the question spans multiple references, consult the Cross-reference map.
4. If a reference points at a source URL for deeper detail, follow it only if the reference itself didn't answer the question.

For first-time orientation — what packages exist, how langchain vs langchain-classic differ, where companion repos live — start with langchain-overview.md.

Claims policy

Cite by default, and make load-bearing claims verifiable:

1. Inline-cite every load-bearing claim with its SHA-pinned permalink — the https://github.com/langchain-ai/langchain/blob/<sha>/libs/langchain_v1/langchain/agents/factory.py#L17-L25-style link the reference gives for that fact (versions, defaults, signatures, deprecations, behavior a user could get wrong by guessing). Put the permalink inline, on the claim. Use a bare filename parenthetical (e.g. (langchain-v1-agents.md)) only when the reference genuinely provides no permalink. This inline permalink is what the grounded-citation eval (SELF-AUDIT Check 8) grades.
2. Don't cite orientational prose — "what is X?", "when did X launch?" — answer those from this navigator alone; opening a reference is itself a citation gesture.
3. End with a one-line provenance footer, emitted italic, formatted *References consulted: foo.md, bar.md. Grounded in {{LIBRARY}}@{{VERSION}} — [reference index]({{INDEX_URL}}).* The footer is a summary of what you read — not a substitute for the inline permalinks on the claims. The {{LIBRARY}} / {{VERSION}} / {{INDEX_URL}} tokens are agent-substituted at answer time, so they appear literally in the stamped SKILL.md.
4. If no reference was opened, say so in the footer ("Answered from general knowledge — no {{LIBRARY}} references consulted") — never fake it.