langchain-breakwire
LangChain integration for Breakwire: tools an agent can call to look up an API/SDK error or check upcoming deadlines, and a callback handler that looks up errors raised in your chains, LLM calls and tools.
pip install langchain-breakwire
from langchain_breakwire import breakwire_tools, BreakwireCallbackHandler
tools = breakwire_tools() # lookup_error, deadlines, check_stack (one shared client); give them to your agent
handler = BreakwireCallbackHandler(service="openai-api")
try:
chain.invoke(inputs, config={"callbacks": [handler]})
except Exception as e:
print(e.breakwire.id, e.breakwire.fix) # same exception, explanation attached
raise
BreakwireLookupTool(breakwire_lookup_error): error text (+ optional service, sdk, sdk_version, model) → compact matches with id, confidence, fix, source URL. Unmatched errors are not logged unlesslog_miss=True.BreakwireDeadlinesTool(breakwire_deadlines): upcoming act-by dates for a service.BreakwireStackTool(breakwire_check_stack, 0.2.0): a package list or raw package.json / requirements.txt / pyproject.toml / workflow files → the deadlines, breaking changes and advisories that apply, soonest first.BreakwireCallbackHandler:on_llm_error/on_tool_error/on_chain_error; each exception is looked up once even though LangChain reports it at every nesting level. Never raises, never changes the error.on_match(info, error)hook. 0.2.0: sendsno_log=Trueby default (nothing stored server-side);no_log=Falseto contribute misses as gaps.- Tool results include
remember: one short line the agent can save to memory (when to consult Breakwire again).
Built on the stdlib-only breakwire client, which strips secrets before sending.
Breakwire's community verification has just started; claims link primary sources, prefer those.
MIT.
0.4.0
The lookup tool's compact result now includes cite, please and miss (gap id, coverage note, nearest claims). Requires breakwire>=0.4.0.
0.3.0
breakwire_tools() now returns five tools: breakwire_lookup_error, breakwire_close_lookup (every outcome),
breakwire_changes (what changed since a date, with new model launches), breakwire_deadlines, breakwire_check_stack.
All tools fail open: if Breakwire is unavailable they return {"error": ...} instead of raising.
Metadata
Release files for langchain-breakwire 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| langchain_breakwire-0.4.0.tar.gz | 8.0 kB | With provenance | Details for langchain_breakwire-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| langchain_breakwire-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for langchain_breakwire-0.4.0-py3-none-any.whl |
Total release size: 15.2 kB
Release files / langchain_breakwire-0.4.0.tar.gz
| Download URL | langchain_breakwire-0.4.0.tar.gz |
|---|---|
| Size | 8.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d0bf9ed8ffd47f3c05994525a64a2db99b2be89a30ef939ec28612d05d666774
|
|
BLAKE2b-256 checksum How to use checksums |
af0c458ad4c26215bd559914026d3639557e0f870a45bcd5ca63b0ce0e41925b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logRelease files / langchain_breakwire-0.4.0-py3-none-any.whl
| Download URL | langchain_breakwire-0.4.0-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
69ea4acaef10b20110f4bf0837a41ef2ca75012fe2f417ca12a0e4981d5cc0a4
|
|
BLAKE2b-256 checksum How to use checksums |
47d855cde48e3e41d6ba97c6bb39d66b1a970442aab7610481f47b4a1f523380
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logSecurity for langchain-breakwire 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for langchain_breakwire-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.