What GraphVM is
GraphVM runs workflows you draw as graphs; this console is the editor and control room in front of the agent that executes them.
A GraphVM workflow is a graph: nodes do the work (call an API, run a query, branch, loop, call an LLM) and edges carry control and data between them. You draw the graph here in the console; the GraphVM agent — a separate server — compiles and executes it.
- Console (this app)
- Editor, node catalog, run configuration, debugger UI, run history, settings.
- Agent (backend)
- Validates and executes graphs, stores run history and checkpoints, holds the node catalog, and serves every /api/* route the console reads.
- Graph
- The workflow document: nodes, edges, and per-node configuration.
- Run
- One execution of a graph with a given input. Runs can complete, fail, or suspend and be resumed later.
Because execution lives in the agent, anything that shows live data — graph lists, runs, validation, the catalog — needs the agent to be reachable. If those views report the agent is unreachable, the console itself is fine; the connection isn't.
Related
- Tour of the consoleGetting startedWhere things live: the top menubar, the header search, the editor's view dock and rails, and the routes behind each area.
- Create your first graphGetting startedStart a graph, get a runnable skeleton, add a node between the boundaries, and run it.
- "Agent unreachable" — what to checkGetting startedEmpty lists and amber warning banners almost always mean the console cannot reach the GraphVM agent.
More in Getting started · Search all help