Skip to content

These six concepts cover almost everything in CrossMind.

An agent is a persistent AI worker with its own identity, memory, skills, tools and settings. You might have one agent for social media growth (“Nova”), one for research (“Atlas”) and one for operations (“Dexter”). Each agent keeps its own sessions, skills and MCP servers, and can be messaged by email.

You organize agents (and projects) on the Home page, as a 3D “Office” view or a plain list:

Home 3D Office view with agent desks and project rack

While an orchestration is live, the Office view adds a Live orchestration sessions panel under the scene: member sessions grouped by their parent, with status, runtime and context usage at a glance (hidden when nothing is running).

A session (also called a run) is one unit of work with an agent. There are three types:

TypeWhat it isWho drives
CopilotA conversation: chat, ask, iterateYou and the agent
Direct taskA bounded one-shot task with an input formThe agent, once
Autonomous taskA goal the agent pursues start-to-finishThe agent

Sessions stream their output live, meter context usage, and can pause for approvals. An agent can also orchestrate: one leader session spawning member sessions (see Orchestration).

A runtime is the CLI harness that actually executes a session: Claude Code, Codex, Cursor CLI, ZCode, and more. You pick a runtime per session (or leave it on the workspace default), and CrossMind routes the work to the computer that has it, or to the cloud runtime which needs no local setup.

A skill is a playbook: a SKILL.md file (plus scripts and references) that teaches an agent how to do one thing well, such as “compile a research brief” or “triage the inbox”. Enable, disable, install from GitHub/URL, evaluate them, or share a public install link. See Skills.

Agents reach the outside world through MCP (Model Context Protocol) servers: built-in ones like browser control, or custom ones you configure per agent. Every tool has a known context-token cost, and the settings page totals it for you. See MCP tools.

A computer is a paired machine (yours, or a teammate’s) that runs the CrossMind daemon. Pairing takes one code; after that the machine contributes its installed runtimes, files and local browser to the workspace. See Computers.