Bug Description

Auto-renamed session titles are intermittently used as Honcho session ID, not honoring sessionStrategy setting.

Steps to Reproduce

1. Set up Honcho
2. Configure Honcho in tools mode (happens in all modes, but this increases chance that honcho session will be created after title rename)
3. Set up Honcho with per-repo sessionStrategy
4. hermes chat in a repo or directory, then talk about a specific topic in the chat
5. hermes chat in the same directory, then talk about a completely different topic
6. Check honcho session table in the workspace

Even though per-repo is the session strategy, you'll end up with 2 different Honcho sessions that are named for the topic you talked about in each.

Expected Behavior

Honor sessionStrategy by reusing sessions "per-repo", "per-directory", or "global"

Actual Behavior

Separate session are created, even when using "global", because session_title takes priority over all session strategies, and session_title is set dynamically by the title generation LLM.

Affected Component

Agent Core (conversation loop, context compression, memory)

Messaging Platform (if gateway-related)

No response

Debug Report

Debug report uploaded:
  Report       https://paste.rs/nDYAf
  agent.log    https://paste.rs/t8BIf
  gateway.log  https://paste.rs/AHTVr

Operating System

Debian 13

Python Version

3.11.15

Hermes Version

0.13.0

Additional Logs / Traceback (optional)

Root Cause Analysis (optional)

session_title prioritized over other sessionStrategy configuration

Proposed Fix (optional)

Remove session_title. It's metadata, should never override the strategy. Especially "global".

Are you willing to submit a PR for this?

• I'd like to fix this myself and submit a PR