vinc-langgraph
Vinc for LangGraph and LangChain agents. Vinc is a knowledge graph you share with AI: the decisions, records and documents your team wrote, with the reasons attached. This package brings the relevant part of it into your graph nodes and model calls.
Install
pip install vinc-langgraph # node helpers and tools
pip install "vinc-langgraph[agents]" # plus the middleware for create_agent
Set VINC_API_KEY to a member key. A vinc_ro_ key is enough for everything except record_episode.
In a graph node
from vinc_client import VincClient
from vinc_langgraph import build_system_message, get_vinc_context
vinc = VincClient()
def review(state):
block = get_vinc_context(vinc, state["messages"]) # newest human message
system = build_system_message(block, "You review design changes.")
return {"messages": [llm.invoke([system, *state["messages"]])]}
get_vinc_context makes one call, two when nothing matched or several nodes tied (it then widens with a search). It returns None when nothing matched, and also when Vinc is unreachable or the daily limit is spent, so the node goes on without it. A wrong key or space raises.
In a create_agent agent
from langchain.agents import create_agent
from vinc_langgraph import VincContextMiddleware
agent = create_agent("openai:gpt-5", middleware=[VincContextMiddleware()])
The middleware adds the block to the system message of each model call. An agent that uses tools calls the model several times per question, so the answer is kept for 60 seconds (cache_seconds) instead of spending a Vinc call each time.
Tools the model can call
from vinc_langgraph import create_vinc_tools
tools = create_vinc_tools(VincClient()) # vinc_brief and vinc_search, read only
Recording, after a person approved
Nothing in this package writes on its own. Put record_episode in the node after an interrupt(), and give only that node a vinc_sk_ key. examples/approve_then_record.py is a complete graph:
context -> review -> approve (interrupt) -> record
License
MIT
Metadata
Release files for vinc-langgraph 0.1.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 | |
|---|---|---|---|
| vinc_langgraph-0.1.0.tar.gz | 10.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vinc_langgraph-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 17.6 kB
Release files / vinc_langgraph-0.1.0.tar.gz
| Download URL | vinc_langgraph-0.1.0.tar.gz |
|---|---|
| Size | 10.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
819714d7cd4d3dc2591df3316b1f9b6487a610caae47a303b825137493c3c21e
|
|
BLAKE2b-256 checksum How to use checksums |
9bf9e20f4ba1718123df70c7afcea352ebca5017a04f88617778008b21568fee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 29, 2026.
Transparency logRelease files / vinc_langgraph-0.1.0-py3-none-any.whl
| Download URL | vinc_langgraph-0.1.0-py3-none-any.whl |
|---|---|
| Size | 7.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
96f71e4aa37cf89f3b01204fe5f5faa8c05b48a49784972df8281d9a50f1c3bb
|
|
BLAKE2b-256 checksum How to use checksums |
94acffae12119ed6bc804c5cf10993fa1c59b3146ccc7e1557c74dff0b1eb15f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 29, 2026.
Transparency log