Agent Examples

Preview

DEFINE AGENT is a preview feature. It ships in broker 2.22. The syntax and behaviour may still change.

The examples below are complete. Deploy the LLM connector with -addConnector and the agent with -addAgent. For the full clause list see Agent Syntax. For more copy-and-deploy recipes (site guide, scheduled report, alert triage, shift handover), see Creating Agents in Coreflux.

Chat with a local agent
File a report the agent may publish

A tools-capable Ollama model on the broker host, granted read access to one topic tree. Create the user line-viewer with -addUser before you add the agent.

DEFINE CONNECTOR LocalLlama WITH TYPE LLM
    ADD LLM_CONFIG
        WITH PROVIDER "ollama"
        WITH BASE_URL "http://localhost:11434"
        WITH MODEL "llama3.2"

DEFINE AGENT LineWatcher
    USES LLM CONNECTOR LocalLlama
    WITH DESCRIPTION "Answers questions about line telemetry"
    WITH DEFAULT_USER "line-viewer"
    WITH INTERACTION_TOPIC "plant/watcher"
    ADD TOOL "read_mqtt"
        WITH TOPICS "lines/+/telemetry/#"

Publish Is line 2 running hot? to plant/watcher/s1/ask. The answer arrives on plant/watcher/s1/response. Each tool call appears on $SYS/Coreflux/Agents/LineWatcher/task/s1/stream.

The agent may publish under reports/shift/# and nowhere else. A writing tool needs WITH LEVEL "write".

DEFINE CONNECTOR Claude WITH TYPE LLM
    ADD LLM_CONFIG
        WITH PROVIDER "anthropic"
        WITH MODEL "claude-sonnet-4-0"
        WITH API_KEY GET SECRET "ANTHROPIC_API_KEY"

DEFINE AGENT ShiftReporter
    USES LLM CONNECTOR Claude
    WITH DESCRIPTION "Writes the end-of-shift report"
    WITH DEFAULT_USER "report-writer"
    WITH INTERACTION_TOPIC "plant/reporter"
    ADD TOOL "read_mqtt"
        WITH TOPICS "alarms/#, lines/+/counters/#"
    ADD TOOL "write_mqtt"
        WITH TOPICS "reports/shift/#"
        WITH LEVEL "write"

A publish to reports/shift/2026-10-15 runs when report-writer may publish there. A publish to lines/3/cmd is refused as out_of_scope on the task stream.

Supervisor with specialists

One LLM connector, a supervisor, and two specialists it may hand work to. Declare AlertAnalyst and MaintenancePlanner the same way, each with the grants its job needs. The delegation rules (shared budget, hop limit, who each tool call runs as) are in Delegation.

DEFINE CONNECTOR Gpt56 WITH TYPE LLM
    ADD LLM_CONFIG
        WITH PROVIDER "openai"
        WITH MODEL "gpt-5.6"
        WITH API_KEY GET SECRET "OPENAI_API_KEY"

DEFINE AGENT ShiftSupervisor
    USES LLM CONNECTOR Gpt56
    WITH DEFAULT_USER "shift-ops"
    WITH AGENTS "AlertAnalyst, MaintenancePlanner"
    WITH MAX_TOKENS 80000
    WITH INTERACTION_TOPIC "plant/supervisor"
    ADD TOOL "read_lot"

Give a classifier specialist WITH MEMORY "none" so an earlier conversation can’t steer it, and run high-volume classification on a local model.

Quick Start

Coreflux MQTT Broker

LoT Language

Coreflux HUB

VS Code - LoT Notebooks

Coreflux Portal

Using AI with Coreflux

Product Updates

Supervisor with specialists

​Supervisor with specialists

Supervisor with specialists