[QUESTION] OpenAIConversationClient is missing

[navneetgargdil]

How can we help?

I followed following example https://platform.openai.com/docs/api-reference/conversations/create?lang=csharp

OpenAIConversationClient client = new( apiKey: Environment.GetEnvironmentVariable("OPENAI_API_KEY") );

I checked the dot net sdk v2.5.0.0 and OpenAIConversationClient is missing.

[jsquire]

Hi @navneetgargdil. Thanks for reaching out and for your inquiry. The Conversations feature area of OpenAI is a recent addition and is not yet represented in the client library. Once the REST API spec is updated to include this area, it will be added to the client.

As for the sample shown in the platform docs - that is an error in the docs. The client surface does not exist and has not been designed yet. There is no basis for that to be in the docs. @achandmsft, can you help get this removed? At best, its misleading.

[navneetgargdil]

Thanks for the response. I also notice that OpenAIResponseClient is only for evaluation purposes only.

[jsquire]

Thanks for the response. I also notice that OpenAIResponseClient is only for evaluation purposes only.

This is by design and part of the Feature Lifecycle in the OpenAI .NET Client Library

[crickman]

Upvote

[imperugo]

@jsquire is there any ETA for the conversation api into the .net client? Are we talking about days, weeks, months?

Thx

[crickman]

Spec updated today: #771

Does this unblock the issue?

[jsquire]

Spec updated today: #771

Does this unblock the issue?

The PR that you're referencing is a generator version update and is unrelated to the spec.

[crickman]

Bummer, ok...thank you.

[jsquire]

@jsquire is there any ETA for the conversation api into the .net client? Are we talking about days, weeks, months?

@imperugo: We were hoping to include Conversations as part of October's release and have been working with adopting that area of the upstream TypeSpec version in isolation. Unfortunately, we're running into issues with correctness from the OpenAI source OpenAPI spec, where the documented behavior disagrees with the service implementation. At this point, it's unclear whether the service behavior or spec are incorrect and we're working with the upstream owners for clarity but do not have a timeline for resolution.

Unless that gets resolved this week, it's unlikely that Conversations will make this release. Our next target would be for mid-November's release.