Skip to content

Should FunctionCallContent derive from UserInputRequestContent? #6831

Closed as not planned

Description

@stephentoub

If the intent of UserInputRequestContent is that it signals any content that the caller must respond to in a subsequent request, should FunctionCallContent derive from it? It currently doesn't.

cc: @westey-m

Activity

  1. westey-m commented on Sep 22, 2025

    @westey-m
    Contributor

    I'm not sure that we should consider UserInputRequestContent as a call for all kinds of input. It is specifically "User" input, where user here means end user, not developer/caller. We could change it to be InputRequestContent though, which would be broader and in that case having FunctionCallContent derive from it as well would probably make sense.

  2. stephentoub commented on Sep 22, 2025

    @stephentoub
    MemberAuthor

    We could change it to be InputRequestContent though

    It does seem like we need some kind of indicator on content that it requires follow-up (and without said follow-up, subsequent requests will fail). I also think "user" is ambiguous and unnecessary.

  3. stephentoub commented on Oct 9, 2025

    @stephentoub
    MemberAuthor

    I think we can leave it as-is.

  4. locked and limited conversation to collaborators on Nov 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    area-aiMicrosoft.Extensions.AI libraries

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions