Trouble with Mistral session
LLM apps2 posts from 2 people2d active+00 posts in the last 7 days, 2 the 7 days before (fading)Unverified
Posts per day
The posts behind it
2, newest firstbug: config change after subagent spawn makes session permanently unresumable (child Session binding conflicts with its parent record)### Component CLI ### Summary Changing agent configuration while a session has subagent children can make the session **permanently unresumable**. On resume, child preflight validates each non-tombstone child store's metadata digests (template digest, policy-ceiling digest)...mistralai/mistral-vibe · SLASHLoginOpen ↗bug: Double callback_resolved corrupts unified session store...case so a poisoned store can self-heal on open instead of being stranded. Workaround that recovered my sessions: the orphan resolve was the final journal record each time; truncating it (after quarantining the segment) makes the store load and resume again. Related: #1162...mistralai/mistral-vibe · mweirauchOpen ↗
Companies and products named
About this problem
Evidence
2 posts from 2 people in 1 place, about 2 a week over 3 days. Mostly on mistralai/mistral-vibe. Tools named alongside: Harness.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about Mistral with no known issue, sharing the word "session". First post Oct 9, 2026, latest Oct 11, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
Other Mistral problems
Mistral agents loop, stall or fail midwayTrouble with Mistral harnessMistral users keep filing bugsTrouble with Mistral vibeTrouble with Mistral systemMistral writes buggy code that is hard to reviewMistral upgrades break working setupsMistral rate limits and usage caps block workMistral fails to return valid structured outputRunning Mistral locally hits memory and speed limitsTrouble with Mistral rustMistral hits connection, locking and scaling limits
History
Trouble with Mistral session (2 posts)