SwitchSD reads copy intent from the model's own states — Copy-intent probe drafting-mode switch — What does it mean?
The news. On September 17, 2026, a paper titled "To Copy or Not to Copy: Controlling Speculative Decoding via Intrinsic Model Signals" introduced SwitchSD. It starts from a tradeoff the field already knew about: neural drafters such as EAGLE3 behave well on any text, while copy-based drafters win big on repetitive text by proposing long spans cheaply. The paper's contribution is the switch between them. Rather than triggering on n-gram overlap, SwitchSD trains lightweight probes on the target model's internal representations and reports AUC above 0.99 at detecting genuine copy intent, with throughput gains of up to 15% over EAGLE3 across Llama and Qwen families. Read the paper →
Picture the counter of a print shop. Two machines sit behind it. The photocopier is unbeatable when the job is a reprint: feed it the original and a hundred identical pages come back in the time the typist needs for one line. The typist is slower, but the typist can handle a page nobody has written yet. Every job that arrives has to be sent to one of them, and the shop cannot ask the customer, because the customer does not know either.
That is the position a speculative decoder is in at every step. A drafter is not judged on being right; it is judged on being cheap enough that being wrong is affordable — and those two machines fail in opposite directions. Neural drafting spends a small forward pass to produce a few plausible tokens, which is a steady, modest win on almost anything. Context-based copying spends essentially nothing and can propose a very long span, but only if the text really is repeating.
The older way to choose was to look at the page itself: if the last few tokens match something earlier in the document, assume a reprint and run the copier. That is the n-gram heuristic, and its problem is that prose repeats itself by accident all the time. Common phrases, list scaffolding and boilerplate all produce overlap that goes nowhere. Send those to the copier and it confidently prints the wrong pages.
The diagram is the loop both machines feed into. Whatever the drafter proposes, the target model checks the whole span in a single forward pass, keeps the longest correct prefix and corrects the first wrong token. That verification step is why speculation is safe: the text you get out is the text the target model would have produced on its own. It is also why a bad draft costs real money — the verification pass is paid in full whether ten tokens survive it or one.
SwitchSD's claim is that the shop does not have to guess at the job, because the author has already written the answer in the margin: a probe on the target model's internal representations picks the drafter, so the choice is made from the model's own state rather than from the text on the page. The paper calls this treating "copying as a latent control signal of the LLM." It describes those probes as lightweight, and the switch is dynamic rather than decided once per request — the copier when the copy signal is strong, the typist when it is weak.
The difference between that and the n-gram trigger is where the evidence comes from. An n-gram match is evidence about the text, which is why coincidence fools it. A probe reading the internal activations is evidence about the model, which is the thing that actually decides what comes next. The paper reports that separation as near-perfect, which is what makes the switch worth having: a gate that is only occasionally right would hand the copier just enough bad jobs to erase its advantage.
| Drafting policy | What proposes the tokens | Strongest when | How it fails |
|---|---|---|---|
| Neural drafting (EAGLE3) | a small trained head runs its own forward pass | ordinary prose, where nothing repeats | the draft costs a forward pass every step; the abstract frames it as robust across settings rather than a large win in any one |
| Context-based copying (n-gram triggered) | a span lifted from earlier text, no model run | copy-intensive text with long repeated spans | fires on accidental overlap, and each false positive still pays a full verification pass |
| SwitchSD (probe-gated switch) | either one, chosen by a probe on the target model's hidden states | mixed traffic, where both regimes appear in one request | reported AUC above 0.99, up to 15% over EAGLE3 on Llama and Qwen (source) |
Here is why a false positive is worse than it sounds. Hold two things fixed: each speculation proposes 8 tokens, and each verification costs one full target forward pass no matter how many of those eight survive. Say a quarter of the steps in a request are genuine repetition (illustrative).
On a genuine copy span the copier is close to perfect — call it 8 of 8 accepted, an acceptance length of 8. On an accidental n-gram match the copied span is simply wrong after the first token or two — call it 1 of 8. A blind n-gram trigger that fires on both cases therefore averages 0.25 × 8 + 0.75 × 1 = 2.75 tokens per verification. The neural drafter, left alone, accepts perhaps 3 of 8 on the same traffic — 3.00 tokens per verification. The heuristic copier is not merely failing to help here; it is running below the drafter it replaced. That is the shape of the problem SwitchSD names.
Now gate the copier on a probe that routes every step correctly, the idealized case. The copy path is taken only on the quarter of steps that are real, and the other three quarters go to the typist: 0.25 × 8 + 0.75 × 3 = 4.25 tokens per verification (illustrative) — above both machines running alone. The numbers here are made up to show the composition; the paper's measured result is the up to 15% throughput gain over EAGLE3. The mechanism behind both is the same: the value of a switch is bounded by how often it is right, because every wrong switch is charged the full price of a verification.
Two limits are worth naming. First, the probe is trained on a target model's internal representations, and the paper's abstract does not say whether such a probe transfers to another model, or what training one costs — so treat portability as an open question rather than a settled one. Second, this is repetition inside a single request. Repetition across requests — the same system prompt on every call — is a different lever entirely, and it is already handled upstream by prefix caching, which skips the computation rather than guessing at it.
What generalizes past this one paper is the move itself. Serving systems are full of choices that are currently made from surface statistics: how long a draft to run, which expert to prefetch, when to stop thinking. The broader bet SwitchSD makes is that the model's own activations are a better place to look for those answers than the text it has produced so far — the signal is upstream of the output, so it arrives before the cost is committed. Whether a given workload is worth speculating on at all is the next question in the same family.
Continue in trackSpeculative Decoding — the draft model variants SwitchSD switches betweenGoes deeper in: LLM Serving → Speculative Decoding → Draft Model Variants
Related explainers
- DeLS-Spec adds short-context heads to block drafting — another way to improve the draft itself, by fusing two drafters instead of choosing between them.
- BlockPilot gives diffusion speculative decoding 4.2x — the same adaptive instinct applied to a different knob: how many tokens to draft per step.
- NVIDIA aligns draft length to tensor-core tiles — what happens when the draft-length choice is made by the hardware instead of the text.