Documentation
¶
Overview ¶
Command custom-invoker demonstrates packtrail's defining feature: the pluggable Invoker seam. The agent-pipeline flow's task nodes select `invoker: agent` and name a target agent; a tiny in-process Invoker plays the agent framework, and a choice node routes on the triage agent's output (results.triage.category). WithResultCache makes the (simulated) agent calls idempotent under packtrail's at-least-once delivery.
Run a NATS server (2.12+, JetStream enabled) and, from the repo root (the flow is loaded from examples/custom-invoker/flows):
go run ./examples/custom-invoker --nats nats://127.0.0.1:4222
It runs two executions — one billing, one general — and prints the route each one took plus its assembled results.
Click to show internal directories.
Click to hide internal directories.