# Zo

Create custom agents through chat and deploy them with cloud computers, integrations, and automations.

Canonical profile: https://agenten-kompass.mmeierhoff.chatgpt.site/en/agents/zo/
Editor: [Michael Meierhoff](https://agenten-kompass.mmeierhoff.chatgpt.site/en/about/)
Sources reviewed: 2026-09-30
Basis: provider documentation. Examples are editorial suggestions, not hands-on product tests.

## Overview

Zo is a platform for creating, deploying, and sharing custom agents. Zo Computer is a separate personal agent product from the same provider family.

- Provider: Zo
- Product family: Zo
- Profile type: Agent platform
- Environment: Cloud platform
- Connections: Cloud computer and communication channels
- Setup: Account, agent description, and connections
- Pricing model: Plan / usage

## Key features

### Create agents with the builder

A chat builder turns a task description into agent instructions, tools, and automations.

Source: https://zo.app/docs/quickstart

### Persistent cloud computer

Each deployed agent receives its own environment for code, files, and state between runs.

Source: https://zo.app/docs/concepts

### Tools and integrations

Tools and connected services are part of the agent definition; the specific selection depends on configuration.

Source: https://zo.app/docs/concepts

### Time-based and event-based automations

The Builder can start processes on a schedule or trigger.

Source: https://zo.app/docs/concepts

### Multiple access channels

Deployed agents are available through web, Zo Mobile, Slack, and Telegram.

Source: https://zo.app/docs/publishing

### Persistence and analytics

Memories, artifacts, and evals support ongoing refinement of an agent.

Source: https://zo.app/docs/concepts

### Private or public sharing

Agents can be invited selectively or offered publicly; integrated payments manage usage costs.

Source: https://zo.app/docs/publishing

## Requirements and limits

### Workspace access

Requirement: Creating and deploying an agent requires Zo access with a workspace.

Source: https://zo.app/docs/quickstart

### Deploy to channels

Requirement: Web, mobile, Slack, and Telegram access requires a deployed agent.

Source: https://zo.app/docs/publishing

### Billing when sharing

Limitation: For private or public sharing, the operator determines who pays for AI and compute usage.

Source: https://zo.app/docs/publishing

### Plan-dependent limits

Not yet confirmed: Current public documentation does not provide a complete list of quotas and feature approvals across all plans.

Source: https://zo.app/docs/concepts

## Example workflows

### Morning research overview

- Your input: Topic, approved sources, and desired time
- Possible result: A scheduled agent run creates a concise briefing with references.
- What to check: Open sources and verify claims before sharing.

### Team questions on a specific topic

- Your input: Reviewed documents and a private Slack channel
- Possible result: A deployed agent answers questions in the selected channel.
- What to check: Check answers against the documents and limit channel access.

## Context

Quality depends on the workflow, data, model, and approvals. Check integrations and usage limits before use.

Primary documentation reviewed. Features, integrations, and availability may depend on the workspace and current platform version. Zo Computer is identifiable as a related, separate product.

## Sources

- https://zo.app/

- https://zo.app/docs

- https://zo.app/docs/concepts

- https://zo.app/docs/quickstart

- https://zo.app/docs/publishing

[Sources and method](https://agenten-kompass.mmeierhoff.chatgpt.site/en/sources/)