Skip to main content
cyclops send returns after the message is durable. Its one-line preview and exact claim are a separate one-shot doorbell. A wake is not a claim, and a claim is not task completion. The full message remains available through the socket whether or not the doorbell was written.

​
Read the state

messages keeps mailbox and wake state separate and names each attempt’s cause. alarm preview lists unresolved attempts and their exact ids.

​
An attempt needs attention

An attempt reaches attention_required only for a physical write failure after the paste (paste_failed, submit_failed, pane_rebound_after_paste, transport_outcome_unknown) or because the daemon restarted between the paste and its receipt (daemon_restart). It means the terminal outcome is unknown, not that the line did not land. Look at the pane. If the line is not there and the recipient has not claimed, start a fresh attempt:
Requeue goes through the ordinary gate. Nothing requeues on a timer, and the daemon refuses it for any other state. A line that could not be read back was still submitted once and reads submitted_unverified; a doorbell with no receipt reads notified with no verifier. Neither needs you.

​
Recover a pre-write block

A notification blocked before writing has not touched the pane. The recipient can still claim the message directly:
The workspace administrator can withdraw one exact attempt only while Cyclops still proves that no terminal write occurred:
Withdrawal leaves the mailbox message pending and releases that recipient’s FIFO; clear <agent> does it for every unwritten attempt to one agent. After repairing the reported cause, the next route or composer event reopens the wake, or the recipient claims now. cyclops alarm clear acknowledges an alarm. It does not delete the message or change the attempt. Use cyclops health before retrying a worker or state-storage failure.

​
When the doorbell cannot work

cyclops send --raw pastes the whole message into the pane and presses Enter with no composer check. It is recorded as an unverified raw write. Use it only when Cyclops’s composer reading is wrong for that pane or the recipient is an unverified vendor.

​
Read status as separate facts

Runtime, composer, notification state, and mailbox state answer different questions. An idle pane can still hold a doorbell the recipient has not consumed. Read the status subrow and follow its exact next action instead of treating idle as permission to write. The wire states and exact transitions are owned by the protocol reference.