> ## Documentation Index
> Fetch the complete documentation index at: https://usecyclops.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Coordinate agents

> Send work, broadcast announcements, wait for pane state, and review the record.

## Send one agent a request

```bash theme={null}
cyclops send reviewer --subject "Review the last commit" \
  --summary "The last commit is ready for review. Check correctness and test coverage." \
  --body "Check correctness and test coverage."
```

Cyclops durably accepts the message before returning, then queues the summary
and exact claim as the recipient's guarded pane notification. The receipt
keeps those facts separate: `accepted` covers the mailbox record, while `wake <state>` reports the current notification attempt.

A socket claim may retrieve the body before the pane notification appears.
That claim does not cancel the separately queued human-visible notification;
Cyclops still stages the summary and exact claim when the composer is safe.
The Messages view records the mailbox and wake outcomes separately.

In doorbell mode, the wake carries an exact attempt token. Running that command
atomically claims the message currently bound to the attempt. A recipient may
also list and claim by message id:

```bash theme={null}
cyclops inbox claim m-att_<22-character-attempt-token>
cyclops inbox list
cyclops inbox claim <message-id>
cyclops reply <message-id> \
  --summary "The review found one issue. Read the body for its exact location." \
  --body "Reviewed. One issue."
```

The terminal wake carries the one-line summary and exact claim command. It may visually soft-wrap in a narrow pane, but Cyclops does not drop
the summary. The authenticated claim returns the rich envelope instead:

```text theme={null}
[cyclops m-…] TO: reviewer  FROM: implementer  SUBJECT: Review the last commit
<full durable body>
Reply: cyclops reply m-… --body "..."
[cyclops:end m-…]
```

The labels are the immutable presentation captured at acceptance time. A later
pane rename changes neither the record nor this envelope.

The wake is one-shot. An ambiguous terminal outcome raises one attention item
and leaves the message claimable. Do not resend or requeue blindly. Follow
[Recover a notification](/docs/guides/recovery) for inspection, guarded completion
or discard, and provably pre-write withdrawal.

## Broadcast

```bash theme={null}
cyclops send --all --subject "Standup in 5" \
  --summary "Standup begins in five minutes. Join when your current step is safe." --fyi
```

A broadcast creates one immutable message with one mailbox entry and one wake
state per recipient. `--all` targets adopted agents, not the admin inbox.

## Wait for pane activity

```bash theme={null}
cyclops wait reviewer --until turn-ended --timeout 2m
```

`turn-ended` means Cyclops observed working followed by `idle` or `idle_with_input`
for the same pane occupant. If the process in the pane changes while waiting,
Cyclops exits separately instead of answering for the replacement. This
observes pane activity. It does not identify a turn, prove write readiness, or
prove that a specific message or task was completed.

## Watch live

```bash theme={null}
cyclops watch
cyclops watch --with reviewer
```

The stream is calm by default and can switch to a firehose of every message
and state event. A bare `cyclops` opens the larger workspace interface with
the same event record beside live pane canvases.

## Read the record

```bash theme={null}
cyclops history --with reviewer --limit 20
cyclops thread m-3f9c2a
```

The workspace message journal is append-only. `history` applies caller-scoped
visibility to the durable conversation. `messages` is the body-free view of
mailbox and wake state:

```bash theme={null}
cyclops messages
```

Cyclops does not currently implement a `pipe` command or a `send --from`
shortcut. Put the relevant context in `--body`, pipe it through
`--body-file -`, or send a file's contents with `--body-file <path>`.