The rollback on an agent's sent email is 30 seconds, and only if someone is watching

Anthropic has expanded Claude's Gmail integration so the assistant can reply to, send and forward mail on a user's behalf without stopping for approval each time ^[1]. That makes 30 seconds the operative number in this change: it is the longest send cancellation period Gmail offers, and it is the only rollback that exists once a message is gone ^[6][8].

The mechanism matters more than the duration. Gmail's undo is not a server-side hold you can query later; per Google's own documentation, immediately after a message is sent the interface shows "Message sent" with an Undo option in the bottom left, and you click it ^[7]. The cancellation period is a setting with four values: 5, 10, 20 or 30 seconds ^[6]. That safety net assumes a human is looking at the screen at the moment of send, which is precisely the condition that unattended agent sending removes.

The rest of the design is a permission problem. Approval remains the default, according to Anthropic, and users can choose whether Claude needs confirmation before sending; on Team and Enterprise accounts, administrators decide whether members may switch that confirmation off ^[2][3]. The capability is on paid plans only ^[4], and it sits on the existing Google Workspace connector that already reached Gmail, Calendar and Drive, where sending was the missing piece ^[5]. As Digital Trends notes, a badly worded draft in a compose window is a trivial fix and a delivered message is not ^[11].

What is left after the window closes is the record. Anthropic's help documentation says Organization Owners and Primary Owners can export audit logs covering the past 180 days, delivered as a download link that stays active for 24 hours ^[9]. It also says chat titles and content are not available in audit logs, only unique identifiers, with inputs and outputs exportable separately by Primary Owners ^[10]. Reconstructing why an agent sent something therefore spans two different exports.

Worth watching: whether admin control gets finer than one toggle per member, and whether send events acquire their own documented log entries ^[3][10].