“Every program attempts to expand until it can read mail. Those programs which cannot so expand are replaced by ones which can.”

Jamie Zawinski’s Law of Software Envelopment lasted because it compressed a real product dynamic into one good line. Useful software does not stay in its lane. Once a system becomes valuable enough, users start asking it to absorb adjacent tasks, and historically one of the most obvious adjacent tasks was email.

The line started as a joke about software bloat, and the Jargon File entry on Zawinski’s Law still frames it that way. Artificial intelligence gives the joke a second life, but with a different visible outcome. The new expansion pressure is not toward email. It is toward chat. Software increasingly acquires a side panel, a copilot, or a conversational prompt box because agentic systems are expected to talk. Chat is becoming the front door.

The Baseline Is Chat Link to heading

The shift toward chat makes sense because classical software was relatively narrow: a computer-aided design (CAD) tool did CAD work, a payroll system did payroll, and a router routed packets. The latest software systems are different. They are built around a more general loop: observe context, interpret intent, choose tools, act, and report back.

Once software is built around that loop, chat stops looking like a gimmick and starts looking like the natural control surface. It is a generic interface for generic agency. Users do not need to learn the full feature tree first. They can ask. The system can answer, clarify, summarize, and act. The old joke was about programs expanding until they could read mail. The new visible pattern is programs expanding until they can converse.

Newer users will probably treat that conversational surface as the baseline. The expectation is shifting from “this app should have a menu for that” to “this app should understand what I mean.” Even when the software underneath remains rigid, the surface increasingly wants to look conversational.

The Basement Is Still Email Link to heading

The AI shift does not eliminate the email angle. It demotes it. Email is no longer the exciting surface. Email is the basement.

Email is where spam accumulates, reminders arrive, signups get confirmed, and password-reset or multi-factor authentication recovery paths come back to haunt you. Email is administrative residue. It is institutional plumbing. The reason AI assistants keep rediscovering it is not that email remains culturally central. It is that the world still contains suppliers, customers, schools, doctors, landlords, government offices, and assorted systems that do not expose a clean application programming interface (API). They expose an inbox.

So the more precise update to Zawinski’s law is not “every program wants to read mail.” It is something like this:

Every useful AI system attempts to expand until it can chat. The ones that need to operate in the real world eventually learn to handle email too.

That updated formulation better matches the stack we are building. Chat is the baseline interface. Email is the fallback substrate when the happy path runs out and institutional reality begins. Long before the current large language model wave, the Calendar.help paper showed why this works: people already knew how to treat an email correspondent as an assistant. The important part was delegation.

AI does not just make software more capable. It makes software more plausibly social, and organizations respond by treating it like a junior colleague. Chat is how organizations increasingly speak to that junior colleague. Email is where organizations still send it when the work turns into reminders, recovery flows, follow-up, paperwork, and the awkward administrative glue that keeps institutions running. Zawinski’s law was once a joke about feature creep. In the AI era, the front door becomes chat, and the basement still smells like email.

References Link to heading