Skip to content

Add support for display_name in sessions #3478

Closed
Closed

Description

@dylan-apex

When you make a POST request to /apps/{app_name}/users/{user}/sessions, there's no support for display_name with VertexAI. _create_session in adk_web_server.py doesn't pass display_name, even if it's included in the request body. The rest of the VertexAI session creation process accepts **kwargs, so we could also pass **kwargs in the signature

Activity

  1. added
    web[Component] This issue will be transferred to adk-web
    on Nov 10, 2025
  2. added theissue type on Nov 10, 2025
  3. self-assigned this
    on Nov 11, 2025
  4. klateefa commented on Nov 25, 2025

    @klateefa

    @dylan-apex Thank you for reporting this. I understand the request is currently under review. Please keep me posted if anything else is needed. Thanks for your patience.

  5. added
    needs review[Status] The PR/issue is awaiting review from the maintainer
    on Nov 25, 2025
  6. wuliang229 commented on Jan 29, 2026

    @wuliang229
    Collaborator

    Hi @dylan-apex please see #4164 (comment). We will come back to this FR.

  7. dylan-apex commented on Jan 29, 2026

    @dylan-apex
    ContributorAuthor
  8. wuliang229 commented on Jan 29, 2026

    @wuliang229
    Collaborator

    @dylan-apex I do see the PR, it has the problem of a breaking database schema.

  9. adk-bot commented on Feb 11, 2026

    @adk-bot
    Collaborator

    This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.

  10. added
    stale[Status] Issues which have been marked inactive since there is no user response
    request clarification[Status] The maintainer need clarification or more information from the author
    on Feb 11, 2026
  11. removed
    stale[Status] Issues which have been marked inactive since there is no user response
    on Feb 11, 2026
  12. adk-bot commented on Feb 13, 2026

    @adk-bot
    Collaborator

    This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.

  13. added
    stale[Status] Issues which have been marked inactive since there is no user response
    on Feb 13, 2026
  14. added
    services[Component] This issue is related to runtime services, e.g. sessions, memory, artifacts, etc
    and removed
    stale[Status] Issues which have been marked inactive since there is no user response
    request clarification[Status] The maintainer need clarification or more information from the author
    on Feb 13, 2026
  15. adk-bot commented on Feb 21, 2026

    @adk-bot
    Collaborator

    This issue has been automatically marked as stale because it has not had recent activity for 7 days after a maintainer requested clarification. It will be closed if no further activity occurs within 7 days.

  16. added
    stale[Status] Issues which have been marked inactive since there is no user response
    request clarification[Status] The maintainer need clarification or more information from the author
    on Feb 21, 2026
  17. adk-bot commented on Mar 1, 2026

    @adk-bot
    Collaborator

    This has been automatically closed because it has been marked as stale for over 7 days.

  18. Tharun-PS commented on May 11, 2026

    @Tharun-PS

    Do we have this feature implemented ? Providing display name for sessions via code is required. In Agent engine UI, I'm able to set it, but not via code.

  19. WojciechNeuman commented on May 25, 2026

    @WojciechNeuman

    Our team would also strongly benefit from this feature.

    Allowing a friendly display_name when creating sessions via the ADK API would greatly improve the experience. Currently we rely on workarounds, users just see raw session IDs and session creation timestamps instead of human-readable titles like in other major LLM platforms.

    Thank you!

  20. WojciechNeuman commented on Jun 23, 2026

    @WojciechNeuman

    Hi @wuliang229 — just gently following up on this feature request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

needs review[Status] The PR/issue is awaiting review from the maintainerrequest clarification[Status] The maintainer need clarification or more information from the authorservices[Component] This issue is related to runtime services, e.g. sessions, memory, artifacts, etcstale[Status] Issues which have been marked inactive since there is no user responseweb[Component] This issue will be transferred to adk-web

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions