v2.0.0 fails silently on SSH sessions because tokens aren't persisted even with gnome-keyring unlocked, while v1.20.0 works fine. This is on a Fedora release 43 (Forty Three)

[talonsec]

Checks

• I have searched github.com/aws/amazon-q-developer-cli/issues and there are no duplicates of my issue
• I have run q doctor in the affected terminal session
• I have run q restart and replicated the issue again

Operating system

Linux 6.19.7-200.fc43.x86_64 - Fedora Linux 43 (Forty Three)

Expected behaviour

fails silently on SSH sessions

Actual behaviour

had to roll back from 2.0 to v1.20.0

Steps to reproduce

No response

Environment

<This will be visible to anyone. Do not include personal or sensitive information>

[q-details]
version = "2.0.0"
hash = "0026b0505ef7bc2b10780c7bdb57813e5d949747"
date = "2026-04-13T09:03:52.798806Z (2d ago)"
variant = "minimal"

[system-info]
chip = "Intel(R) Core(TM) i7 CPU       Q 820  @ 1.73GHz"
total-cores = 4
memory = "31.26 GB"

[system-info.os.linux]
kernel_version = "6.19.7-200.fc43.x86_64"
id = "fedora"
name = "Fedora Linux"
pretty_name = "Fedora Linux 43 (Forty Three)"
version_id = "43"
version = "43 (Forty Three)"

[environment]
cwd = "/home/USER"
cli-path = "/home/USER"
os = "Linux"
shell-path = "/usr/bin/bash"
shell-version = "5.3.0"
install-method = "unknown"
in-ssh = true

[env-vars]
PATH = "/home/USER/.npm-global/bin:/home/USER/.local/bin:/home/USER/bin:/usr/local/bin:/usr/bin:/home/USER/.local/bin"
QTERM_SESSION_ID = "40cd5cdebe3649f2ab2844b59cf40cf8"
Q_PARENT = "/tmp/kiro-cli-parent-d0e6b449d455485e96aaa4d232be07c8.socket"
Q_SET_PARENT_CHECK = "1"
Q_TERM = "1.20.0"
SHELL = "/bin/bash"
TERM = "xterm-256color"
XDG_SESSION_TYPE = "tty"