handle stop_reason == "pause_turn"

[andyrdt]

One stop reason for Claude completions is pause_turn. It is common when enabling web search.

Currently, this results in a pydantic parsing error, since we're not explicitly checking for this stop reason.

I think there's a design choice here. We could pass the response through, back to the user, and expect them to handle the retrying of stop_reason == "pause_turn". Or we could bake this retry behavior into the client. I think probably the latter would be preferable, but open to feedback.

[johnh-ant]

you could check for stop_reason == "pause_turn" and if it is there raise a runtime error, this will mean it just retries. it should probably be added to the pydantic object as a stop reason too so it doesn't error after the retries are finished

[johnh-ant]

the api.py has retry logic and it should happen each time there is a runtime error (IIRC)

[johnh-ant]

there is also a retry callable you can pass through - this usually looks at the contents of teh response but it could be modified to retry on stop_resonse