Input text field removed from response api

Meanwhile, Chat Completions not being silly, a ‘message’ shape that is just a message, the only difference being the API blocking you from sending image types on the same dang roles as responses now allows.

{
  "role": "assistant",
  "content": [
    {
      "type": "text",
      "text": "(Verse)\nWell, I woke up this mornin', heart heavy as a stone,\nShe packed her bags and left me."
    }
  ]
}

“output_text” of course the obvious way to send back gathered AI output from a collector…a collector of ResponseTextDeltaEvent, so obviously different from ResponseRefusalDeltaEvent that you’ll need to send back (yes, find the way to send that back..)

Where - why not just shut off all assistant messages as input and force you to only use a prior ID and force ID verification? Okay, ChatKit it is.

The AI output is a stream of integers that can be decoded client-side. Everything else, busting it into a bunch of typed chunks that have to be replayed (or alternately denied to you) is an insult to intelligence.

1 Like