[Feature]: Add loop / repetition detection to stop runaway model output (e.g., endless emoji stream)

Offen
  • Stimmt etwas nicht?
#592 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
45/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript
Bereich
ai, cli

Rechercherichtung

Start by locating the interactive TUI's streaming generation path and how it cancels a run when the user presses Esc; the issue does not name specific files or tests. Check whether output limits or repetition checks already exist, then trace how a stop notice and retry or continue options reach the user. Done means repetitive streaming output can be detected, stopped, and covered by configurable safeguards.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

enhancement needs-triage tui
Product or interface

CLI - interactive TUI

Use case and problem

I'm using Mcode with BYOK (Bring Your Own Key) and the MiMo-V2.6-Pro model. Partway through a task, the model appeared to hallucinate and started emitting the same emoji over and over. The output never stopped on its own: the session kept showing Running (2min14s and counting) while the terminal filled with hundreds of identical emoji.

Today the only way out is to notice it and press Esc manually. If I'm not watching the session, it keeps generating indefinitely, which wastes tokens/cost on my own API key and blocks the rest of the task.

Question: does Mcode currently have any built-in mechanism to detect and break infinite/degenerate generation loops? If not, I'd like to request one.

Desired behavior

Mcode should detect degenerate, repetitive output and stop it automatically, regardless of which provider/model is used (including BYOK models).

Acceptance criteria:

  • Detect repetition in the streaming output (e.g., the same token, n-gram, or line repeated beyond a threshold) and abort the current generation.
  • Enforce a sensible per-turn output cap (max output tokens and/or max wall-clock time) as a safety net.
  • When a loop is detected, show a clear notice such as: Generation stopped: repetitive output detected (model may be looping). and return control to the user, with options to retry or continue.
  • Make thresholds configurable (or allow disabling) in settings, since some legitimate outputs may be repetitive.
  • Optionally pass frequency_penalty / repetition_penalty / max_tokens to providers that support them, configurable per model.
Platform

macOS

Alternatives and additional context
  • Workaround: manually pressing Esc to stop the run. This only works if I'm actively watching.
  • Model: MiMo-V2.6-Pro via BYOK. I understand the root cause is model behavior, but a client-side guard would protect users from any model that falls into a loop.
  • A screenshot of the runaway output is attached below.
Image
Vorherrschende Sprache
TypeScript
Sterne
2.2k
Forks
281
Ø Merge
14 Std. 42 Min.
Gemergte PRs (30 T.)
37

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus MiniMax-AI/minimax-code

Alle Issues in MiniMax-AI/minimax-code

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.