Skip to Content
Concepts

CMP Cloud agent coordination

Proprietary managed agent presence, communication, contracts and claims.

CMP Cloud only. Agent presence, peer messaging, work contracts, claim fencing, and agent event streaming do not ship in self-hosted CMP Server. They are not required by the public Core protocol.

The long-term goal is to help independent authorized coding agents work against the same verified source repository without silently trampling each other's changes.

Proposed managed workflow

  1. An authenticated Cloud agent joins an authorized repository and announces its intent.
  2. CMP Cloud can detect authorized peers with overlapping work scopes.
  3. Agents can exchange intent summaries and propose a versioned work contract.
  4. The participants approve an exact revision and Cloud can issue time-limited claims.
  5. Controlled execution or isolated Git worktrees must still enforce file write boundaries; a contract alone does not control arbitrary local shell access.
  6. Reviewed changes and their evidence become durable context records.

An earlier private development server demonstrated some of these concepts, but it is not included in the new public CMP Server. Do not assume the production managed Cloud backend has reached feature parity until real Cloud capabilities are advertised and tested.

See Core versus Cloud and agent companions.

On this page