AbstractFlow

# <token>: <data dir>/auth/bootstrap-admin-token, or the console's one-time link (abstractgateway docs/configuration.md:120, v0.7.2)

# Start a run of a shipped workflow (flow_id omitted: the bundle's default entrypoint)
RUN_ID=$(curl -sS -H "Authorization: Bearer <token>" -H "Content-Type: application/json" \
  -d '{"bundle_id":"basic-agent","input_data":{"prompt":"How long should I steep green tea?"}}' \
  "http://127.0.0.1:8080/api/gateway/runs/start" | python3 -c 'import json,sys; print(json.load(sys.stdin)["run_id"])')

curl -sS -H "Authorization: Bearer <token>" -H "Content-Type: application/json" \
  -d '{"flow_id":"@default","interface":"abstractcode.agent.v1","input_data":{"prompt":"Hello"}}' \
  "http://127.0.0.1:8080/api/gateway/runs/start"

Every start answers with the run id and the exact workflow version that runs it (resolved_workflow). Inside a chat, the workflow is the chat's driver: every turn is a run of the selected workflow on the same session_id, and the client can switch workflow between turns. The run's ledger records every step, and any client can load it and follow it live.

Make it the default agent of a client

A client that runs an agent names an interface rather than a fixed workflow, and the gateway setting agents.default_workflow.<interface> decides which workflow answers. With nothing saved, AbstractCode (abstractcode.agent.v1) runs the shipped basic-agent and the Assistant (abstractassistant.agent.v1) runs its built-in orchestrator. An admin changes it in the web console (Workflows → Make agent default), in the terminal console (Runtimes → Runtime knobs → Edit default agent workflows) or from the command line; the change is audit-logged. A saved workflow must declare the interface, and a default that no longer resolves is refused rather than replaced.

abstractgateway config set agents.default_workflow.abstractcode.agent.v1 coding-agent:coder

The full list, with pin types, is in VisualFlow format.

Share a workflow

A published workflow is one portable .flow file: the manifest, the root flow and its subflows in a single zip. Workflows are made to be shared between gateways and the people who use them.

curl -sS -H "Authorization: Bearer <token>" \
  -F "file=@./my-bundle@0.1.0.flow" \
  -F "overwrite=false" \
  -F "reload=true" \
  "http://127.0.0.1:8080/api/gateway/bundles/upload"

Packing a bundle from Python

Outside the editor, AbstractRuntime packs a bundle from VisualFlow JSON files. Upload the result as above, or place it in the directory named by ABSTRACTGATEWAY_FLOWS_DIR.

from abstractruntime.workflow_bundle import pack_workflow_bundle

pack_workflow_bundle(
    root_flow_json="/path/to/root.json",
    out_path="/path/to/bundles/my-bundle@0.1.0.flow",
    bundle_id="my-bundle",
    bundle_version="0.1.0",
    flows_dir="/path/to/flows",
)

# Gateway console: Apps > Flow Editor > Install, then Open
# or from a terminal:
abstractgateway apps install flow --launch

# The editor is at <gateway address>/apps/flow/ and opens signed in

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

# or install the command
npm install -g @abstractframework/flow
abstractflow-editor --gateway-url http://127.0.0.1:8080

# open http://127.0.0.1:3003/ and sign in with a gateway user id and token

Each browser signs in with a gateway user id and that user's token. The editor exchanges the token for a gateway session kept in HTTP-only cookies and does not keep the token. Serving at /apps/flow/ needs AbstractGateway 0.7.0 or later.