Post

this is super cool! It definitely reminds me of deferred tools, but for a model without specific training for it. It also sounds like it can be implemented inference side, to prevent needing a round trip as well. I really like the ack as well

Guidance injection at inference would be awesome. However, the guidance my app injects is user-editable at runtime. I think we'd lose that if this was inference side?

0 reposts1 like

it should definitely be possible! deferred tools work like this inference side too to prevent round trips. As long as you know the tool->guidance mapping at api request time (chat completions, responses api, etc), you can just send both to inference and inference can manage the guidance flow

Mostly I just think this is cool and these patterns are useful at all layers of the model serving stack, and messing with the inference layer makes things fun :)