Trouble with Mistral resume
1 post from 1 person1d activeFading, +0 this weekunverified
Posts per day
The posts behind it
bug: /resume` fails with pydantic ValidationError and loops forever in recovery
...`{"type":"runtime_builtin","name":"process.start","arguments":{"command":"..."}}`. ## Workaround applied locally Removed the offending line from the session journal (backup kept as `0000000000011402.jsonl.bak`). After that, `vibe --resume ` works again (verified headless: `vibe...
Companies and products named
About this problem
Evidence
1 post from 1 person in 1 place. 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 "resume". First post Nov 9, 2026, latest Nov 9, 2026. Unverified: fewer than 3 posts, or one person or place only. Method
Other Mistral problems
Mistral tables suffer from small files and skew
2 posts from 2 people on GitHub issues. Unverified.
Mistral users keep filing bugs
Top post: "Chromium and Firefox browser extension", one of 24 posts from 23 people on GitHub issues.
Trouble with Mistral vibe
Top post: "Vibe desktop on macOS and Windows", one of 11 posts from 10 people on GitHub issues.
Mistral upgrades break working setups
15 posts from 14 people on GitHub issues.
Mistral writes buggy code that is hard to review
12 posts from 10 people on GitHub issues.
Trouble with Mistral session
Top post: "/status session cost ignores prompt-cache discount on the Unified Harness (cached tokens billed at full input", one of 9 posts from 9 people on GitHub issues.
Mistral rate limits and usage caps block work
5 posts from 5 people on GitHub issues.
Mistral runs out of context on real work
5 posts from 5 people on GitHub issues.
Mistral fails to return valid structured output
3 posts from 3 people on GitHub issues.
Trouble with Mistral harness
Top post: "`enable_otel` exports no traces under the default harness, tracing is only wired into the legacy", one of 3 posts from 3 people on GitHub issues.
Trouble with Mistral return
Top post: "apply_chat_template ignores return_tensors=None for processors that default to tensors (e.g. Pixtral)", one of 3 posts from 3 people on GitHub issues.
Running Mistral locally hits memory and speed limits
2 posts from 2 people on GitHub issues. Unverified.
History