From 6015ee5d2add69e69c6964147b3fe35fd6d1b643 Mon Sep 17 00:00:00 2001
From: teknium1 <127238744+teknium1@users.noreply.github.com>
Date: Tue, 7 Jul 2026 16:36:05 -0700
Subject: [PATCH] fix: pass profile-scoped SessionDB to
 _session_latest_descendant in dashboard chat PTY resume

The chat PTY launch path landed on main after PR #50558 and still called
_session_latest_descendant() with the old one-arg signature. Open the
requested profile's state DB (matching the REST endpoint) so profile-scoped
resume resolves descendants in the right database.
---
 hermes_cli/web_server.py | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/hermes_cli/web_server.py b/hermes_cli/web_server.py
index 4e1582fdeb9..64f1e684e70 100644
--- a/hermes_cli/web_server.py
+++ b/hermes_cli/web_server.py
@@ -13757,7 +13757,13 @@ def _resolve_chat_argv(
         env["HERMES_HOME"] = str(profile_dir)
 
     if resume:
-        latest_resume, _latest_path = _session_latest_descendant(resume)
+        _resume_db = _open_session_db_for_profile(
+            requested if profile_dir is not None else None
+        )
+        try:
+            latest_resume, _latest_path = _session_latest_descendant(resume, _resume_db)
+        finally:
+            _resume_db.close()
         if latest_resume:
             resume = latest_resume
         env["HERMES_TUI_RESUME"] = resume