OpenAI Frontier Coworkers Still Need a Familiar Door

OpenAI’s February 2026 Frontier launch, reported by Bloomberg as enterprise infrastructure for “AI coworkers,” lands in the same season vendors keep promising fewer tabs and somehow deliver more consoles. The State of Enterprise AI 2025 narrative from OpenAI shows business usage, reasoning-token growth, and structured workflows climbing fast—yet still describes employees hopping surfaces to finish a task. That gap between procurement success and daily habit is the whole story.

Macro adoption does not equal micro calm

Stanford HAI’s 2025 AI Index documents generative AI spreading across functions and geographies. Good news for boards; stressful news for anyone whose calendar is already half email. Harvard Business Review’s classic guidance on how to spend less time on email is really about coordination design: batching, intentionality, and protecting focus. AI coworkers do not automatically fix that—they can amplify it if every specialist lives behind another login.

TechCrunch’s February 2026 piece on Anthropic’s enterprise agent plugins shows the same arms race: vertical copilots for finance, engineering, design. Someone still has to decide which plugin opens when urgency hits.

The familiar door is an address, not a dashboard

via.email is deliberately boring: each specialist is an email address. You send context you already have; the model replies in-thread; humans edit before anything ships. It works alongside Frontier-style platforms—IT can govern models upstream while employees trigger work through a protocol they already authenticate to daily. See https://www.via.email and browse https://www.via.email/agents.

Three agents illustrate the pattern for mixed enterprise roles:

• Distill to Three distill.to.three@via.email for executives who need a decision memo, not a PDF vacation.
• Decode Customer Sentiment decode.customer.sentiment@via.email when a forward from support needs tone and churn-risk readouts before you reply.
• Summarize Hiring Pipeline summarize.hiring.pipeline@via.email when people ops need a single narrative out of scattered ATS exports pasted into mail.

via.email does not access your inbox without a send, does not send mail for you, and does not remember unrelated conversations—limits that keep security reviews grounded.

Read this next to the rest of the interface debate

Our essays on agent managers orchestrating from the inbox, Gmail and Outlook AI leaving workflow gaps, and context-switching taxes extend the same argument for operators who bought the platform but still live in threads.

Pilot design that actually measures behavior

Pick one high-volume workflow this quarter—customer escalation triage, weekly hiring recap, steering-deck prep. Run half the team through the vendor console, half through email-agent routing with identical review gates. Count minutes to first quality response, not vibes. If the inbox path wins, you learned something your license renewal spreadsheet never showed.