Repository navigation
Virtual-model repetition_limit semantics + max-pattern knob #73
Description
Activity
- added a parent issue
on Sep 1, 2026 Resolved.
A (locked as proposed): explicit
0beats global, unset inherits global, per-model value wins over global.B (revised per your reply): max pattern becomes a second knob, not a hardcoded 8:
- Virtual-model field
repetition_max_pattern(tokens). Unset = inherit global. Explicit 1–64 = that value.0makes no sense for a pattern length, so this field has no tri-state — onlylimitkeeps the0-beats-global semantics. - Global default via env
STREAM_REPETITION_MAX_PATTERN; unset = 8. - Both fields appear in the Models view next to
slowdown.
C (recommendation: keep the name).
STREAM_REPETITION_LIMITmatches the handoff spec, the YAML keystream_repetition_limitalready ships inconfig.example.yaml, and every ticket uses "limit" for this knob. Renaming now is docs churn for zero gain. The second env follows the same prefix:STREAM_REPETITION_MAX_PATTERN.Final env surface:
STREAM_REPETITION_LIMIT— global default repeat count (0 = off)STREAM_REPETITION_MAX_PATTERN— global default chain length in tokens (default 8)
Final virtual-model fields:
repetition_limit— tri-state (*int): unset inherit / 0 off / N onrepetition_max_pattern— int, unset inherit, 1–64
- Virtual-model field
- added a commit that references this issue
on Sep 3, 2026
Question
Lock the virtual-model
repetition_limitsemantics and the related knobs before #69 starts.Three letters, one reply:
A: explicit
0beats global, unset inherits global.Unset on model + unset globally = off. Unset + global
N= on withN.0+ globalN= off for this model.N+ globalM= on withN. Match the existingslowdown: 0pattern ininternal/virtualmodels/.B: hardcode max pattern at 8 tokens inside the detector (no new field). v1 ships one knob — the limit count.
C: env name
STREAM_REPETITION_LIMITstays as-is. Unset / empty /0= off.N>0= on withN. No second env for opt-out (one knob = KISS).Reply as a letter per item. Example:
A, B, C.