basic-tool-interrupts

Documentation

Overview

This sample demonstrates tool interrupts, which are how Genkit does human in the loop (HITL): a tool pauses generation to ask a person, and resumes with their answer.

transferMoney interrupts when a transfer is large enough to need approving. Interrupting ends the turn with the tool unfinished, so the flow reads the interrupt, decides, and runs a second turn that restarts the tool with the answer attached. The tool then acts on it. (Tool.RespondWith is the other option, answering a call outright instead of letting the tool run again.)

The approve field stands in for the person: a real app would hand the pending interrupt to a client and run the second turn when they answer.

basic-tool-interrupts-exp is this same sample written against the in-preview tools API in genkit/exp. Reading the two side by side is the shortest way to see what that API changes.

Run it:

go run .

Or with the Dev UI, to call the flow from a browser and read a trace of both turns at http://localhost:4000/traces:

curl -sL cli.genkit.dev | bash    # install the Genkit CLI, once
genkit start -- go run .

Or over HTTP. The balance carries across requests, so run these in order. Decline a transfer that needs approving, which leaves the money where it is:

curl -N -X POST 'http://localhost:8080/transferFlow?stream=true' \
  -H "Content-Type: application/json" \
  -d '{"data": {"request": "Send $120 to bob", "approve": false}}'

Then approve the same one, which spends it:

curl -N -X POST 'http://localhost:8080/transferFlow?stream=true' \
  -H "Content-Type: application/json" \
  -d '{"data": {"request": "Send $120 to bob", "approve": true}}'

A small transfer needs no approval, so it finishes in one turn:

curl -N -X POST 'http://localhost:8080/transferFlow?stream=true' \
  -H "Content-Type: application/json" \
  -d '{"data": {"request": "Send $20 to alice", "approve": false}}'

Repeating the $120 one now asks for more than is left, which the tool answers outright rather than pausing on.