Data and AI struggles

Trouble with Mistral harness

LLM apps4 posts from 4 people3d active+33 posts in the last 7 days, 1 the 7 days before (rising)

Posts per day

Posts per day4 posts, Oct 9 to Oct 21

The posts behind it

4, newest first
GitHub issuesOct 17 4 days agobug: `enable_otel` exports no traces under the default harness — tracing is only wired into the legacy (`--legacy-harness`) path### Component CLI ### Summary Setting `enable_otel = true` with a custom `otel_endpoint` does not produce any OpenTelemetry traces for sessions running on the default (unified) harness. Traces are only exported when Vibe is run with `--legacy-harness`. The documentation...mistralai/mistral-vibe · SotemOpen ↗GitHub issuesOct 17 4 days agobug: nix package's runtime closure keeps ~530 MiB of vendored crate sources (Harness panic paths)## What happens The runtime closure of `packages. .default` contains every vendored crate source of the Harness build, about 530 MiB (`v8` alone is 166 MiB). Measured on aarch64-darwin, v2.26.1: The reference comes from `mistralai_vibe_local_harness/_native.abi3.so`. Panic...mistralai/mistral-vibe · pr0d1r2Open ↗GitHub issuesOct 15 6 days agobug: /status session cost ignores prompt-cache discount on the Unified Harness (cached tokens billed at full input price)### Component CLI ### Summary # DRAFT - GitHub issue for mistralai/mistral-vibe Title: bug: `/status` session cost ignores prompt-cache discount on the Unified Harness (cached tokens billed at full input price) Labels suggestion: `bug` --- ## Summary On the default Unified...mistralai/mistral-vibe · pzometa2 repliesOpen ↗GitHub issuesOct 9 12 days agobug: Unified Harness sessions do not record which agent they run (`agent_name` is null)### Component CLI ### Summary Under the Unified Harness, a session started with `--agent ` does not record the agent's name. In `generations/*/runtime-state.json`, `session_metadata.agent_name` is `null`, and the name appears nowhere else in the session's folder. With...mistralai/mistral-vibe · Simon-LMOpen ↗

Companies and products named

About this problem

Evidence

4 posts from 4 people in 1 place, about 2 a week over 9 days. Mostly on mistralai/mistral-vibe. Tools named alongside: Harness, GitHub, Docker, Reply.

Frustration Frustration 0 of 3· Seen on GitHub issues

How it was grouped

Posts about Mistral with no known issue, sharing the word "harness". First post Oct 9, 2026, latest Oct 17, 2026. Corroborated: 3 or more posts from 2 or more people or places. Method

History

AddedOct 21, 2026Trouble with Mistral harness (4 posts)