Bug Description
Session appears in list but becomes inaccessible after resume attempt. Session 4d4c76a7-e58a-487a-b66f-7ff408dafb37 (prompt neuron) showed status: running but mcp__genie__view/resume returned "No run found"
Steps to Reproduce
- Start long-running agent session:
mcp__genie__run with agent="orchestrator"
- Session ID returned:
4d4c76a7-e58a-487a-b66f-7ff408dafb37
- Wait ~45 minutes
- Resume same session:
mcp__genie__resume with sessionId="4d4c76a7-e58a-487a-b66f-7ff408dafb37"
- Error: "No run found for session 4d4c76a7-e58a-487a-b66f-7ff408dafb37"
Expected Behavior
Session should remain queryable and resumable indefinitely. mcp__genie__view shows state, mcp__genie__resume continues session with context preserved.
Actual Behavior
Session appears in mcp__genie__list_sessions but mcp__genie__view returns "No run found". Session context lost entirely.
Environment
- OS: Linux (WSL2)
- Node: v22.16.0
- Package version: 2.4.0-rc.8
- MCP: Genie MCP v2.4.0-rc.8
Impact
High (blocking work) - Sessions cannot be resumed after timeout
Affected Areas
Root Cause (Preliminary)
Session storage backend may have timeout/expiry issue or state sync problems between list/view/resume operations. mcp__genie__list_sessions succeeds but mcp__genie__view/resume fail on same session ID.
Possible Solution
Verify session persistence across time boundaries. Check if session state is being garbage collected or if there's a state sync issue between different MCP operations.
Bug Description
Session appears in list but becomes inaccessible after resume attempt. Session 4d4c76a7-e58a-487a-b66f-7ff408dafb37 (prompt neuron) showed status: running but mcp__genie__view/resume returned "No run found"
Steps to Reproduce
mcp__genie__run with agent="orchestrator"4d4c76a7-e58a-487a-b66f-7ff408dafb37mcp__genie__resume with sessionId="4d4c76a7-e58a-487a-b66f-7ff408dafb37"Expected Behavior
Session should remain queryable and resumable indefinitely. mcp__genie__view shows state, mcp__genie__resume continues session with context preserved.
Actual Behavior
Session appears in mcp__genie__list_sessions but mcp__genie__view returns "No run found". Session context lost entirely.
Environment
Impact
High (blocking work) - Sessions cannot be resumed after timeout
Affected Areas
Root Cause (Preliminary)
Session storage backend may have timeout/expiry issue or state sync problems between list/view/resume operations. mcp__genie__list_sessions succeeds but mcp__genie__view/resume fail on same session ID.
Possible Solution
Verify session persistence across time boundaries. Check if session state is being garbage collected or if there's a state sync issue between different MCP operations.