Stable

Integrations

Connect real implementation workflows into Neurovn using CLI ingestion, runtime decorators, and framework-specific integration patterns that end in the same canvas editor.

Start here if you are asking “how does my code get into Neurovn?”

Code to Canvas

Understand the real flow: local run, backend trace session, remote canvas creation, then open the editor.

How to choose an integration path

Existing workflow JSON

Use the CLI path to estimate and persist a remote canvas without touching runtime code.

Python runtime already exists

Use decorators around agent/tool functions for runtime-observed traces that are posted to Neurovn on completion.

Framework-specific apps

Pick OpenAI, LangGraph, LangChain, Google ADK, FastAPI, or CrewAI guides below after you understand the code-to-canvas capture path.

Integration Guides

Next up