Example — not a product screenshot
MiraResearch
Awaiting approval
Compared three sources on handoff. The brief is ready. Nothing ships until you say so.
नाम nama — a name, an identity
Every agent has a name, and every name has a job.
Namabots is a roster of named agents. You hire each one for a purpose: research, building systems, maintenance, or the routines that fill a day. You assign the work. They keep going.
Your agents, always working. You approve.
This is not a tool for minting anonymous bots. If it has no name and no job, it is not on the roster.
How it works
You name the work. They do not invent a factory.
A namabot is someone on the roster, not a button that spits out another chatbot.
-
1
Name the agent and the job
Identity comes first. The purpose is part of who they are, not a costume you add later.
-
2
Assign the work
You say what done looks like. Research, a system, upkeep, or a routine — one job, clearly held.
-
3
They keep going
The agent stays with that job between your check-ins, instead of waiting for a fresh prompt each time.
-
4
You approve what ships
Nothing leaves on its own. Your agents, always working. You approve.
Roster
Four purposes. Four names. Not a creation wizard.
Scroll the roster. Each face is a different agent with a job already chosen. You are not spinning up a generic bot.
Research
Mira keeps the reading.
Mira goes through sources, lines up where they disagree, and brings back a brief you can approve. The job is research — not “be a chatbot.”
Build systems
Kato builds what has to last.
Kato wires the system around the work: steps, handoffs, and parts a person can still read. You get a system, not another unnamed bot.
Maintain
Nila stays after the launch.
Nila watches what is already running. Drift, failed checks, and quiet breakage get a named owner and a fix you can approve.
Daily routines
Soren carries the day that repeats.
Soren holds the checklist, the follow-ups, and the loops you should not rebuild every morning. Same name tomorrow. Same job.
Features
Purpose you can point to.
A roster, not a blank box
You see who is hired and what they are for. Names stay attached to the work.
Status in words
Working, waiting, or ready for you. Color supports the label. It does not replace it.
Approval before anything ships
Agents keep going on the job you gave them. You still decide what leaves.
Not a factory
This is not about generating namabots.
Identity and purpose come first. Namabots is not a wizard that mints anonymous chatbots, and it is not a factory line for “create a bot.” You do not generate a namabot. You give an agent a name and a job: research, building systems, maintenance, or daily routines. Then you approve what ships.
Not this
Generate a namabot
No purpose. No name worth keeping. Another blank chatbot.
This
Name an agent, then give it a job.
Mira researches. Kato builds. Nila maintains. Soren runs the routine.
Early access
Join the waitlist
We are opening namabots slowly. Early access, not a menu of plans — a place in line for named agents that already have a job.