Threads
Reply to any comment, at any depth. Deep threads flatten after three levels.
Mentions
@ a teammate to notify them. @Dench to bring the agent into the thread.Follow
Commenting, being mentioned, creating, or being assigned follows the record.
In the app
The comment box is the same editor as Notes: slash commands, images, tables, and the@ picker for files, records, meeting moments, people, and Dench.
↵ posts, Shift+↵ adds a line. Hover a comment for reactions, Reply, and ⋯ (edit, copy
link, delete). The Follow toggle in the section header controls whether
you hear about activity on the record.
Mentions are links
A mention is a markdown link, so comments and notes round-trip as plain markdown:dench members list. Plain @Kelly text notifies nobody.
CLI
--dench is fire-and-forget: the command returns the comment id and Dench’s
answer lands as a threaded reply shortly after. Poll comments list or read
your notifications.
API
/<workspace>?entry=<object>:<entryId>&comment=<commentId> opens the record
scrolled to that comment. Comments are also searchable from ⌘K.
@Dench
Mentioning Dench runs the same agent that answers in Slack. It reads the thread it was mentioned in, replies as a comment, and delegates record work (field changes, research, tasks) to a worker. Changes the worker makes appear in the same feed with Dench as the actor, so the reply summarizes rather than narrates. A comment written by Dench never re-summons Dench.Dench’s own replies can’t be edited; workspace admins can delete them.
Notifications
Each person is notified once per comment (mention wins over reply, reply over
activity), never for their own actions. See Notifications.