Problemsby GlyphTrouble with Mistral blocks
3 posts from 3 people3d activeRising, +2 this week
Posts per day
The posts behind it
Feature: code-sign Windows binaries (vibe.exe, vibe-acp) — Defender ASR / SmartScreen blocks unsigned executables on corporate machines
...where a large share of potential users work - unsigned, low-prevalence executables are blocked by default security baselines, so Vibe cannot even start without a per-version IT exception. ## What enterprise users actually see On any Intune / Microsoft Defender for...
bug: oversized MCP image results lose their image blocks
...asked vibe to review a ticket with text and images, and while the text was fine, it was unable to load the images. To access the ticket, I use an MCP. I discovered that a valid image fetched by an MCP tool is lost when oversized-output handling replaces the tool result with a...
bug: thinking blocks displayed as raw JSON in terminal
## Summary When the model produces thinking/reasoning blocks, they are displayed as raw JSON in the terminal instead of being hidden or rendered in a collapsed/clean way. ## Expected behavior Thinking blocks should either be: - Hidden by default (collapsed) - Rendered in a...
Companies and products named
About this problem
Evidence
3 posts from 3 people in 1 place, about 1 a week over 21 days. Mostly on mistralai/mistral-vibe. Tools named alongside: Observe, Raw, Shell, Microsoft Azure.
Frustration Frustration 0 of 3· Seen on GitHub issues
How it was grouped
Posts about Mistral with no known issue, sharing the word "blocks". First post Oct 7, 2026, latest Oct 27, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method
Other Mistral problems
Mistral runs out of context on real work
3 posts from 3 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 6 posts from 6 people on GitHub issues.
Mistral upgrades break working setups
9 posts from 9 people on GitHub issues.
Mistral users keep filing bugs
Top post: "RoPE corruption due to TF32 on B200 (possibly others) when using `torch.set_float32_matmul_precision(high)`", one of 21 posts from 20 people on GitHub issues.
Mistral writes buggy code that is hard to review
8 posts from 6 people on GitHub issues.
Trouble with Mistral vibe
Top post: "Mistral Vibe CLI does not update to 3.0.0", one of 8 posts from 8 people on GitHub issues.
Mistral rate limits and usage caps block work
4 posts from 4 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.
Trouble with Mistral system
Top post: "Installation fails, sound system dependency?", one of 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.
Mistral fails to return valid structured output
2 posts from 2 people on GitHub issues. Unverified.
Running Mistral locally hits memory and speed limits
2 posts from 2 people on GitHub issues. Unverified.
History