Repository navigation
Conversation
In ES-module and CommonJS apps alike, the LangChain integration stays pending and records no LangChain spans; LangChain's model requests are still captured as wire spans. The coverage notes and the limits now say so.
This branch has not been deployed
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.
What does this PR do?
Corrects the
@traceai/autoREADME: the zero-code agent does not trace LangChain yet.pendingin ES-module and CommonJS apps alike, and that the model requests LangChain sends are still captured as wire spans.@traceai/langchain's own API until a later release adds it.Why?
The README listed
langchainas an import-hook integration with no qualification. In a clean install of the published@traceai/auto0.1.4 with@traceai/langchain0.1.8,@langchain/core0.3.56 and@langchain/openai0.3.16, the agent reports the LangChain integration aspendingand records no LangChain spans. That holds for a CommonJS app started with--requireand an ES-module app started with--import. Users reading the README today should not expect LangChain spans.How was it tested?
@traceai/auto's test suite at this branch: 1,502 passed, 2 failed, 12 pending. Atdevit is the same: 1,502 passed and the same 2 failures, both inround6-boundary.test.ts(Vercel enable B3). This change does not touch them.The docs tests, including the check that the generated coverage table matches the registry, all pass. The generated block itself is unchanged.
Unit tests added / updated (
pytestorvitest)Integration tests pass (or N/A — no gateway behavior changed): N/A, documentation only
ruff check/mypy/npm run typecheck/npm run lintall passPublic types, env vars, or SDK behavior changes are documented in the relevant README
Checklist
main: this branch targetsdevfeat:,fix:,docs:,chore:…)docs/VOCABULARY.md. This repository has nodocs/VOCABULARY.mdondevormain, so there was nothing to check against. The two new sentences use only the README's own terms (pending, wire spans, integration).Notes for reviewers
typescript/packages/traceai_auto/README.md.