I let an AI sort my inbox, and sorting is all it does
# I let an AI sort my inbox, and sorting is all it does
My inbox used to be the first thing that wrecked my day. I would open it in the morning, find forty new messages, and burn twenty minutes just deciding what deserved attention. Reading was never the bottleneck; I read fast, and so does everyone. The expensive part was the sorting: working out which three messages actually needed me and which thirty seven were receipts, newsletters, alerts, and threads I had been copied on for no reason. All of that deciding happened before I had done a single useful thing, and it spent the sharpest part of my morning.
So I built a small system that does the sorting for me. It reads each new email as it arrives, decides what kind of thing it is, and hands me a short list of the ones that represent real work. Everything else gets filed somewhere findable that I never have to look at. What follows is how it works, what it is allowed to touch, and where it still gets things wrong, because the honest version of this is far more useful than the magic version people usually get sold.
A sorter, and deliberately nothing more
The words inbox and AI in one sentence usually promise something dishonest, so let me define the machine precisely. It writes no email. It replies to nobody, and nothing ever goes out in my name. Its entire job is to place each incoming message into one of three buckets.
The first bucket is actions: messages that need a real decision or a real reply from me. The second is things to know: useful, non-urgent items like delivery updates, receipts, and confirmations I might want later. The third is noise, the material I would have deleted without a second thought.
That is the whole machine. Everyone imagines the glamorous version, a model that answers in your voice and empties the inbox while you sleep. The part that turned out to be valuable is far more boring: something reads the pile and tells you where to look first. That one dull job was what had been eating my mornings all along, ahead of the reading and far ahead of the replying.
How it reads a message
When an email lands, the system extracts the parts that matter, meaning the sender, the subject line, and the body, and passes them to a language model along with a set of instructions I wrote myself. Those instructions are where nearly all of my effort went.
They spell out, in plain words, what an action looks like for me specifically. A person asking a direct question is an action. An invoice with a due date is an action. A colleague asking for a decision is an action. A newsletter is never an action, however urgent its subject line pretends to be, and a receipt is a thing to know rather than a thing to do.
The model brings one genuine strength to this: reading the gist. It reliably understands that "hey, could you send that over by friday" is a request even when it is buried under three paragraphs of pleasantries. What it cannot know is my priorities. It has no idea which clients matter more, which threads I am quietly avoiding, or which sender always signals something urgent. So I never ask it to know those things. The model handles the language. The meaning of the rules stays with me. Blur that line, let the model start guessing at your priorities, and it becomes confidently wrong in ways you stop catching.
The one screen I open in the morning
Sorted actions land on a single short list, and that list has replaced my inbox as the first thing I open. Most mornings it holds five or six items, each one a genuine task, each with a one line summary the model wrote so I know what it is before clicking in.
The things-to-know bucket feeds a quieter list I skim once a day, and some days barely that. The noise bucket I simply never open. It sits there, filed, in case I ever need to dig something out.
The effect is hard to convey until you have lived with it for a week. Opening six real tasks feels like reading a plan for the day. Opening forty unread messages feels like wading into a flood before you are allowed to start working. My inbox did not shrink and the volume of email never changed. The sorting simply moved to before I look instead of after, and that single change did more for my mornings than any productivity app I have tried, and I have tried plenty.
The powers it will never have
Now the part that matters most, which is everything the system is forbidden to do. It cannot send email. It cannot reply to anyone. It cannot delete a message, including the junk I am completely certain is junk, and it cannot mark anything as read on my behalf. Those powers were kept out of its hands deliberately and permanently.
People ask why, since auto-clearing the obvious junk would surely save even more time. The answer is that the cost of a mistake is lopsided. When the sorter misfiles a real action into the noise bucket, I lose a few seconds finding it once I notice a reply never went out. Harmless. If the system could delete or reply on its own, one wrong call would send the wrong message to a client or discard something I needed, and the damage would exist in the world before I could catch it.
A sorter that errs sends me looking in the wrong list for a moment. An actor that errs can hurt my work and my relationships. So the line is drawn hard: the machine reads and files, while every action that touches the outside world, every send and every delete, stays with me. I do not consider that timid. I consider it clear eyed about where a mistake is cheap and where it is genuinely expensive.
What it costs to run
People always want numbers, so here are the real ones. Each incoming email gets one read by a metered language model, and a single read costs a tiny fraction of a cent. A normal day of email runs a few cents. A busy month adds up to a couple of dollars. One person's inbox simply does not generate enough volume to make this expensive, though I want to be straight that it is a paid service rather than a free one. It merely happens to be very cheap at this scale.
The real bill was the setup. My first version classified half my newsletters as actions because their subject lines were loud and pushy. Fixing that took a week of watching it sort, correcting it, and refining the instructions until the judgments got genuinely sensible. That attention was the true price, and the pattern repeats across every small automation I have built. The tool costs pocket change. The taste to configure it well is what actually takes something out of you.
Where it still gets things wrong
It misses every week, and I would rather describe the misses than pretend they stopped. Occasionally a real request lands in things-to-know because it was phrased softly, with no question mark and no due date, just a quiet ask folded into a friendly note. And once in a while a newsletter engineered to look like a personal message sneaks onto the action list and wastes a few seconds of attention.
Neither failure costs much, and that is the design rather than luck. Because the system never deletes and never replies, the worst case of a wrong sort is a message sitting one list away from where I expected it. The daily skim of the things-to-know list exists precisely to catch the real items that slipped. I will take a sorter that is right roughly ninety percent of the time and physically incapable of damage over one that claims perfection and is trusted to act alone. A tool's confidence tells you nothing about whether it deserves the keys.
Should you build one
It depends entirely on your inbox. If you receive a dozen emails a day and already feel on top of them, this is machinery for a problem you do not have. If you open your inbox each morning and feel that specific dread where the volume itself stops you from starting, a sorter genuinely changes the shape of the day.
Start smaller than I did. Two buckets, action and not-action, driven by a handful of plain rules. Live with it for a week and watch where it gets confused. Then add one rule that fixes the most common mistake, and repeat. Mine grew exactly that way, one correction at a time, until it fit how I actually work. It never made me faster at reading or writing email. It removed the pile as the first decision of my day, and that one decision turned out to be the costly one. More honest write-ups of small systems like this live at [xavierfok.com](/).
Get new guides and videos first — join the Telegram channel.