Back to docsOverview

What is Zero?

Zero is an AI teammate from VM0 that delivers finished work, not replies.

Last updated May 27, 2026 · 5 min read

You're a few tools into a workday: 30 unread Slack messages, a half-finished PRD in Notion, a customer email asking for help, a dashboard that needs a weekly write-up. Each task is small. Together they eat an hour you don't have.

Zero is the AI teammate that takes that hour back. You tell Zero the outcome you want, like "summarize the thread, file a GitHub issue, draft the customer reply", and Zero does the work.

Behind the scenes, Zero figures out which of your tools to call (Slack, GitHub, Notion, Gmail, your CRM, your warehouse), chains them together, and hands back a finished artifact. You don't pick the tools or wire them up. You describe the outcome.

One teammate, every channel you work in

Zero is built by VM0. The same teammate, with the same context, same memory, same connectors, is reachable wherever you happen to be:

  • Web app. The VM0 web app is the default workspace, with full session history, replay, and forking.
  • Slack. DM Zero, or @Zero in any channel; replies land in-thread.
  • Telegram. Same Zero, on mobile, when you're away from your desk.
  • Phone. Call Zero, or have Zero call out for briefings, reminders, and customer follow-ups.

Switch channels mid-task. A request started on the phone can be picked up in the web app; a Slack thread can become a scheduled morning brief. There is one Zero, not five.

What Zero is not

Zero is not a chatbot, a workflow builder, or a prompt library.

  • Not a chatbot. Zero produces artifacts (a draft, a PR, a slide deck, a Slack reply), not a paragraph of "here's what you could do."
  • Not a workflow builder. There are no nodes to drag, no triggers to wire up. You describe the outcome in plain language and Zero figures out the steps.
  • Not a prompt library. You don't memorize commands. The same request that worked yesterday works today, and Zero asks for clarification only when something material is unclear.

A typical morning with Zero

It's 8:00 a.m. on a Monday. Yesterday you scheduled Zero to brief you:

"Every weekday at 8 a.m., DM me: (1) unread @mentions in Slack, (2) GitHub issues assigned to me sorted by age, (3) today's calendar, (4) one focus suggestion."

By the time you sit down, your Slack DMs already contain:

Good morning. Five @mentions overnight: three need a reply today; two are FYI. Three issues are blocking a teammate (links inline). One meeting at 10 a.m. with prep notes attached. Suggested focus: ship the auth migration PR before standup so the team can review it.

Time spent reading: 30 seconds. Time saved skipping the morning catch-up: roughly 20 minutes.

Through the day, the same Zero handles the rest:

  • At 2 p.m. you @Zero in #bug-report with a vague issue. Zero searches GitHub for similar reports, classifies severity, files a structured issue, and replies in the thread with the link.
  • At 5 p.m. you ask Zero, over Telegram, on the walk home, to write a 60-second changelog video for the new feature. Zero drafts the script, generates an AI-avatar voiceover, syncs screen recordings, and exports a ready-to-share MP4.

None of this requires a new tool. Zero uses the ones your team already has.

How a request becomes a result

Every Zero session follows the same shape:

  1. You message Zero. Web chat, Slack DM, channel @mention, Telegram, a phone call, or a scheduled trigger.
  2. Zero plans the work, silently. It reads your message, picks the connectors it needs, and decides what context to fetch.
  3. Zero asks only when it must. No interrogation. If everything is clear, Zero just runs.
  4. Zero uses your tools on your behalf, without ever seeing your passwords or login tokens.
  5. Zero returns the artifact, plus a full session log of every step it took.

How Zero is different

Three things distinguish Zero from chat-based assistants:

  • Connected execution. Zero ships with 100+ first-party connectors maintained by VM0, plus custom connectors for anything internal to your team. Most "AI agents" can only describe using tools. Zero actually picks the right ones, chains them, and uses them.
  • Outcome-first. Zero is judged on the artifact, not on the conversation around it. Sessions that don't produce a result are visible in the log, so you can see what went wrong.
  • You stay in control. Zero never sees your passwords or login tokens. They stay locked on the VM0 platform. Every tool Zero touches shows up in the session log: which account, what it read, what it changed, when. If anything looks off, you can revoke access or tighten a permission in one click.

Together, the result is an AI teammate that reaches into the real work, on every channel you already use, and shows you exactly what it does with your tools.

Where to go next