NousResearch/hermes-agent · error · Error
resume returned no session id
Error message
resume returned no session id
What it means
Error "resume returned no session id" thrown in NousResearch/hermes-agent.
Source
Thrown at apps/desktop/src/app/contrib/hooks/use-session-tile-delegate.ts:125
// reading messages) without a profile lets the gateway fall back to the
// launch-profile DB and fork the conversation into the wrong profile —
// the same cross-profile bleed the recovery resumes had (#67603).
const profile = await resolveSessionProfile(storedSessionId)
const [prefetch, resumed] = await Promise.all([
getLatestSessionMessages(storedSessionId, profile).catch(() => null),
requestGateway<SessionResumeResponse>('session.resume', {
session_id: storedSessionId,
cols: 96,
omit_messages: true,
...(profile ? { profile } : {})
})
])
const runtimeId = resumed?.session_id
if (!runtimeId) {
throw new Error('resume returned no session id')
}
updateSessionState(
runtimeId,
state => ({
...state,
busy: Boolean(resumed?.info?.running),
messages:
state.messages.length > 0 ? state.messages : toChatMessages(prefetch?.messages ?? resumed?.messages ?? [])
}),
storedSessionId
)
return runtimeId
},
submitToSession: async (runtimeId, text) => {
await withSessionNotFoundResume(
runtimeId,View on GitHub (pinned to c896c09c42)
Solutions
- Retry the resume; the gateway returned no session id, usually due to a transient disconnect.
- Start a new session if the old one no longer exists on the backend.
- Check gateway connectivity and confirm the session id still exists.
When it happens
Trigger: Thrown at apps/desktop/src/app/contrib/hooks/use-session-tile-delegate.ts:125 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of NousResearch/hermes-agent@c896c09c42 (2026-08-14).
Data as JSON: /api/errors/ebf162586b9634a6.
Report an issue: GitHub.