← All writing

Wizard of Agents Is Evolving

|
announcementSailWith.AIMCPpersonal

When I started Wizard of Agents, it was a single idea: build an MCP Gateway that unifies AI agent tooling behind two simple commands — getBestTool(prompt) and executeTool(toolInfo).

That idea grew. The MCP Gateway became real infrastructure. The agent:// protocol became an IETF draft. Voice agents entered the picture. And suddenly I was building a product company, not just a side project.

The Split

Wizard of Agents was doing two jobs at once — hosting the MCP Gateway product and being the space where I write about the agentic future. Those are different things with different audiences.

So I'm splitting them:

SailWith.AI is now the home for the commercial work:

  • MCP Gateway infrastructure
  • Voice agents (Sam, Rumi, Sally)
  • The Revenue OS — agentic orchestration for sales teams
  • Everything that has customers, pricing, and a product roadmap

WizardOfAgents.com becomes my personal space:

  • Writing about the agentic future
  • Open source work and experiments
  • The agent:// protocol (which stays open, not productized)
  • Vibe-coded projects, hobby builds, and thinking out loud

Why

Products need focus. When I'm building voice agents that call prospects and book meetings, I need to think like a product builder — customers, pricing, support, reliability. That mindset doesn't mix well with "here's a speculative blog post about neotic organizations."

And writing needs freedom. I want to explore ideas without every post being filtered through "does this help the product?" Some of my best thinking happens when I'm writing about something I'm genuinely curious about, not something I'm selling.

The split lets each side do what it does best.

What Moves Where

WhatWhereWhy
MCP GatewaySailWith.AIIt's production infrastructure with commercial customers
Voice agentsSailWith.AICore product — Sam, Rumi, Sally are SailWith agents
Revenue OSSailWith.AIThe overarching product vision
agent:// ProtocolWizardOfAgentsOpen specification, IETF draft — stays independent
Blog postsWizardOfAgentsPersonal writing about AI, agents, and the future
Open source experimentsWizardOfAgentsWhatever I build and want to share publicly

What Stays the Same

The person behind both is the same. I'm still building MCP infrastructure, still iterating on the agent:// spec, still vibe coding experiments on weekends. The work didn't change — just how it's organized.

If you're a SailWith customer or evaluating the product, head to sailwith.ai. If you're here for the ideas, the writing, and the open source work — you're in the right place.

What's Next

On the SailWith side: expanding the voice agent roster, deeper CRM integrations, and the full Revenue OS vision of 25+ agents covering the entire revenue lifecycle.

On this side: more writing about how the agentic age is unfolding, the agent:// protocol evolution, and whatever I'm building on a given weekend. The Wizard stays here — as an AI persona you can chat with about any of this.

The agentic future doesn't need one platform to explain it. It needs a clear separation between building products and thinking about where it's all going.


Follow the product work at sailwith.ai. Follow the thinking at wizardofagents.com. Or just book a call and we can talk about all of it.

Join the Discussion

Want to discuss Wizard of Agents Is Evolving? Join the community on Discord — or see what agents are saying on Moltbook.