Role
It maps to a job you were about to hire a human for.
AI Employees
Loading AI employees
AI Employees
Start with the job you were about to hand to a person: one concrete task inside a Cloud workspace, with Hermes or OpenClaw as the runtime choice.
An AI employee = role + tools + first job + human confirmation points + memory + runtime. It is not a chat persona; it is a role that takes responsibility for one job.
It maps to a job you were about to hire a human for.
It uses the sources, APIs, and templates you authorized.
One concrete, verifiable outcome — not a bag of vague skills.
Outbound, paid, or public changes land in an approval queue first.
Local memory stays with the employee; Instance Knowledge belongs to the workspace.
Hermes or OpenClaw can carry the entries, tasks, tools, and reviewable state for the employee.
Chatbot — you ask, it answers.
AI employee — it takes one job and moves it forward.
Copilot — it shadows you all day.
AI employee — it works on its own rhythm and comes back when it matters.
Fixed automation — does not judge, does not ask.
AI employee — pauses for approval the moment a decision is yours.
Choose the one job from Use Cases you want to stop doing yourself.
One voxyz Cloud workspace wires runtime, memory, approval queue, entries, and schedule.
It queues the items that need your call, with the context.
Decisions, taste, people, and roles stay available the next time.
Add inbox, research, and support employees into the same workspace later.
Not a prompt wearing the word "team". The team parts are visible: inbox, work state, and Instance Knowledge.
Every item that needs a decision or an outbound action lands in one queue.
Who owns what, what is blocked, and who you are waiting on — all visible.
Decisions, rules, people, and taste persist so a new employee does not relearn them.
Pick the job you want to stop doing yourself first.
Builders who open five tools before they know what matters today.
Founders sorting email, DMs, leads, and partnership asks before lunch.
Small teams answering support and community threads.
Builders who want a weekly topic, competitor, or market scan they did not do by hand.
Read-only by default. Anything that changes an outside system lands in the approval queue.
Only the sources you authorize. Nothing pretends to read what it never saw.
Outbound replies, commitments, spending, and public content changes need a tap.
Pause, stop, or revoke at the action level or the whole employee.
Start with the work you were about to hand to a person. Over time, the same workspace can become the start of an AI-native team.