Reviser: writing and editing text with cursor actions
0
14 commits
1 linked in READMEs
updated Oct 15, 2026
Language models usually write text once, left to right. Reviser is a decoder-only Transformer that writes and edits text with cursor actions (insert, move, delete, stop) that a deterministic executor applies to a canvas. Reviser is autoregressive over its own actions, so a step costs the same as an autoregressive (AR) step.
This Space runs the models of the paper Reviser: Writing and Editing Text with Autoregressive Cursor Actions (Sean Diab, arXiv:2609.20830, v2) and animates every action: the cursor jumping, text inserted in the middle, and deletions (backspace).
Write. Reviser continues an English prompt of exactly 35 GPT-2 tokens, the prompt length the models were trained on (the app counts tokens and trims longer prompts; 🎲 pulls the opening of a random FineWeb web page). Decoding follows the paper: the prompt is locked (the cursor cannot move into it), temperature 0.9, top-k 50, at most 220 new actions. Models:
Edit. Reviser-Edit (300M default, or 100M) gets a text and an instruction such as "Fix grammar". It starts with the text on the canvas and the cursor at its end, moves to the places that need a change, fixes them and stops. Decoding is greedy over action types, as in the paper's evaluation, so the output is deterministic. A checkbox also runs the AR rewriter of the same size, trained on the same data, which retypes the whole text, so you can compare the outputs and the number of steps.
These are small research models (100M and 300M parameters), so judge the mechanism rather than the prose. The continuation models continue web text; they do not follow instructions. The edit models know the kinds of edits they were trained on (grammar, fluency, clarity and simplification, coherence, neutral wording).
Everything runs on the CPU (the Space uses the free 2-vCPU hardware). Measured on a desktop CPU (Intel i9-9900K) with 2 threads, one generation took about:
On single examples, 8 threads gave the same times as 2. The Space's shared vCPUs may be slower than this desktop.
The first request for a model also downloads its checkpoint (0.4 GB for 100M, 1.2 GB for 300M); at most three models are kept in memory.
The app code is Apache-2.0 (see LICENSE); the inference code in src/ is taken from the paper's code release.
The model weights this Space loads are licensed CC BY-NC 4.0 (non-commercial use only), see
https://huggingface.co/sean-diab/reviser-checkpoints.
Reviser: writing and editing text with cursor actions
0
14 commits
1 linked in READMEs
updated Oct 15, 2026
Language models usually write text once, left to right. Reviser is a decoder-only Transformer that writes and edits text with cursor actions (insert, move, delete, stop) that a deterministic executor applies to a canvas. Reviser is autoregressive over its own actions, so a step costs the same as an autoregressive (AR) step.
This Space runs the models of the paper Reviser: Writing and Editing Text with Autoregressive Cursor Actions (Sean Diab, arXiv:2609.20830, v2) and animates every action: the cursor jumping, text inserted in the middle, and deletions (backspace).
Write. Reviser continues an English prompt of exactly 35 GPT-2 tokens, the prompt length the models were trained on (the app counts tokens and trims longer prompts; 🎲 pulls the opening of a random FineWeb web page). Decoding follows the paper: the prompt is locked (the cursor cannot move into it), temperature 0.9, top-k 50, at most 220 new actions. Models:
Edit. Reviser-Edit (300M default, or 100M) gets a text and an instruction such as "Fix grammar". It starts with the text on the canvas and the cursor at its end, moves to the places that need a change, fixes them and stops. Decoding is greedy over action types, as in the paper's evaluation, so the output is deterministic. A checkbox also runs the AR rewriter of the same size, trained on the same data, which retypes the whole text, so you can compare the outputs and the number of steps.
These are small research models (100M and 300M parameters), so judge the mechanism rather than the prose. The continuation models continue web text; they do not follow instructions. The edit models know the kinds of edits they were trained on (grammar, fluency, clarity and simplification, coherence, neutral wording).
Everything runs on the CPU (the Space uses the free 2-vCPU hardware). Measured on a desktop CPU (Intel i9-9900K) with 2 threads, one generation took about:
On single examples, 8 threads gave the same times as 2. The Space's shared vCPUs may be slower than this desktop.
The first request for a model also downloads its checkpoint (0.4 GB for 100M, 1.2 GB for 300M); at most three models are kept in memory.
The app code is Apache-2.0 (see LICENSE); the inference code in src/ is taken from the paper's code release.
The model weights this Space loads are licensed CC BY-NC 4.0 (non-commercial use only), see
https://huggingface.co/sean-diab/reviser-checkpoints.