All tools

Visual Studio Code extension · beta

CopyWorkCode

Review AI-generated code changes by typing them yourself.

What it is

When an AI assistant edits your code, the change doesn't just land silently. CopyWorkCode queues it up and asks you to write it out, change by change, in the real editor. While you type, the file follows the code to the letter: a matching key lifts the dimming, a wrong key changes nothing. If you disagree with what the AI wrote, one keystroke hands you the editor to write your own version instead. Skip any change with a click, and set rules to auto-skip the files you never want to review.

  • Typed, not skimmed. Every accepted line passed through your hands.
  • Nothing slips. A stray key, paste or undo can't rewrite what you're reading.
  • Local only. No account, no network calls, no data leaving the machine.

Copywork, the old practice

Copywork is the habit of reproducing a piece of good writing by hand to absorb how it is put together. It was a staple of classical schooling and it is how a number of well-known writers trained themselves: Benjamin Franklin describes taking apart and rewriting essays from The Spectator until his own prose matched them[1], and Hunter S. Thompson is said to have typed out The Great Gatsby in full to feel what writing that well was like[2].

Programming borrowed the same idea. Zed Shaw's Hard Way books insist that every exercise be typed rather than pasted, on the grounds that copy and paste stops the material from sinking in[3]. The claim in both worlds is the same: you cannot reproduce something character by character without reading it at the pace of understanding, and that attention is where the learning happens.

Why it matters for AI-written code

AI assistants make it very cheap to accept code you did not write and only half read. In a controlled study, developers with an AI assistant wrote measurably less secure code than those without one, and were more confident that their code was secure[4]. The failure is not the tool. It is the review that quietly turned into a glance.

Retyping is a review you cannot skim. It also leaves a record: the extension knows which changes were written out, which were skipped, and which you rewrote yourself. "I looked at it" is hard to measure. "I typed it" is not.

The goal: validate the AI's work, and keep learning

CopyWorkCode has two aims that reinforce each other. The first is a layer of real validation on top of AI-generated changes: every line that lands in your codebase has been read closely enough to be reproduced, and anything you did not agree with was rewritten by you rather than waved through.

The second is the ordinary benefit of copywork applied to your own project. Much of the code may now be AI-generated, but your understanding of it does not have to atrophy. Writing it out keeps you fluent in the codebase, and where you take over and write your own version, you get the strongest learning effect of all: information you generate yourself is remembered far better than information you merely read[5].

How to get it

  1. Install it from the Visual Studio Code Marketplace (or Open VSX for editors that install from there), or search for CopyWorkCode in the Extensions view.
  2. Open a project and enable the extension in that workspace from the command palette. It does nothing in a workspace until you ask it to.
  3. Choose where changes come from: turn on agent capture for your AI assistant, or compare the working tree against a git revision, which needs no setup at all.
  4. Open the CopyWorkCode panel, pick a file with unreviewed changes, and start typing.

Early days: the review loop works end to end, and the details are still moving. The README on the Marketplace listing is the up-to-date reference.

Sources

  1. [1]Benjamin Franklin, Autobiography — the Spectator exercise (Project Gutenberg)
  2. [2]The Art of Manliness — "Want to Become a Better Writer? Copy the Work of Others"
  3. [3]Zed A. Shaw — Learn Code the Hard Way (type every exercise, never paste)
  4. [4]Perry, Srivastava, Kumar & Boneh — "Do Users Write More Insecure Code with AI Assistants?" (CCS 2023)
  5. [5]Slamecka & Graf — "The generation effect: Delineation of a phenomenon" (J. Exp. Psychology, 1978)