Setting KeepAlive with SendAsync/SendAsAsync

[StarbuckSapien]

I see that the ChatRequest has a KeepAlive property, but I don't see a way to set that when calling SendAsync. The SendAsAsync method creates a new ChatRequest object but does not set the KeepAlive value. Am I missing some other way to set KeepAlive for SendAsync?

[Ganesh-403]

@StarbuckSapien From what I can see, you're not missing an obvious overload.

ChatRequest does expose a KeepAlive property, but the convenience methods like SendAsync/SendAsAsync appear to construct a new ChatRequest internally without exposing a way to pass that value through.

That means there are a few possibilities:

1. It's an intentional simplification of the high-level API, where KeepAlive is only configurable when constructing a ChatRequest manually.

2. It's an oversight, and the overloads simply haven't been updated to forward the KeepAlive property even though the underlying request supports it.

If you specifically need control over model lifetime, I'd recommend checking whether there's an overload that accepts a fully constructed ChatRequest. If there isn't, then it seems like a reasonable feature request to either:

• Add a keepAlive parameter to the convenience methods, or
• Provide a SendAsync(ChatRequest request) overload so all request options remain accessible without having to duplicate the implementation.

That would keep the convenience API easy to use while still exposing the full capabilities of the underlying request model.

If a maintainer can confirm this isn't already supported, I'd say it's a worthwhile enhancement to add.

If this solves your problem, feel free to mark it as the accepted answer so others can find it easily.