Most of what I give Claude Code isn't code
Someone on Reddit asked a fair question: lots of people who don't write code use Claude Code instead of the chat app. Should they? What does it do that chat can't?
I build apps with it, so I am not the target audience. But when I scrolled back through the last two months, most of what I asked it for had nothing to do with an app. It was chores. The kind I used to do myself, badly, at 1 am.
The difference is simple. Chat tells you what to do. Claude Code runs on your computer, so it does the thing, then checks whether it worked. You stop being the hands.
A game that wouldn't start
I play Windows games on a Mac through a free Wine wrapper. That setup breaks in creative ways.
The first version of the wrapper looped forever: Steam opened, crashed, and reopened every minute. Claude read the logs, decided the Wine engine was too old, and swapped in a newer one. A Unity game then died before writing a single log line. It switched the graphics backend and the game started. Months later a new game complained about a missing Microsoft runtime. It found the helper built into the wrapper and installed the runtime in one command.
I didn't learn what any of that means. I wrote down nothing. It did, in its own notes, so the next broken game starts from what already worked.
A disk that kept shrinking
My projects live on an external drive, but the build tools quietly dump caches on the internal one. One day I lost about 35 GB.
Claude cleared the caches, then set up a small job that runs every night and deletes the ones nobody has touched in three days. Free space still drifted down. The usual disk tools pointed at folders that, when deleted, freed almost nothing. It figured out why: the Mac file system shares copies between files, so the tools count the same space twice. It stopped trusting them and measured real free space before and after every delete.
The real culprit turned out to be a 93 GB system icon cache in a folder only an admin can read. That one needed my password. Everything else it did on its own.
A TV full of ads
My Sony TV runs Android and came with promo apps, demo modes and a home screen built to sell me things. I turned on developer mode and gave it the TV's address.
It connected over wifi, listed every app, and turned off the promos, the store demo and the stock launcher. It kept a list of every package it disabled and the command to turn each one back on. I never needed the list. I like that it exists.
Ten years of Facebook
I wanted an old conversation I couldn't find in the app. I downloaded my data export, a giant zip of HTML files, and pointed Claude at it. It unpacked it, worked out the file format, and searched ten years of messages for what I described, in two languages.
It also told me what the export doesn't contain, which saved me a second evening of looking.
The small stuff
Most days it is smaller than that:
- "Fetch AdMob" pulls my ad revenue, rebuilds a local report and writes me a three-line note on what changed.
- It checks my apps' ratings in every country's App Store, then drops reviews older than the current version so I don't chase bugs I already fixed.
- Research that used to eat an evening: how many copies apps like mine sell, whether my city publishes its planning maps as open data, what an AI video series would really cost per episode.
- Excel files with broken rows, files to merge or split, a few hundred things to rename.
The habit
I don't have a system for this. I have a reflex. Before I start anything tedious, I ask: can Claude just do this?
Usually yes. When it can't, it is because it needs a password or my hands on a device, and it says so up front.
Two things make it safe enough to hand over. It runs on my machine, so I decide what it can touch. And I made it verify before claiming: it checks that the game started, that the space really came back, that the TV still boots, before it tells me it's done.
If you don't code, that is the whole pitch. Not that it writes software. That it finishes the chore and shows you it worked.