Skip to content

fix(langchain): LC-112 fix text names the run call's config - #233

Open
ericksondelacruz wants to merge 1 commit into
mainfrom
fix/lc-112-run-call-callbacks
Open

ericksondelacruz wants to merge 1 commit into
mainfrom
fix/lc-112-run-call-callbacks

Conversation

@ericksondelacruz

Copy link
Copy Markdown
Collaborator

Summary

LC-112 ("Agent has no callbacks while the rest of the project is instrumented") now offers a third way to fix it: pass the handler in the run call's config, agent.invoke(..., config={"callbacks": [handler]}). This is how LangWatch, Langfuse and LangSmith document their LangChain integration.

Text-only change to langchain/tracing.yaml. No change to severity, confidence, match or schema version.

Companion PRs

These land together:

  • agent-reliability-analyzer: "feat: add LangWatch support". The engine now credits callbacks passed in the run call's config, so the new fix text matches what the engine accepts. Its test copy of the rules mirrors this change, so the engine's rules-sync CI check passes once this PR merges.
  • trustabl-rulebook: "docs: record LangWatch as a vendor and LC-112's out-of-constructor credit".

Checks

  • scripts/check-rules-sync.sh against this branch: in sync (149 files).
  • tools/check_rulebook.py against this branch: OK.

The engine now credits callbacks passed at run time
(agent.invoke(..., config={"callbacks": [...]})), the wiring LangWatch,
Langfuse and LangSmith document, so the fix text offers it beside the
constructor kwarg and a global handler.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants