---
title: "Comment by Kartik N V J K on \"An Attention Window Is Not a Checkpoint: Inside vLLM's 128-Token Replay\" | Hashnode"
description: "Opening on the coding-agent task that keeps failing and then going into the 128-token replay is a good way in, because I think most people treat the attention w"
url: "https://hashnode.com/posts/an-attention-window-is-not-a-checkpoint-inside-vllm-s-128-token-replay/6acb2337061765bf8144b005/comment/6acd2ddcdb7691c9e42932ef"
---

[Discussion](https://hashnode.com/posts/an-attention-window-is-not-a-checkpoint-inside-vllm-s-128-token-replay/6acb2337061765bf8144b005)

Comment [An Attention Window Is Not a Checkpoint: Inside vLLM's 128-Token Replay](https://hashnode.com/posts/an-attention-window-is-not-a-checkpoint-inside-vllm-s-128-token-replay/6acb2337061765bf8144b005)

[Kartik N V J K](https://hashnode.com/@kartik-nvj)

[Oct 12](https://hashnode.com/posts/an-attention-window-is-not-a-checkpoint-inside-vllm-s-128-token-replay/6acb2337061765bf8144b005/comment/6acd2ddcdb7691c9e42932ef)

Opening on the coding-agent task that keeps failing and then going into the 128-token replay is a good way in, because I think most people treat the attention window like durable state when it is not. The distinction from a checkpoint is worth hammering: nothing about the window survives the way a real checkpoint would, so "it remembered a second ago" is doing a lot of unearned work. Did the retry-test example actually trace back to the replay boundary, or was that mostly the hook?
