Skip to main content

Glossary

TermMeaning
Agent nodeA node that runs an LLM in a loop, with tools. agentNode.
Approval requestA gated tool call waiting for a human, listed in the agent's approvalRequests.
AttestationA signed record of an approval decision, chained to the previous one.
Catalog runnerrunCatalogGraph / resumeCatalogGraph: runs a graph from its JSON definition and returns its state, so it can resume anywhere.
ChannelA named piece of run state, with a type label, a default and a reducer.
CheckpointThe saved state of a run after a node. A run resumes from its last checkpoint.
ComponentA ready-made node that runs inside the engine, such as a retriever or a prompt template.
Compiled graphWhat compile() returns: a checked graph you can run many times.
CouncilA graph where several agents answer, others rank the anonymized answers, and a chair decides.
EdgeA link from one node to the next. Plain, conditional (with a named predicate) or error.
EngineThe Rust runtime that executes graphs, shipped inside the npm package.
Fan-outRunning several branches at the same time, then joining.
Graph definitionA graph as plain JSON (app.definition), the same format YAML compiles to.
Human gateA node that suspends the run until you resume it.
Offline modeAILU_LLM_MOCK=1: agents without a key answer from a deterministic mock.
ReducerHow a channel combines updates: replace, append or merge.
ReplayRe-running a recorded run from its record, without calling a model.
Resolved byThe person who approved a tool call, recorded with the approval.
RunOne execution of a graph, with its own runId and state.
SubgraphA graph used as one node of another graph.
SuspendedThe status of a run waiting for a human, a date or a signal.
TierA capability level (fast, balanced, frontier, creative) mapped to a model per provider.
ToolA function an agent can call. Gated tools need a human's approval.