This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: `nemo-flow` is now `nemo-relay`
NeMo Flow
nemo-flow is the NeMo Flow package for Python applications. It gives Python
code access to a portable agent runtime for execution scopes, middleware,
plugins, lifecycle events, adaptive behavior, and observability around tool and
LLM calls.
The package wraps the shared Rust runtime, so Python applications use the same runtime semantics as the Rust and Node.js surfaces.
Why Use It?
- 🧭 Own execution context in Python: Group agent, tool, and LLM work into one scope tree from Python application code.
- 🛡️ Package policy around callbacks: Use guardrails and intercepts to block work, sanitize observability payloads, rewrite requests, or wrap execution.
- 📡 Emit one lifecycle stream: Send runtime events to in-process subscribers, Agent Trajectory Interchange Format (ATIF), OpenTelemetry, or OpenInference workflows.
- 🧩 Integrate without a framework migration: Wrap framework or provider callbacks while preserving the application’s orchestration model.
What You Get
- ✅ Scope, tool, and LLM helpers: Managed boundaries that emit lifecycle events and run middleware in a consistent order.
- ✅ Middleware APIs: Guardrails and intercepts for tool and LLM requests, responses, and execution.
- ✅ Subscribers and exporters: Event consumers for observability and diagnostics.
- ✅ Plugin and typed helpers: Public modules for plugins, codecs, typed wrappers, adaptive runtime behavior, and observability plugin configuration.
- ✅ Shared Rust runtime semantics: Python behavior aligned with the Rust and Node.js surfaces.
Installation
Install the published package with uv:
uv add nemo-flow
If you are not using uv, install it with pip:
pip install nemo-flow
Optional Dependencies
LangChain Integration
LangChain integration is available with the langchain extra:
# With uv
uv add "nemo-flow[langchain]"
# With pip
pip install "nemo-flow[langchain]"
LangGraph Integration
LangGraph integration is available with the langgraph extra, this builds upon and includes the langchain extra as well.
# With uv
uv add "nemo-flow[langgraph]"
# With pip
pip install "nemo-flow[langgraph]"
Deep Agents Integration
Deep Agents integration is available
with the deepagents extra. This extra builds upon and includes the
langgraph and langchain extras.
# With uv
uv add "nemo-flow[deepagents]"
# With pip
pip install "nemo-flow[deepagents]"
LangChain NVIDIA Integration
The LangChain NVIDIA extra builds upon the langchain extra adding a compatible version of the langchain-nvidia-ai-endpoints package.
# With uv
uv add "nemo-flow[langchain-nvidia]"
# With pip
pip install "nemo-flow[langchain-nvidia]"
To install this along with the langgraph extra, use:
# With uv
uv add "nemo-flow[langgraph,langchain-nvidia]"
# With pip
pip install "nemo-flow[langgraph,langchain-nvidia]"
Getting Started
Register a subscriber, create a scope, and emit a mark event:
import nemo_flow
def on_event(event) -> None:
print(f"{event.kind} {event.name}")
nemo_flow.subscribers.register("printer", on_event)
with nemo_flow.scope.scope("demo-agent", nemo_flow.ScopeType.Agent) as handle:
nemo_flow.scope.event("initialized", handle=handle, data={"binding": "python"})
nemo_flow.subscribers.deregister("printer")
Package Surface
The public package modules are:
nemo_flow.scopenemo_flow.toolsnemo_flow.llmnemo_flow.guardrailsnemo_flow.interceptsnemo_flow.subscribersnemo_flow.pluginnemo_flow.adaptivenemo_flow.observabilitynemo_flow.typednemo_flow.codecs
Integrations
nemo_flow.integrations.langchainnemo_flow.integrations.langgraphnemo_flow.integrations.deepagents
The compiled extension is exposed as nemo_flow._native.
Documentation
NeMo Flow Documentation: https://nvidia.github.io/NeMo-Flow
Metadata
Release files for nemo-flow 0.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distributions (wheels)
| File | Reset | |||
|---|---|---|---|---|
| nemo_flow-0.2.0-cp311-abi3-win_arm64.whl | CPython 3.11 | abi3 | Windows ARM64 | Details |
| nemo_flow-0.2.0-cp311-abi3-win_amd64.whl | CPython 3.11 | abi3 | Windows x86-64 | Details |
| nemo_flow-0.2.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl | CPython 3.11 | abi3 | Linux glibc 2.17+ x86-64 | Details |
| nemo_flow-0.2.0-cp311-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl | CPython 3.11 | abi3 | Linux glibc 2.17+ ARM64 | Details |
| nemo_flow-0.2.0-cp311-abi3-macosx_11_0_arm64.whl | CPython 3.11 | abi3 | macOS 11.0+ ARM64 | Details |
Total release size: 23.7 MB
Release files / nemo_flow-0.2.0-cp311-abi3-win_arm64.whl
| Download URL | nemo_flow-0.2.0-cp311-abi3-win_arm64.whl |
|---|---|
| Size | 4.5 MB |
| Tags | CPython 3.11 Windows ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
94ce2e9354300dd1ba7fcc99315b7b2f71e78a3c988ed5d8b2b23115e11dcb71
|
|
BLAKE2b-256 checksum How to use checksums |
003a698ac0786515ea260695c0b12700d026e29912cdf5e881992e9f91b737a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 May 15, 2026.
Transparency logRelease files / nemo_flow-0.2.0-cp311-abi3-win_amd64.whl
| Download URL | nemo_flow-0.2.0-cp311-abi3-win_amd64.whl |
|---|---|
| Size | 4.7 MB |
| Tags | CPython 3.11 Windows x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
741a300b07d615b81288ea8bba1bf4b9c52d6eda62c3974847725ba5f5df76fe
|
|
BLAKE2b-256 checksum How to use checksums |
23f4624cd48a8253a42654a704bab37ae9fc4481c558194f69bf1326a502199d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 May 15, 2026.
Transparency logRelease files / nemo_flow-0.2.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
| Download URL | nemo_flow-0.2.0-cp311-abi3-manylinux_2_17_x86_64.manylinux2014_x86_64.whl |
|---|---|
| Size | 4.8 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ x86-64 abi3 |
|
SHA-256 checksum How to use checksums |
db4eb9e89ea6ccdf8ddb15c59d556ec37e400b6e363e52644c2d37c3d93c1429
|
|
BLAKE2b-256 checksum How to use checksums |
30c377b8150f3874f9a3f99f9acd01950adebe75a072cff3a06fad13fd16a681
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 May 15, 2026.
Transparency logRelease files / nemo_flow-0.2.0-cp311-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl
| Download URL | nemo_flow-0.2.0-cp311-abi3-manylinux_2_17_aarch64.manylinux2014_aarch64.whl |
|---|---|
| Size | 4.6 MB |
| Tags | CPython 3.11 Linux glibc 2.17+ ARM64 abi3 |
|
SHA-256 checksum How to use checksums |
eb1b59c85c06d2669019d2b6c5d69e63602481d1252148964203027dc8df2917
|
|
BLAKE2b-256 checksum How to use checksums |
119fa47fae363348a2ff342944d6ca294c65ce788c01a02e836a36060b11e912
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 May 15, 2026.
Transparency logRelease files / nemo_flow-0.2.0-cp311-abi3-macosx_11_0_arm64.whl
| Download URL | nemo_flow-0.2.0-cp311-abi3-macosx_11_0_arm64.whl |
|---|---|
| Size | 5.1 MB |
| Tags | CPython 3.11 abi3 macOS 11.0+ ARM64 |
|
SHA-256 checksum How to use checksums |
06453887f35fc96478566ac8aa113465210d1922dfd6607b9caaa28d688fddf0
|
|
BLAKE2b-256 checksum How to use checksums |
a3e5ee63a77c7f5c73d39471efd314df67ec92ed21bd325f54ea86fd789f440c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
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 May 15, 2026.
Transparency log