hermes - 💡(How to fix) Fix [Feature]: Session state not written to state.db until session end — agentic runs invisible to external tooling [2 comments, 2 participants]

Problem or Use Case

state.db is only written at session end. For long agentic runs, this means the session is completely invisible to any external tooling (dashboards, monitors, integrations) until the run completes. If the process is interrupted before completion — container restart, connection drop, crash — the session is lost entirely with no record. Steps to reproduce

Start a long agentic task (any multi-tool run expected to take 10+ minutes) Query state.db or any dashboard backed by it during the run Observe: no session record exists, no turn data, no indication work is in progress Kill the container before the session completes Observe: session never appears in state.db

Expected behavior A session record should be created (or at minimum reserved) when the session starts. Turn data should be written incrementally, or at least a heartbeat/status field should update during the run so external tooling can observe in-progress work. Actual behavior Nothing is written until session end. The entire run is a black box to any consumer of state.db. Impact

Dashboards and monitoring tools show no activity during long agentic runs, creating a false "nothing is happening" signal Any interruption during a run results in complete data loss — no partial record, no turn history, no recovery path Combining with Issue #[2] (session continuation after max_turns), interrupted runs that span multiple sessions are entirely unrecoverable

Environment

Hermes Agent, max_turns: 150 External dashboard reading state.db directly via SQLite

Proposed Solution

Write a session record on turn 1 with a status of in_progress. Update status to complete on clean session end. Even a single initial write would allow external tooling to detect that a run is active. Incremental turn writes would be better but may have performance tradeoffs worth discussing.

Alternatives Considered

No response

Feature Type

New tool

Scope

None

Contribution

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

Debug Report (optional)