How weavemindai/weft works
Weft is a language and runtime for composing AI, human, API, database, and infrastructure nodes into durable orchestrations. A user authors a graph, the compiler validates and builds it, and the runtime coordinates node execution, waits, signals, and recorded values; users can inspect and operate runs through the CLI and graph interface. The README documents the workflow and major capabilities, while sampled source is limited, so several runtime connections below reflect documented behavior rather than inspected call sites.
Main entry points: app.rs Dispatcher · execution_driver.rs Execution engine · lib.rs Node catalog · storage.rs Runtime file storage
Components 20
Authoring and compile
- Weft project
crates/weft-compiler/src/project.rs - Compiler
crates/weft-compiler/src/weft_compiler.rs
Execution runtime
- Execution engine
crates/weft-engine/src/execution_driver.rs - Runtime primitives
crates/weft-core/src/exec/loop_runtime.rs - Signal listeners
crates/weft-listener/src/lib.rs - Infrastructure lifecycle
crates/weft-infra-supervisor/src/lifecycle.rs
Nodes and integrations
- Node catalog
crates/weft-catalog/src/lib.rs - AI nodes
catalog/ai/llm/call.rs - Service nodes
catalog/google/api.rs - Human interaction
catalog/human/query/mod.rs
Operations and state
- weft CLI
crates/weft-cli/src/main.rs - Dispatcher
crates/weft-dispatcher/src/app.rs - Execution journal
crates/weft-journal/src/lib.rs - Broker services
crates/weft-broker/src/lib.rs - Runtime file storage
crates/weft-engine/src/storage.rs - Graph interface
packages/weft-graph/src/webview/lib/projection/engine.svelte.ts
Other components
- Developer / operator
- Object store
- External services
- Human reviewer
Connections 25
- Developer / operator → Weft project: authors
- Developer / operator → weft CLI: operates
- Weft project → Compiler: compiled by
- Compiler → Execution engine: builds program for
- weft CLI → Dispatcher: sends commands
- Dispatcher → Execution engine: coordinates runs
- Execution engine → Runtime primitives: uses runtime
- Execution engine → Execution journal: records execution
- Signal listeners → Dispatcher: delivers signals
- Execution engine → Node catalog: executes nodes from
- Node catalog → AI nodes: includes
- Node catalog → Service nodes: includes
- Node catalog → Human interaction: includes
- AI nodes → External services: calls
- Service nodes → External services: calls
- Human interaction → Human reviewer: requests review
- Human reviewer → Dispatcher: submits response
- Dispatcher → Infrastructure lifecycle: manages lifecycle
- Execution engine → Runtime file storage: uses file storage
- Runtime file storage → Broker services: requests URLs and metadata
- Broker services → Object store: presigns transfers
- Runtime file storage → Object store: transfers bytes
- Developer / operator → Graph interface: inspects graph
- Graph interface → Dispatcher: edits and queries
- Dispatcher → Execution journal: serves run records