Websites were the warm-up
You shipped a web page without touching code. Here's what the same loop can build now: tools, assistants, and toolbelts.
In April I wrote about my wife shipping features to a live website by typing into an Apple Note. The point of that post was simple: the deploy became invisible, so the only skill that matters is knowing what you want.
That post was about websites. A website is a thing people look at.
Since then, OpZero has grown three capabilities that are a different species entirely. They're things people (and AIs) can use. And the loop for building them is the same one you already know: describe it in plain English, iterate in chat, ask for a deploy, get a URL.
This post explains the three, in order of how strange they'll sound at first: tools, assistants, and gateways. No engineering background assumed. If you can describe a chore, you can build all three.
Tools: teaching your AI a new trick
Here's the mental shift. When you chat with Claude, it can talk, write, and reason. But out of the box it can't do much in your world. It doesn't know what's on your reading shelf. It can't check the river level near your house. It has a brain and no hands.
A tool server (the technical name is an MCP server, and you'll see that acronym around) is a set of hands you build for it. It's a small program that lives at a URL and offers the AI a few specific abilities: "save this quote," "check the water level," "add this to the grocery list," "look up today's schedule."
Once it exists, you connect it to your AI chat app the same way you'd connect a calendar, and from then on the AI just has that ability, in every conversation, forever.
Two real ones from my house:
Fragments. I read a lot, and I kept losing good passages. So I described a tool to Claude: save an excerpt with the book it came from, list what I've saved, surface a random one when I ask. Claude wrote it, OpZero deployed it, and now "save that quote from the Ephrem book" is something I can just say, mid-conversation, about anything I'm reading. The excerpts persist. They're mine. They live at a URL I own.
A river gauge. I paddle on the Chattahoochee, and whether a training session is worth doing depends on flow data the government publishes for free. I built a tool that fetches it. Now "how's the river looking" gets a real answer with real numbers, because the AI has a hand that can reach that data.
Notice what these aren't. They aren't apps with screens and buttons. Nobody "opens" Fragments. It's a capability that got bolted onto every conversation I have. That's the new category: not software you use, but abilities your AI has because you gave them to it.
You could build: a tool that saves ideas to your own idea box, one that checks your league's game schedule, one that tracks the family chore rotation, one that logs what you ate. Anything shaped like "I wish I could just tell the AI to ___ and have it stick."
Assistants: a specialist you can hand to someone else
Tools give your AI new abilities. An assistant goes one step further: it's a whole AI persona, with its own knowledge, its own tools, and its own address, that other people can talk to.
The one I use as the example is Hooch Coach. It's a paddling conditions assistant. It knows the Chattahoochee, it has the river gauge tool built in, and it has a coaching voice I wrote in one paragraph of instructions. Anyone I share it with can ask it "is tomorrow morning worth paddling?" and get an answer grounded in live data, in the voice I gave it.
I didn't train a model. I didn't write AI code. I described a specialist: here's what you know, here's the tone you take, here are the tools you can reach for. OpZero wraps that description around Claude and gives it a home.
Think about who you'd build one for. A new-member assistant for your club that actually knows your club's rules and calendar. A homework helper tuned to how your kid's teacher wants math shown. A "what's our policy on that" assistant for a small business, loaded with the actual policies. The pattern is always the same: knowledge plus tools plus a voice, wrapped up and handed to someone who just wants answers.
The website post said your contribution is taste. Here it's even clearer. An assistant is nothing but taste: what it should know, how it should sound, where it should look things up. All domain, no engineering.
Gateways: one plug for the whole toolbelt
This one sounds the most technical and is actually the simplest.
Say you've built four tools over a few months. A grocery list, a chore tracker, a reading shelf, a river gauge. Each lives at its own URL, and each has to be connected to your chat app separately. Four tools, four plugs. Your spouse wants three of them, your book club wants one, and now you're managing a small tangle of connections.
A gateway is a power strip. It's one URL that bundles whichever tools you choose. You connect the gateway once, and everything behind it just works. Want to hand your family "the household setup"? That's one link, and behind it: groceries, chores, calendar helpers. Want a separate "morning briefing" bundle with news, weather, and river conditions? Different gateway, different link, same tools reused underneath.
The reason this matters for non-engineers is curation. The tools are ingredients. The gateway is the plate. You decide which abilities travel together and who gets which bundle, and you change your mind later without rebuilding anything.
The same loop, one level up
The April post described a three-piece loop: an AI that writes the code, an editing surface you already use, and a deploy that's invisible. Every word of that still applies. What changed is what comes out the other end.
Then: a web page. A thing at a URL that people look at.
Now: an ability, a specialist, or a bundle. Things at URLs that people and AIs use.
And the honest caveats still apply too. These are small, specific builds for you and the people near you, not products. You'll hit ambiguity and iterate. You still have to know what you want, and knowing what you want is still the whole job.
How to actually start
- Finish this sentence: "I wish I could just tell the AI to ___ and have it stick." That's your first tool.
- Open claude.ai or Cowork and describe it. Say what it should remember, what it should fetch, what you want to be able to say to it.
- Ask it to deploy to OpZero. You get a URL and a connect button.
- Use it for a week. Then build the second one.
- When you have two or three, put them behind a gateway and hand the link to someone you love.
Somewhere in your head there's already a candidate. The quote box, the chore wheel, the club helper. It's been waiting on infrastructure that no longer stands between you and it.
You still don't have to be a developer. Now you don't even have to be building a website.
Try OpZero at opzero.sh. The original post in this series is You don't have to be a developer.