docs: introduce langchain-runcycles for LangChain agent users#59
Merged
Conversation
Documentation-only update introducing langchain-runcycles (https://github.com/runcycles/langchain-runcycles, PyPI: langchain-runcycles) as the canonical path for LangChain agent middleware integration with Cycles. No SDK code or protocol changes. - README.md: new "## Integrations" section listing langchain-runcycles as the right fit for langchain.agents.create_agent workflows. The existing examples/langchain_integration.py row is reframed as the callback-handler path for non-agent runnables (bare ChatOpenAI, chains, RAG) — the two patterns serve different surfaces and both remain supported. - examples/langchain_integration.py: docstring updated to point agent-using readers at langchain-runcycles. Code unchanged. - AUDIT.md: new entry "LangChain Agent Middleware Integration Pointer (added 2026-05-10)" documenting the docs-only nature of this change and the rationale for splitting the agent middleware into a sibling package per LangChain's publishing guidance (https://docs.langchain.com/oss/python/contributing/publish-langchain). The new package wraps the existing decide / create_reservation / commit_reservation / release_reservation / stream_reservation surface; no SDK methods were added to this repo.
Sibling-repo consistency follow-up to commit 80a0736 (which introduced
langchain-runcycles in README + examples but missed the issue templates).
Users opening bugs or feature requests can now select langchain-runcycles
as the affected repository.
Files: .github/ISSUE_TEMPLATE/bug_report.yml,
.github/ISSUE_TEMPLATE/feature_request.yml
Inserted after cycles-client-typescript to keep the Python-adjacent
integrations grouped.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documentation-only update introducing
langchain-runcycles(PyPI:langchain-runcycles) as the canonical path for LangChain agent middleware integration with Cycles. Companion to the v0.1.0 release of the new sibling package.No SDK code changes. No protocol changes.
Files changed
README.md— new## Integrationssection listinglangchain-runcyclesas the right fit forlangchain.agents.create_agentworkflows. The existingexamples/langchain_integration.pyrow is reframed as the callback-handler path for non-agent runnables (bareChatOpenAI, chains, RAG); LangChain 1.x agent middleware requirescreate_agent, so the two patterns serve different surfaces and both remain supported.examples/langchain_integration.py— file-level docstring updated to point agent-using readers atlangchain-runcycles. Code unchanged.AUDIT.md— new entry "LangChain Agent Middleware Integration Pointer (added 2026-05-10)" documenting the docs-only nature of this change and the rationale for splitting agent middleware into a sibling package per LangChain's publishing guidance..github/ISSUE_TEMPLATE/bug_report.yml,.github/ISSUE_TEMPLATE/feature_request.yml— addlangchain-runcyclesto the affected-repository dropdowns so users can file issues against the new package.Why a sibling package
LangChain 1.x introduced an
AgentMiddlewareAPI withwrap_tool_call,before_model, andwrap_model_callhooks. The new package wraps that API on top of this SDK's existingdecide/create_reservation/commit_reservation/release_reservationsurface — no new SDK methods needed. Splitting into a sibling repo follows:langchain-<service>naming convention used bylangchain-anthropic,langchain-openai,langchain-mongodb.The new repo mirrors this one's CI / release / linter / coverage configuration so both repos remain operationally consistent.
Test plan
examples/langchain_integration.pystill parses and runs (no code changes)bug_report.ymlandfeature_request.yml