amq-remote

Topics in the source

• AMQ Remote
• /amq-remote (connect)
• Answering a Buzz message (default mailbox)
• /amq-remote off
• /amq-remote mirror on|off|status
• /amq-remote status
• Status line
• Trust limits

/amq-remote gives this session its own private Buzz channel. One Buzz agent per machine, "AMQ Remote @ ", imported once, makes the channel, adds the owner and mentions them. The owner writes in that channel from the Buzz phone app or Buzz Desktop. Several sessions can be connected at once; each has its own channel. The same session connecting again gets its own channel back. A resumed session gets its channel back by itself unless the owner turned it off: a pi session within about 35 s; on macOS, a Claude mailbox seat started directly by amq coop exec claude within about 35 s; any other Claude session at its first approval dialog. A Codex session needs $amq-remote again. A different session never gets another session's channel. A session that already has its own Buzz agent keeps its DM. In Codex the skill is invoked as $amq-remote (Codex does not register / commands for skills); the commands below are the same. Codex runs sandboxed: attach writes /.amq/remote, so the first attach may be refused until the user reruns it with approval — ask for that one approval, do not work around it. Default (AMQ mailbox). Each message the owner writes in the channel (or DM) arrives as an AMQ messa

This is an excerpt. Refer to the complete source and its current requirements.