← Back to library

Revive decades-old assembly code with a coding agent

TacticalCoder is reconstructing an unreleased 1991 PC game written in assembly, working with Claude Code, the MASM-compatible UASM assembler and DOSBox. Their old helper programs, such as picture converters and a sprite extractor, now build and run; the game itself is nearly there. Claude spotted a macro name that later became a reserved assembler keyword.

  • OutcomeHave a coding agent get old source compiling with a modern compatible assembler and emulator, and use the old comments to hunt known bugs.
  • SetupAn afternoon+
  • LevelIntermediate
  • CreditTacticalCoder on Hacker News
View original
Works with
Claude Code

Published Oct 23, 2026Updated Oct 23, 2026AI dry run on sample input: passed Oct 23, 2026Source verified Oct 23, 2026

When should you use it?

  • You have old source code you would like to run again
  • The original tools are gone
  • You can test in an emulator

Not for: Commercial code you do not own; Code with no source

What do you need, and what do you get?

You need

  • Old source files
  • A compatible modern assembler
  • An emulator

You get

  • Compiling utilities and program
  • Notes on fixes made
  • Bugs found from comments

How does it work, step by step?

  1. Put it in gitOld code often has no version control; start one now.
  2. Pick toolsChoose an assembler compatible with the original and an emulator.
  3. Build small firstGet utilities compiling before the main program.
  4. Fix clashesAsk the agent to look for names that later became reserved words.
  5. Hunt old bugsPoint it at comments that describe bugs and ask where they could be.

The prompt

Our own prompt, inspired by TacticalCoder on Hacker News and written to work in Claude Code. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt3 variables
Help me compile this old {language} code with {assembler} and run it in {emulator}. First, make a git repo and do not modify the originals folder.
Build the small utilities first. When builds fail, check for names that later became reserved words. Then read comments that mention bugs and point to where each bug might be.

Inspired by TacticalCoder on Hacker News: Comment in Revision Demoparty 2026: Razor1911 [video]. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Huge single files strain context; work file by file.
  • Old floppy copies may be damaged; back them up first.
  • Keep original files untouched in their own folder.

Our take

TacticalCoder's project shows why old code is such good territory for coding agents. The models have absorbed decades of manuals, forum posts and assembler quirks that most of us have forgotten, so an error that would once cost an evening, like a macro named incbin colliding with a keyword added years later, is identified at once. Order of work matters here. Get the small utilities compiling and running first, as the author did with the old image and sprite utilities, because each success confirms the toolchain and emulator settings before you tackle the big program. Commit the original files to git before changing anything; in 1991, version control usually meant copying folders, and you want an untouched baseline to compare against when something behaves strangely. Old comments describing known bugs are a surprisingly good task list, so feed them to the agent and ask for a fix with an explanation. Keep each change small and test it in the emulator before moving on, since assembly errors rarely fail politely. Above all, enjoy it; reviving lost work is one of the most rewarding uses of these tools.

Where the time goes back: Old projects come back to life in hours instead of weekends of reading manuals.

FAQ

What tool did it use?
UASM, a MASM-compatible assembler matching what the author first used, plus DOSBox.
What was the tricky bug?
A macro name from 1991 that later became reserved in assemblers.

Source and credit

Inspired by TacticalCoder on Hacker News. We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
Comment in Revision Demoparty 2026: Razor1911 [video]
Creator
TacticalCoder on Hacker News
Published on
Hacker News
Original date
Apr 8, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
Claude Code
AI dry run
Oct 23, 2026: passed. Dry-run tested by our AI test agent on sample input. PASS: Gates held on desk check; no live sends, bookings or purchases.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 23, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Career & Learning

All 37 Career & Learning playbooks →

Related playbooks

Career & LearningWorkflow✓ AI dry run

Have a coding agent review your Logseq journal

Point a coding agent at your note app's command line tool so it can summarize months of journal pages and report on tagged items such as job applications.

Credit: wosk on Hacker News

Under an hour
Career & LearningSkill✓ AI dry run

Learn any topic with a strict Socratic tutor skill

Load Jane Street's open-source tutoring skill into Claude, ChatGPT or a coding agent so that when you ask to be taught something, it first tests what you already know, keeps a 0 to 5 level for each part of the topic, quizzes you one question at a time without handing over answers, re-tests older material by surprise, and only ends the course after a final mixed exam.

Credit: janestreet

Minutes
Career & LearningWorkflow✓ AI dry run

Let the agent see its own 3D output

Give a coding agent a way to position a camera and take screenshots of the 3D scene it builds, so it can check its own work in a loop.

Credit: neomantra on Hacker News

An afternoon+
Career & LearningWorkflow✓ AI dry run

Write a new driver for a printer your OS dropped

Have a coding agent reverse-engineer an old USB device and write a driver, while you act as its eyes on test prints.

Credit: revolvingthrow on Hacker News

An afternoon+