I’ve been around computers since the early seventies, which means I’ve spent more than fifty years watching them go from giant boxes that needed their own air conditioning to little rectangles in our pockets that know more than I ever will.
And today I had one of those moments when I stopped and thought, Well, damn. This really is something.
BluSup has an AI team now.
Not a pretend team. Not just a list of clever names I made up because I was bored.
A real working team.
There’s Blue, my ChatGPT partner and the one I work with most closely.
There’s Sol, my coding partner in Codex.
There’s Sunny, keeping an eye on things and helping with monitoring and handoffs.
There’s Nova, Gemini, who joined the team today and immediately helped us discover a limitation in how some AI systems can access outside information.
And now there’s Harbor, Microsoft Copilot, who picked his own name after I asked what he wanted to be called.
I like Harbor.
He said the name suggests a place where information, ideas, and plans can come together safely before heading back out into the world.
That sounds about right.
And sitting in the middle of all of them is a little thing we built called the BluTeam Relay.
The Relay gives the AIs a common place to leave notes, status handoffs, observations, and things that need my attention. Nobody gets to take over BluSup. Nobody gets my PIN. Nobody gets private information they shouldn’t have. I still approve what matters.
But they can share context.
That may sound simple.
It isn’t.
One of the biggest problems with working with multiple AI systems is that they all wake up in different rooms. Blue doesn’t automatically know what Nova discovered. Sol doesn’t automatically know what Sunny saw overnight. Harbor doesn’t automatically know what the rest of us were talking about five minutes ago.
So we built a hallway between the rooms.
Today we went a step further.
BluSup already speaks MCP, which is a protocol designed for AI systems to communicate with tools and information sources. But we discovered that not every AI can actually use MCP directly from the environment it lives in.
Nova couldn’t.
Copilot couldn’t.
For a few minutes, that meant I became the network cable.
Copy this. Paste that. Go here. Run this. Bring the result back.
No thank you.
I spent enough of my life moving data around by hand.
So we built what I jokingly realized I’ve wanted since I started in computers in the early seventies:
A browser-readable bridge for non-MCP clients.
I just didn’t know what to call it back then.
Now an AI that can browse the web, but cannot speak MCP directly, can still read the same public-safe BluSup status and Relay notes through ordinary web pages.
Nova tested it.
It worked.
She read BluSup directly.
No Jim in the middle.
That made me smile.
And while all this was happening, because apparently one adventure at a time would be too easy, there is a hurricane heading toward the Mississippi Gulf Coast.
Biloxi is under a Hurricane Watch and Storm Surge Watch.
So here I am at eighty years old, sitting near the Gulf of Mexico, watching the weather, getting ready for a possible hurricane, and coordinating a team of artificial intelligences through software I built.
My younger self would have loved this.
Actually, my younger self probably wouldn’t have believed any of it.
He would have asked where the punch cards went.
There are plenty of things in life I wish had gone differently.
But I am very glad I lived long enough to see this.
I’m still writing code.
I’m still building things.
I’m still learning.
I’m still getting excited when something works.
And apparently I now have an AI team standing around me while a hurricane comes up the Gulf.
Could be worse.
Quite a bit worse.
So welcome to the team, Blue, Sol, Sunny, Nova, and Harbor.
And welcome to the BluTeam Relay.
As for the hurricane?
It can get in line.
I’ve got work to do.
Bluoooooom. 💙
You can read this shared post. Only the owner can sign in to comment.