- Rating
- 2
- Confidence
- 3
- Informativeness
- 1
- Presentation
- 2
- Soundness
- 3
Read review
Paper summary
The paper addresses glitch tokens, which are vocabulary items a model cannot reproduce even in a simple repetition task. It argues that earlier repairs such as GlitchCleaner do not restore the model's understanding of the token, since the model still cannot generate the glitched token. The authors propose GlitchPatch, which targets "functional repair": the token can be reproduced and the model can still say what it means.
The method has two parts. First, it trains a Glitch cleaner style lora adapter to fix the model's understanding of these tokens. Then, it trains one output-head row per glitch token so it passes 5 copy prompts. The adapter is switched on only when the input contains such a token. On Qwen-7B-Chat, GlitchPatch reaches 86.5% functional repair on 16,788 tokens, versus 16.2% for GlitchCleaner.
Critical strengths
- The method works, and the gains are large and consistent. The ablation is informative: on semantic-deficient tokens, combined finetuning is much better than row-only or lora-only. General-task accuracy is essentially unchanged.
- The paper is well written and easy to follow overall, and the figures and tables are clear.
Critical weaknesses
- The semantic LoRA with a gate on glitch-token inputs follows the same general recipe as GlitchCleaner. The main new ingredient is the closed-form edit of one output-head row per token. This is a neat, cheap idea, and the ablation shows it matters on repetition prompts. But the paper does not demonstrate that this is a fix necessary and effective for LLMs in practical use cases (non repetition/copy prompts).
- The straightforward baseline is to jointly tune LoRA adapters and the specific output rows, then apply the adapter everywhere. This is a simple functional repair that GlitchPatch should be compared to.
- The paper is generally easy to read, but the definition of output success is harder to follow than it needs to be. A concrete example, such as the one in the appendix, would explain it faster, and the formal notation could move to the appendix. The same applies to Definitions 1 and 2, which restate simple ideas in notation and slow down the reader.
- Output success is a narrow definition. Being able to reproduce a token under a direct copy prompt does not mean the model can use it correctly in context without such prompting.
Questions for authors
Could a better measure be used, for example using the token in a sentence, completing text containing it, or downstream tasks with natural text containing the token?
I am looking for evidence that GlitchPatch is necessary and effective for generating glitched tokens in practical settings (outside repetition prompts).
2 comments
Q1. Sentence completion and natural-text evaluation
Could a better measure be used, for example using the token in a sentence, completing text containing it, or downstream tasks with natural text containing the token?
Response. We adopted the suggested sentence-generation and cloze tasks to evaluate correct token use in context. On 50 tasks that base model answers incorrectly, GP correctly completes 45 (90%). Evaluation checks whether the response meets the task requirements and uses the target appropriately. These results provide the proposed contextual measure alongside the original copying and semantic checks.
Q2. Evidence outside repetition prompts
I am looking for evidence that GlitchPatch is necessary and effective for generating glitched tokens in practical settings (outside repetition prompts).
Response. Two executable Qwen7B tasks show how GP recovers correct token use outside repetition prompts:
- AssemblyTrademark: the required API name is absent from the input. Base model substitutes AssemblyProduct; GP generates the correct trademark attribute and passes compilation and reflection checks.
- addContainerGap: the API name is supplied, but the model must satisfy new layout constraints. GP uses the correct operation with the required bounds and passes compilation and size checks, whereas base model uses addGap.
The MiniMax name case (it failed to produce a Chinese name 马嘉祺) and the gpt-oss token-interpretation failures provide further motivation. GlitchSplit recovers the name's surface form without producing a correct identity answer. This illustrates why repair should be evaluated for both output accessibility and semantic use. Our contextual tasks and executable examples directly examine these two aspects.
Response to Reviewer muiB
Thank you for the suggestions. We added contextual tasks and executable examples, implemented the joint-training baseline, and revised the presentation of the definitions.
W1. Practical relevance of the repair
Response. We address practical relevance with executable tasks outside copying prompts, then clarify how GP differs from GlitchCleaner. In the Qwen7B API tasks, we compare base model with GP on identifiers whose correct use affects program behavior. For an assembly-trademark task, base model generates AssemblyProduct, whereas GP uses the required token "AssemblyTrademark"; compilation and reflection verify the correct attribute and value. For a container-layout task, GP uses "addContainerGap" with the required bounds and passes compilation and layout-size checks. These examples connect token repair to concrete tasks outside repetition.
GP directly calibrates output rows for targets that pass semantic diagnosis. For deficient targets, it first performs reference-supervised semantic learning and then calibrates the rows in the adapted model state. This semantic supervision differs from GC's repetition objective, where the prompts for training and testing are identical.
Related failures also occur in modern models. https://www.minimax.io/blog/sparse-token-forgetting describes the Chinese-name case, and https://fi-le.net/oss/ records failures to interpret particular Chinese tokens. These cases motivate jointly examining output accessibility and semantic behavior.
W2. Joint LoRA and output-row training
Response. We implemented the requested joint LoRA and output-row baseline with an always-on adapter, and compared target repair, training cost, and instruction following.
Following GP’s separation of semantic and output repair, we trained the joint baseline on semantic data followed by copy data. This baseline achieves 7.30% functional repair, compared with 86.20% for GP.
To explore its potential under overly favorable supervision, we also evaluated a mixed joint variant that combines copy and semantic supervision at every optimization step. Using the same training examples, this variant achieves 93.22% functional repair. Both joint variants optimize 69,971,968 parameters, approximately 58 times the 1,208,320 parameters in GP’s semantic adapter. The mixed variant requires 3.77 times GP’s recorded gradient-training time (6 h 2 min versus 1 h 36 min). Its IFEval strict prompt accuracy is 16.45%, compared with 32.72% for GP. Thus, GP achieves high functional repair with substantially fewer trainable parameters, less gradient-training time, and better retained instruction following.
The repaired-target results are:
W3. Examples before formal definitions
Response. We have revised the main text to place a concrete example before the definitions and moved nonessential formal notation to the appendix. The example now introduces the criteria before their detailed notation.
W4. Correct use beyond direct copying
Response. We evaluate correct token use beyond direct copying with sentence-generation and cloze tasks. We identified cases in which base model cannot use the target correctly. GP recovers 45/50 of these base model failures (90%) without training on these contexts.