AbstractFlow

AbstractFlow is the visual workflow editor for AbstractFramework.

It is a web package (@abstractframework/flow). It runs a browser editor and a small Node server that serves the built UI and proxies /api/* to AbstractGateway. AbstractGateway owns users, sessions, runtime routing, provider configuration, workflow storage, run execution, ledgers, artifacts, and media catalogs.

Install

npx @abstractframework/flow --gateway-url http://127.0.0.1:8080

For a local checkout:

npm install
npm run dev -- --host 0.0.0.0 --port 3003

Open http://localhost:3003 and sign in with the Gateway user and token created by AbstractGateway. Leave provider/model selectors on Auto (Gateway default) for portable workflows. Gateway/Core capability defaults choose the actual provider/model at run time for the current user/runtime.

Text model selectors use Gateway's Core-backed capability_route discovery filters, so normal LLM pickers request output.text models. The Models Catalog node can store a route such as input.image,output.text to discover provider models for a specific input/output shape while the workflow runs.

LLM Call and Agent nodes include a Reasoning control backed by Core's thinking option. Leave it on Auto to inherit the Gateway/runtime default, or set/pin values such as off, low, medium, high, or xhigh for reasoning models that support explicit effort controls.

LLM Call and Agent response schemas can be defined directly on the unconnected resp_schema pin. The Builder tab creates ordinary JSON Schema, including Choice fields saved as enum values. Connected schema inputs override the inline default, and published workflows keep the schema in data.pinDefaults.resp_schema for Gateway/Runtime execution. When a response schema is configured, response remains the text output and a structured data object output is shown for Break Object, Switch, and other object-aware nodes.

Media artifact inputs can be wired from another node or uploaded directly on the node when the artifact pin is unconnected. Uploaded browser files are stored as Gateway artifacts. Image generation, editing, restoration/upscaling, video, voice, music, and transcription nodes all execute through Gateway-advertised capabilities. During Listen Voice waits, Flow records in the browser, uploads the captured audio artifact, and resumes the Gateway run; Flow does not execute local audio or transcription logic itself.

Vision media nodes now surface Gateway/Core's richer route contract directly in authoring:

• task-scoped provider/model discovery for text_to_image, image_to_image, text_to_video, and image_to_video
• batch generation controls with count and explicit ordered seeds
• ordered lora_adapters stacks for compatible image/video models
• plural media outputs such as image_artifacts and video_artifacts when a route returns more than one artifact in one call

The editor keeps those controls in the right-side Properties drawer and only surfaces them on nodes whose Gateway contract advertises the corresponding support.

File and document workflows can use Write File for Markdown/JSON/text paths, Read File for UTF-8/JSON inputs, Read PDF for extracting PDF text/metadata, and Write PDF for rendering report content to a real PDF path through Runtime.

The toolbar star opens the Workflow Authoring Assistant in the right drawer. The assistant reads docs/workflow-authoring-skill.md plus a compact generated node catalog, uses Gateway's default output.text model by starting normal Gateway planner runs unless a model is pinned, and reads planner responses from run ledgers. The model authors the complete workflow as one JSON document; the editor diffs it against the draft canvas and applies only validated edits. It can create or refine common workflows such as internet research, deep research, news digests, and job searches; Save, Publish, and Run remain explicit user actions.

Gateway Setup

export ABSTRACTGATEWAY_USER_AUTH=1
export ABSTRACTGATEWAY_DATA_DIR="$PWD/runtime/gateway"
abstractgateway serve --host 127.0.0.1 --port 8080
cat "$ABSTRACTGATEWAY_DATA_DIR/auth/bootstrap-admin-token"

Use:

• Gateway URL: http://127.0.0.1:8080
• User: admin
• Token: the agw_... token printed by Gateway or stored in auth/bootstrap-admin-token

What Lives Here

• src/ - React/Vite visual editor.
• bin/cli.js - npm CLI/static server and Gateway proxy.
• examples/flows/ - sample VisualFlow JSON files kept for reference/import tests.
• docs/ - external documentation for users and contributors.

AbstractFlow does not ship a Python package or local execution host. VisualFlow compilation, bundle execution, runtime state, and provider calls are handled by AbstractGateway and AbstractRuntime.

Scripts

npm run dev
npm run build
npm run lint
npm run docs:llms

Documentation

• Getting started
• Web editor
• Architecture
• API and contracts
• VisualFlow JSON
• CLI
• FAQ

Related Projects

• AbstractFramework: https://github.com/lpalbou/AbstractFramework
• AbstractGateway: https://github.com/lpalbou/AbstractGateway
• AbstractRuntime: https://github.com/lpalbou/AbstractRuntime
• AbstractCore: https://github.com/lpalbou/AbstractCore

Policies

• Changelog: CHANGELOG.md
• Contributing: CONTRIBUTING.md
• Security: SECURITY.md
• License: LICENSE