docs: langchain parity table (Python ↔ TypeScript) - #254
Merged
Merged
Conversation
Co-Authored-By: Larry Osakwe <larry@keycard.ai>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
Larry-Osakwe
approved these changes
Aug 31, 2026
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
The Python half of the cross-language parity documentation for the new
@keycardai/langchainpackage (typescript-sdk#158). README-only; no code changes, and the title is unscoped so nothing releases.Adds a "Contract parity with TypeScript" section to
packages/langchain/README.md: a row per contract concept (middleware, identity factories, accessor, resources/scopes, credential, sign-in and authorization URLs, fallback identity, escape hatch, testing seam, error accessors, ungranted read, interrupt payloads, attempt cap) with Python spelling vs TypeScript spelling, plus the three deliberate divergences — the TS escape hatch is a callback (so there is noagrant), the TS middleware owns itscontextSchema, and MCP composition stays Python-only in v1.Every row was verified against both sources rather than assumed, including the error paths:
get_resource_error/getResourceError,ResourceAccessErroron ungranted reads, thesubject_token_expiredvsmissing_identitysign-in reasons, and the shared 3-attempt acquisition cap.Link to Devin session: https://app.devin.ai/sessions/3c9fc9cb3a1143f6a9d21f172a366682
Open in Devin Desktop: https://app.devin.ai/desktop/session/3c9fc9cb3a1143f6a9d21f172a366682?variant=devin
Requested by: @Larry-Osakwe