All Documentation

Documentation Settings: This Mac

Appearance: display, continued

How a new discussion is named, what a message sent mid-run does, being told about a similar recent discussion, and when a ticket's due date changes colour.

The rest of the Display group on Settings → This Mac → Appearance. Every switch here is shared with your account, so the web (Settings → Appearance → Display) and the iPhone (Settings) show the same value and change it for every app.

Short titles

Default: on.

A new discussion is named at once from the first few words of your first message, and a moment later a small model writes a short title for it. A name you give a discussion yourself always stands. A temporary discussion keeps the first words; a discussion you opened but never asked anything in leaves the sidebar. Off, a discussion is named by its first words only.

Suggest a second check for files made by one seat

Default: on.

When one seat makes a PDF, deck, document, HTML report or image and no other seat reviews it, a line under the answer offers to ask another switched-on seat to check it page by page at full size, sent as an ordinary @mention message. Off, the line is not shown.

Messages during a run join at the next step

Default: on.

A message sent while the room answers reaches the working seat once its current tool returns, marked Waiting — joins at the working seat's next step; the seat folds it in and keeps what it has done. Claude Code reads it without stopping; Codex, Gemini CLI and Grok Build pause after the tool and carry on in the same session. An ACP agent reads it when its turn ends. Send now cuts the current reply short. Off, it waits for the current answer to finish.

Point out a similar recent discussion

Default: on.

Before a new discussion's first run, the discussions you and your team started in the last 30 days are compared with your question by plain word overlap, with no model call. When one is close, a line names it, who asked it and when, with a link, and the room goes on; nothing is held up. Nothing is looked up while you are signed out.

When to use it. A team that asks the same question twice in a week finds the first answer before paying for a second.

Mask personal data before a prompt leaves

Default: off.

On, an email address, a phone number, a card number or a national ID in what a seat on a key is sent — your message, an attachment, a tool's result — is swapped for a placeholder such as [email-1] before it reaches the provider, and swapped back in the answer as it streams. The transcript you read holds the real values; only the wire carries placeholders, and the same value gets the same placeholder for the whole run, so a seat reasoning about [phone-2] is reasoning about one person. A seat that asks a tool about a placeholder gets the real value in the tool.

Names and addresses are not attempted, on purpose: a pattern that guesses at names masks half of every sentence, and a masked word the model needed produces a confident wrong answer. Four shapes with real structure, matched carefully, beat a guess.

What it does not cover. A seat that works inside its own command-line tool (Claude Code, Codex, Gemini CLI) reads your files itself, so nothing on this path stands between it and the provider. A team's own switch (Team → Governance) applies on top of yours: either on is on.

The same switch is on the web and the iPhone, where every seat runs on the server and the masking is the server's (see Pages, reports and privacy on the web).

Mark tickets due within

Default: 2 days. Choices: Never, 1 day, 2 days, 3 days, 7 days, 14 days.

A ticket due within that many days reads amber on its strip, its board card and its row in the issue list; one past its date reads red. A done ticket is never overdue. Never marks nothing. The due date itself is set on the ticket; see Tickets, boards and projects.

See Also

Not what you were looking for? The help centre answers one question at a time, and the support page says how to reach a person.