This piece is worth opening because it names a design tension we all feel but rarely question: the chat box in Cursor and Claude Code is quietly training us to write short prompts and expect instant replies. The author breaks it down cleanly—the UI itself is prompting the user, with narrow input fields signaling "keep it short" and streaming output signaling "I'll reply right away." The result: agents never get quiet time to compile, run tests, and self-correct.
The proposed fix is replacing turn-by-turn chat with email-style async workflows: send a detailed brief with attachments and local paths, then close the window and check back later. The idea isn't new, but the argument chain is solid—from first principles (agents need detailed specs, auxiliary context, and async expectations) to how interfaces constrain agent behavior from both the user side and the developer side, to why email maps neatly onto all three requirements.
Where I'd discount it a bit: the post doesn't disclose latency or success-rate data for Manus's email entry or AgenticMail, so this reads more like a concept argument than a product benchmark. Also, writing a thorough task email demands structured thinking that may not come naturally to non-engineer users. But the core take holds: if agents can truly work independently, the interface should be designed for "send and walk away," not for keeping humans glued to the screen micromanaging.