nesquena-hermes 1a4d56c215 fix: CLI DB has no profile column, and silent SQL error swallowed results (#60) ...

The sessions table in the CLI state.db does not have a 'profile' column --
selecting s.profile caused an OperationalError which was silently caught by
'except Exception: return []', making get_cli_sessions() always return empty.

Fix: remove s.profile from the SELECT (it doesn't exist in the CLI schema)
and derive the profile from get_active_profile_name() instead, which is the
right value anyway since the CLI DB has no profile concept.

Co-authored-by: Nathan Esquenazi <nesquena@gmail.com>

2026-04-03 21:02:01 -07:00

12 KiB

Raw Blame History

View Raw