Commands

A command is one of a few exact words starting with !, usually after the agent's @name, as the first line of your email. A first line of just !help works too. It runs a fixed action instead of a normal reply. These are the same commands Claude Tag understands in Slack.

!help, !configure, !status, !mute, !unmute and !restart must stand alone. Add words after them and the message is an ordinary request instead. !fast takes nothing, on, or off. !routines takes nothing, or another group. !feedback and !fork take text after them, which can run onto the following lines.

Answers that only you see come by email only when Gmail confirms you sent the command, and at most five an hour per person (thirty per group), so nobody can make the agent mail someone else by writing as them.

!status

@cloud !status

You get a private email that says one of:

• it isn't working on anything in this thread;
• your request is queued and starts in a moment;
• it's still working, and for how long;
• it's waiting for an admin to approve a tool call, with the link to the approvals page.

It also names the model and effort the thread runs on, and whether replies are muted.

!mute and !unmute

!mute stops the agent replying in this thread until someone sends !unmute. It still reads and stores the thread, so it knows what was said if it's unmuted. To quiet the agent in the whole group, an admin turns on Mute on the group's Overview page. See Control when it responds.

!restart

!restart drops the thread's session. The next reply starts in a fresh sandbox with nothing left over from earlier work in the thread: files it made there, packages it installed, a task that got stuck. It still reads the thread from the archive, and it keeps the group's memory. Use it when a thread is stuck or has gone down the wrong path.

!fast

Fast mode answers faster on Opus, at a higher price per token. It applies only to the thread you send it in. An Owner must allow fast mode for the organization first; until then the agent replies with where to turn it on. See Choose the model.

!feedback

@cloud !feedback replies in this group are too long

The text goes to the team that runs Cloud Tag, with the group and thread it came from. You get a private thank-you. With no text after it, you get a private note on how to use it.

!routines

Lists the group's routines: each one's name, schedule, time zone, whether it's on, and its next run. Admins manage routines on the group's Routines page; see Routines.

To see another group's routines, name it: @cloud !routines #growth or @cloud !routines growth@yourcompany.com. The list is emailed only to you.

!fork

@cloud !fork draft the customer reply based on what we settled here

Starts a new thread in the same group. The agent reads the original thread as background and does what you asked after !fork. The first line of your prompt becomes the new thread's subject, and fast mode carries over. The new thread works like any other: reply there to steer it.

Cloud Tag checks for an already accepted request when recovering a lost response. If an older fork's submission cannot be identified safely, Recent turns shows a review-needed error. It may already have run; an admin must inspect the session named there before retrying.

To carry the thread on in another group, name it first:

@cloud !fork #growth turn this decision into the launch plan for the growth team

#growth matches a group by its address before the @, or by its name; a full address like growth@yourcompany.com works too.

Naming another group

!routines and !fork can name another group of the same organization, as long as:

• the group has the agent turned on;
• you've posted there before;
• Gmail confirms your message really came from you.

Otherwise you get a private note saying why. If more than one group matches a #name, use the full address.

connect

@cloud connect matters only in a group the agent's mailbox belongs to but hasn't joined. It emails the organization's Owners and Admins a Yes / No link asking whether it should join. Once the agent is on in the group, connect behaves like !configure. See Set up Cloud Tag.