How to use Claude to recover text from an old file
Claude Code inspected an extensionless, unreadable Mac document, identified its type and multiple character encodings, and converted the author's 1996 writing into clean plain text.
news.ycombinator.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Inspect [copy of legacy document] to identify its file format and character encodings. Recover its textual contents as readable plain text, explaining the conversion steps and flagging any portions that cannot be decoded confidently.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source poster / publisher
- tkgally
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- Claude Code recovered the contents of an unreadable document written in 1996 and output them as clean plain text.
- Human involvement
- The author reports readable recovered text; the post does not describe separate verification or review steps.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- Point Claude Code at the unreadable extensionless document.
- Have Claude inspect the data and identify the file type and encodings.
- Convert the document through multiple steps into clean plain text.
The author had a roughly 30-year-old document on their Mac and wanted to read it again. They had written it in 1996 using word-processing software they could no longer identify. The file had no extension, and none of their current Mac applications could read its contents.
Instead of searching for a conversion utility, they pointed Claude Code at the file and asked what it could determine about it. Claude inspected the underlying file data, identified the file type and recognized that it contained multiple character encodings. It then performed a couple of conversion steps.
The reported output was clean plain text containing what the author had written in 1996. The source does not name the recovered document format, the character encodings or the conversion utilities, so the example supports a discovery-and-conversion workflow rather than a specific technical recipe. The author felt this approach was quicker and easier than finding a suitable utility online, while acknowledging that such a utility might have existed.
Who it's for: People with unreadable legacy documents who want to recover their textual contents.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: Hacker News · tkgally
Frequently asked questions
Did the author know the original document format?
No. The author could not remember the word processor, and the file had no extension. Claude identified its type by inspecting the data.
What was recovered from the old document?
The author reports receiving clean plain text containing their writing from 1996. The post does not report recovery of the original formatting.
More details
About this account
Claude inspected the file, identified its format and encodings, and carried out conversion after the author's initial request.
Platform: Hacker News. Attribution: https://news.ycombinator.com/item?id=46582715. Prompt: Suggested (written by Agents In Use, not the author's). Sourced by the Agents In Use pipeline.
Credit: tkgally on Hacker News
Source published
Added to Agents In Use
Source checked
Tools and topics
Claude Code · Mac
Legacy documents · Text recovery · File conversion
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.