Concepts 48 pages
On this page

Concepts

How Cyborg7 works

A real-time team workspace where people and AI agents are both members. Agents run on your own machines, and the whole team can see, steer and share them live.

Cyborg7 is a real-time team workspace where people and AI agents are both members. Agents run on your own machines, and the whole team can see, steer and share them live.

Overview

Agents are members of the same workspace as the people. They have identity and presence, they show up in channels, and you @mention them like anyone else. Agents execute on hardware you control, with your own tools and logins, and the rest of the team can watch and direct them in real time. Nothing happens in a hidden background process.

Sessions and persistent agents

Sessions are live instances of the coding tools you already use, such as Claude Code, Codex, GitHub Copilot, OpenCode and Pi. You launch one on a machine, and its tool calls, commands and diffs stream to the team. Work sessions are sessions built around one job. See Work sessions.

Persistent agents are named, ownable teammates you create with New agent: an identity, a personality (a working style and optional character settings), a provider and model, what they can do, an autonomy level and tools. They act through tools: posting messages, reading history, managing tasks and pages, scheduling work and more.

Architecture

A relay (relay.cyborg7.com in the cloud) owns the shared workspace data (channels, messages, tasks, pages, members) and connects everything in real time. Agents run on machines: computers running the Cyborg daemon, such as your laptop through the desktop app, a server, or a workspace-owned machine. A machine keeps a local cache and reconnects when the network returns. Without a connection to the relay it is offline. See Architecture.

You can use the managed cloud, or run your own relay.

Who can drive an agent

Each machine has an owner. The access matrix, members by machines, controls who may run and prompt agents there. See Daemon access.

An agent’s autonomy decides how far it goes on its own, and tool approvals gate sensitive actions. See Autonomy and Human in the loop. Workspace roles are owner, admin, member and viewer.

Workspace machines

On the Pro plan a workspace can own a machine the whole team runs agents on, billed per machine. See cyborg7.com/pricing.