Agenten-Kompass

AGENT PROFILES

Zo

Zo · Agent platforms

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

Automate Organize office work

Zo · Agent platform

Product and access

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

01

Core features

7 features from provider sources · sources reviewed on 30 September 2026. Availability and limitations are listed directly below.

  • Create agents with the builder

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

    Source 4

  • Persistent cloud computer

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

    Source 3

  • Tools and integrations

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

    Source 3

  • Time-based and event-based automations

    The Builder can start processes on a schedule or trigger.

    Source 3

  • Multiple access channels

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

    Source 5

  • Persistence and analytics

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

    Source 3

  • Private or public sharing

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

    Source 5
02

Requirements and limits

‘Still open’ means the reviewed sources do not answer this point clearly.

  • Requirement

    Workspace access

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

    Source 4

  • Requirement

    Deploy to channels

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

    Source 5

  • Limitation

    Billing when sharing

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

    Source 5

  • Not yet confirmed

    Plan-dependent limits

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

    Source 3
03

Practical tasks

Editorial examples based on documented features. No product tests performed.

01

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.
02

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.
EDITORIAL EXAMPLE

Create an internal research agent and make it available to a team.

Your possible prompt

Design a process for new requests: capture information, sort it by topic, and create a proposed response. Plan an approval step before external actions.

Getting-started idea based on documented capabilities. Not an executed product test. Adapt the task, data, and permissions.

04

What you should know first

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.

Requirements & limitations

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

Setup

Account, agent description and connections.

Pricing model

Plan / usage. Check current terms and included quotas with the provider.

The classification indicates the scope of effort. It is not a price or performance commitment.

05

Sources from the provider

Editorial team: Michael Meierhoff · sources reviewed on . Provider information is not independent evidence of performance.

Read profile as Markdown

How we assess the sources