Vercel CEO Guillermo Rauch thinks the future of multi-agent work may look like one agent. Vercel gives employees one front door. behind it, the company harness routes each request to the right knowledge, tool, or specialist agent. employees shouldn’t need to understand the agent architecture. they should just ask... the company. here’s how to build the shared harness behind it.show more

built this before, the front door's easy. the routing logic behind it is where all the bugs live.

agreed

All paths converge back to modular monolith architecture

Amen This is my entire product thesis at precision One agent to talk to, who configures background workers to do the other jobs and manages them The answer to everything is the same: “talk to Claudia” v easy for non-AI native ppl to understand

nicely done

That’s a clever inversion of the multi-agent hype – one front door with hidden routing. Makes sense for marketing stacks too; most teams don’t need to know how the attribution stitching happens, just that it does.

@xHub_AI Hola Placido, Por favor, me puedes mandar una invitación? Saludos

Give me one interface, then let the harness route the work behind it.

Vokal ( is the shared harness that makes this real. One front door for the whole company. Behind it your Claude Code, Cursor, Codex and specialist agents stay fully powered while Vokal handles routing, persistent memory, identity and live channels. Employees just ask. They never need to understand the architecture, chase private sessions or re-explain context. The entire team gets visibility, ownership and the ability to review or steer in one place. That is the layer missing when multi-agent work stays fragmented.

This is the way.

The one-door UX is right, but it relocates the hard problem. The question stops being "which agent do I use" and becomes "which one silently answered wrong, and who owns it." A router without a confident "escalate to a human" path is just a single door for confident failure.

One front door for every agent, that's a clean way to simplify things.

Exactly. The user sees one system. The complexity stays underneath.