Feature request: SSH agent per Windows session (RDS / multi-user) instead of the machine-global openssh-ssh-agent pipe

Setup: a shared Windows Server VM (RDS, several concurrent user sessions) used as a management/jump host. Each administrator has their own 1Password account and runs the desktop app in their own session. Problem: the 1Password SSH agent listens on the machine-global named pipe \\.\pipe\openssh-ssh-agent. Named pipes are not per session, so only one 1Password instance can serve it. Other users get "Permission denied" on the pipe and ssh-add -l fails, even though their own 1Password has the SSH agent enabled and holds the keys. Request: allow the SSH agent to be served on a per-user or per-session pipe (configurable name or an SSH_AUTH_SOCK-style path that the desktop app exposes), so that ssh clients and tools in each session use that user's own 1Password and approval prompt. Related: please also see the request for item-scoped approval for the CLI (per-item authorization with item names in the prompt). Use cases: administrators and technicians sharing a jump host, AI agents and automation per user, each needing per-user approval.