InboxZeroAI: the one thing you cannot paste into someone else’s cloud
Your inbox is the most sensitive archive you own and the one most people hand over without thinking. InboxZeroAI is an attempt to sort it out without it ever leaving your machine.
Email assistants are having a moment, and almost all of them work the same way: they read your mail on someone else’s servers. That is a strange thing to accept, because an inbox is not just messages. It is contracts, medical results, legal correspondence, salary discussions, the client list, and every password reset you ever requested. It is the single richest description of a person or a business that exists in one place.
InboxZeroAI classifies, drafts, archives and unsubscribes — the ordinary work of getting to an empty inbox — and does it with a model running on your own machine. Nothing is sent to a third party. That is the entire design constraint, and everything else follows from it.
It is being built open source, for the same reason ClawLite is: a privacy claim that cannot be inspected is a marketing claim. If the promise is that your mail never leaves the building, the code that handles the mail has to be readable by anyone who wants to check.
It also inherits something from the rest of the portfolio. Every action the assistant takes against your inbox is recorded in a tamper-evident local audit trail, which is the same idea VaultTrace applies to AI compute. If an automated system is going to archive, reply to or unsubscribe from things on your behalf, you should be able to reconstruct exactly what it did and when — without taking its word for it.
Where it stands: early. The project started in July and the first milestone is a working assistant that reads, classifies and answers locally. There is no download yet, and the honest caveat is the same as with any local-first tool — the quality of the drafting depends on the model your hardware can run, and a local model is not the largest model in the world. What it is, is yours.