lvkit

lvkit parses LabVIEW .vi, .ctl, .lvclass, .lvlib and .lvproj files directly into queryable dependency and dataflow graphs, with no LabVIEW license and no LabVIEW install. From that graph it describes what a VI does, renders its block diagram to SVG or interactive HTML, generates cross-referenced documentation, diffs two versions, visualizes dataflow and dependencies, indexes a whole repo for project-wide questions in read-only SQL, and maps callers, callees and blast radius.

It reads, never writes: lvkit never modifies, re-saves or edits a VI, and every capability, including convert, parses the source and writes to a separate output file. It is a clean-room project, not affiliated with NI, built from public NI documentation, the open-source pylabview parser and observation of VI files. Generating a Python transliteration of a VI is experimental, and how far it gets varies from VI to VI.

It runs from a terminal, in CI, or through an AI agent: lvkit setup installs agent skills into Claude Code, GitHub Copilot or OpenAI Codex, and lvkit mcp starts an MCP server for IDE sessions where an agent needs to load a graph, walk wires and ask follow-up questions across multiple VIs.