The box reads "Ask Laureo, or describe what you want done", or names the record you are looking at when the panel is open on one. Send is the square button to its right. While a run is going, that same square becomes Stop.

Keyboard

• By default, Enter sends and Shift+Enter starts a new line.
• If you set Send messages with to Cmd+Enter in chat settings, plain Enter starts a new line instead and only Cmd or Ctrl with Enter sends.
• Escape stops a run that is generating. If a menu is open in the box, it closes that menu first.
• Typing in a language that uses a composition step, such as Japanese or Chinese, never sends on the key that accepts a candidate.

Attaching things

Add context is the plus control inside the box, at its bottom right. It offers three things: Upload file, CRM file for something already stored in Laureo, and Record for a contact, company, deal, quote, product, project, campaign, or ticket. Search there only ever shows records you can currently access.

What you attach appears as chips above the box, each with its own remove control. Laureo takes a snapshot of them when your message is accepted, so removing a chip later changes future messages without changing the file or record it came from.

Mentioning a record with @

Type @ at the start of a message or after a space, then at least two characters, and a short list of matching records appears. An email address you type never triggers it. Arrow keys move through the list, Enter or Tab inserts, and Escape dismisses it. Enter never sends while that list is open. See Mentioning a Record below for which types also attach themselves.

Slash commands

Type / at the start of the box to open the command list. Arrow keys move, Tab completes, and Escape clears the slash. Full list in Slash Commands.

Length

Messages are capped at 5,000 characters. Past 4,000 a quiet counter appears inside the box reading, for example, 4,320 of 5,000. It turns amber as you approach the cap and red past it, and the line under the box says why Send is unavailable: "Message too long: trim to 5,000 characters."

Sending while something else is happening

The box is never locked while Laureo is working, and never locked by a proposal waiting on you. You can always type.

• A run is going: Send queues your message behind it, and a strip above the box reads "{n} waiting to send" with Edit, Up, Down and Remove on each row. If instead you want the new message to replace the work in flight, use Stop current task and send, which appears under the box while a run is active.
• A proposal is waiting: a muted line reads "Waiting for your approval above." You can still type. Sending asks first, with "A proposal is waiting for your approval", offering Send this instead (which cancels the action waiting for approval and sends), Queue it behind the proposal, or Keep waiting, which sends nothing and puts your message back in the box. Queue it and the message waits its turn behind the proposal: it stays in the thread marked Queued, a line under it reads "This is waiting for your decision above.", and beside that line is Cancel that request and run this instead if you would rather not wait.

Send completes only once Laureo has durably accepted the command. After that, closing the panel or the browser does not cancel it.

Example questions:

• "Show me my at-risk deals"
• "What tasks are overdue?"
• "Find companies in the healthcare industry"
• "Summarize my pipeline health"
• "Move the Acme Corp deal to Negotiation"
• "Help me prioritize my deals this week"
• "Draft an email to Sarah about the renewal"

The Add context menu has three choices: upload a new file, select a file already stored in Laureo, or select a record such as a contact, deal, quote, campaign, product, or booking. Record references stay structured and are not copied into fake files.

• Text formats: plain text, Markdown, CSV, and JSON.
• Office formats: XLSX, DOCX, and PPTX. Macros, embedded objects, password protection, external relationships, and unsafe archives are refused.
• PDF: support is narrow on purpose. A PDF is read when its text is selectable, it uses the standard Helvetica, Times, or Courier fonts, and it was saved in one piece without a password. Everyday files fall outside that: one that was edited or signed electronically and saved as an update on top of the original, one from a newer editor that writes a compact cross-reference layout, and one whose fonts were embedded as partial copies, which is what exporting or printing to PDF usually produces. Image-only scans and files with active content are refused too. Each refusal shows a file error naming what is supported, and no text is ever guessed. Attaching the original as DOCX, XLSX, or text is the reliable path.
• Images: on the Business plan and above, paste, drop, or attach a PNG, JPEG, WebP, or GIF and Laureo reads what is in it and answers from it. A screenshot of an error, a signed page, or a spreadsheet a colleague sent you all work. Any other image format is refused, and so is every image on a plan that does not carry the capability, or in an organization where it has not been switched on. The refusal happens before the file is stored, and it names which of those two reasons applies, so a file is never accepted and then quietly ignored.

Each message can include up to 10 references. File size and storage limits follow your plan. Extracted context is capped per reference and across the message, so a very long document may be shortened to the portion that fits safely.

The AI assistant is designed to be a business advisor grounded in your CRM data. It will help with sales strategy, pipeline planning, email composition, and workflow optimization.

If you ask about topics outside its scope (code, medical advice, general trivia), it will redirect you back to CRM-related help. For competitor questions, it will only assist with migrating data from another CRM into Laureo.

While Laureo is working there is exactly one block describing that run, and it sits in the conversation itself rather than in a footer bar or a floating pill. Its top line holds three things:

• What is happening right now, as a short verb and object such as "Searching deals" or "Saving quote". The line is replaced as the run moves on, so a long run does not bury the conversation in narration. Before there is anything to name, it reads Working on it; while Laureo is still reattaching to a run that is already going, it reads Connecting to the running task.
• How long it has been going, in whole seconds.
• Stop. Pressing it changes the label to Stopping immediately, before the server has answered, so the button never lies about what you just did.

On a narrow screen the line wraps: the activity and the timer on one line, Stop on the next.

The steps underneath

Each step Laureo takes is listed under that line. Up to three of the most recent are shown outright, two on a small phone. From four onward the rest are behind Show all {n} steps. The list never opens itself and never scrolls itself while you are reading. The same thing done several times in a row collapses into one row, such as "Searching deals, 3 times", rather than three identical lines. Each finished step carries one of four marks: a tick when it is done, an arrow when it was handed to its page, a clock when it needs you, and a cross when it failed.

A written plan appears only when a run declares five or more steps in advance, and even then it arrives collapsed as Plan: {n} steps. Below that, the step list is the record. Most runs show no plan at all, which is deliberate.

The thinking line

When Laureo is working out what to do and has produced neither text nor a step yet, the same line reads Thinking for {n}s and counts up. That is all it ever shows. Private reasoning is never displayed, summarized, stored, or exported, not even as a length or a first line.

When the answer starts

The moment the answer starts arriving, the working block's top line disappears and the answer takes its place. You never see both at once. In its place, under the finished answer, a quiet Steps control keeps the full step list available for as long as the conversation exists. It is a name rather than a tally, because the count of the run belongs to the closing summary and one run is never counted twice on one screen. Traces do not vanish when a run ends.

Beside the activity line, a short word names the kind of work the run was routed to, such as a short answer or an agentic run. It is read from the run's own saved record rather than guessed, so if that record has not been read back yet nothing is shown instead of a guess. It never names a provider or a model.

A proposal is a card in the conversation, never a pop-up over it, so the rest of the app stays usable while you read it. Every change gets its own card. It is laid out top to bottom:

• The action, as a verb and its object: Create contact, Update deal, Create quote.
• Why it is asking, in one short sentence, when Laureo has a reason worth stating. If it has none, the line is simply absent rather than filled with something invented.
• The record as it will be saved: every value the change will write, and every required field of the page's own form for that record, with linked records by name. Each row says what it is in words beside the value: Not set with Required for an empty required field, default for a value the page fills in, and was with the old value under an update's new one. The card first reads Preparing details while the rows arrive.
• Approve, Edit, Request changes, and Deny.

Approve stays off until you have everything in front of you: while the details are still preparing, while a required field is not set, and while a long value is cut short. In that last case, Show all opens every value as plain text, and Approve comes on once you have opened it. The reason Approve is off is written under it.

The lines above the buttons

Up to three short muted lines can appear between the fields and the buttons. Each is absent unless it is true, so a card is never padded out with reassurance:

• Where the content came from, when the run read something from outside the CRM before proposing this write, such as "This proposal used content from an email." or "This proposal used content from an attachment." Content that arrived from outside always earns you a look, even in automatic mode.
• Whether it can be taken back: "You can undo this afterwards.", "You can correct this afterwards, but not undo it.", or "This cannot be undone." An action that changes no record says nothing here.
• How to put it back, when there is a specific route to reversing it.

Approve, Edit, Request changes, Deny

• Approve records your decision and runs the change. An update is saved against the version of the record the card showed: if someone changed the record in the meantime, nothing is written and the page's own conflict message says so.
• Edit turns the rows into a form, so you change the values yourself. A field of the page's own form becomes an input; a linked record, a list or a message body stays as it is, with Ask in chat to change and the field name beside it. Save and approve checks only what you changed, the same way the page checks it, and approves the change with your values: "Approved with your changes." If someone changed the record after the card was made, nothing is approved yet. Your values go on a new card for you to check and approve: "Your changes are on a new card. Approve it there." A required field must be filled in first. If the card changed under you, it says "This card changed. Review the new one." Edit comes on once you can see every value, so use Show all first when a value is cut short.
• Request changes opens one line, "What should change?". Say what to change and select Send changes: this card is declined, your words become your next message, and Laureo makes the changes and shows a new card. Once the new card is there, this one shrinks to a line saying it was replaced.
• Deny opens one line for an optional reason. Leave it blank and the change is declined. Type a reason and it becomes your next message, so Laureo can try again the right way.

What the card becomes afterwards

• Done: the card collapses to one receipt line with a tick, such as "Contact created." and an Open link straight to the record. Following it keeps the conversation with you. A receipt only ever reports what was actually saved.
• Hidden by your view: if one of your own saved views would hide the new record, a line under the receipt says "Your view and the view's name hides it.", with Show in list, which opens the list with that record shown. Your view is not changed, and the record is never created a second time.
• Next steps: after a create or an update, a row under the answer offers Open and up to two next steps for that record. Pressing a step sends it as your next message.
• Still finishing: "Saved. Finishing this in the background." The card does not linger with dead buttons.
• Denied: the card is replaced by a single line, "You denied this. Nothing was changed."
• Expired: the action, one line reading "This proposal expired.", and one Ask again control. Ask again re-sends your original request. It never silently re-approves anything.

Batches keep a checkbox per item and read Approve selected, Approve all, or Deny all. Some batches are all or nothing and say so. Risk is stated once, in words, in the why line, rather than as a badge beside every row.

An approval is bound to the run and conversation it came from, and cannot authorize a different action later. Before the effect actually runs, Laureo rechecks your current membership, role, plan, scope, the record version, and the recipients. A double press, a second tab, or a retry cannot make the same change twice.

Automatic mode lets a change run without a card, except for the ones that show a card every time, in every mode: anything that moves money, changes people's access, exports data or creates an export link, emails someone outside your organization, changes many records at once or deletes, and automations. Which individual actions may run without asking in Ask first is a separate organization setting on the Business plan and above; see Approval settings.

A proposal appears in exactly two places: once as a card in the conversation it belongs to, and once as a row in the assistant chip. There is no footer bar and no floating pill duplicating it.

On a wide screen the chip sits in the top right of the app bar, beside the notification bell. It reads Needs approval with a count when something is genuinely blocked on you, and the quieter Working with a count when runs are simply in progress. With nothing pending and nothing running it does not render at all.

On a narrow screen, where there is no app bar, the same chip floats in the top right corner instead, and its list opens as a bottom sheet. It hides itself while you are on an assistant surface, because the conversation in front of you already shows the card.

Opening it lists each run with what it is waiting for and the conversation it belongs to. From a wide screen you can Approve or Deny straight from the row without opening the conversation, or press Open to go to it. If a decision cannot be sent, the panel says "Could not send that decision. Open the task to try again." rather than pretending it landed.

In the conversation list, a conversation whose run needs approval carries a small dot before its title.

When Laureo needs something only you can tell it, it asks with a question card rather than a question in its text. A card holds one to three questions, each with up to four options, and Laureo's turn ends there: your answer is your next message. It asks at most once per request.

• It never asks for what it can work out. A value it can write itself, look up or take from a default is never asked. An email subject, for example, is written for you, not asked for.
• You can always type your own answer. Under every question there is a box, Or type your own answer, with a note not to type passwords or keys there. What you type is cleaned of anything that looks like a secret before it is sent.
• You decide under each question hands that one back to Laureo. Until you pick or type something, the button at the bottom reads Let the assistant decide; once you do, it reads Send answer.
• After you send, the card stays as a record of what you picked, with "Answer sent.", and cannot be sent twice.

If Laureo read an email, an attachment or other outside content in the same request, the card says so in one line, and its options come from Laureo's own fixed choices rather than from that content.

Ask take me to the vendor list or where do I set up booking pages and Laureo answers with an Open button for that page, from the real list of pages you can open, filtered exactly the way your sidebar and command palette are filtered. Laureo never moves the screen on its own: press the button and the page opens, with the conversation still beside you. Opening a page creates nothing and sends nothing, so it raises no approval card; Back is the whole undo.

The same button answers a request Laureo cannot carry out from the chat. One line says where it is done, such as "This is done on the Tasks page.", with Open Tasks under it, and Laureo does not try again another way. When your role, your seat or your plan does not include the action, the line says only that, with no button.

Ask how does the scheduler work and Laureo searches this help centre, reads the article that answers you, and replies in the product's own words with a link to the article it used. Follow the link when the answer looks thin; the article is always longer than the summary.

Laureo can list your cold outreach sequences, read one in detail, and read the replies they brought in. Drafting a sequence, choosing its lead lists and launching it are done on the Cold Outreach pages: ask for one of those and Laureo gives you a button that opens the right page. Launching is the only step that sends anything.

Laureo can only see the sequences you could see yourself. If your role gives you access to your own outreach rather than the whole team's, a teammate's sequence is simply not found: the same answer you get in the Cold Outreach pages.

Alongside contacts, companies, deals and email, Laureo can answer questions about the parts of the business that used to need a trip to another page:

• Duplicates: "do we already have Acme" before you create a second record. It reports what matched and why: the company name, a contact email already on file, or the account number.
• Collections: the overdue worklist, the reminder plans invoices are on and the promises to pay, the aging report, and payment disputes.
• Renewals: recurring schedules and the renewals coming up in a window you name.
• Enrichment: whether it is set up at all and what a lookup would cost, so it can tell you before offering rather than after failing.
• Imports: how many contacts are staged and waiting to be imported, with a few of their names.

Every one of these is read-only, and every one is limited to exactly what you could see yourself. The Recycle Bin, import history, purchase and sales orders, and lead capture are read on their own pages: ask about them and Laureo gives you a button that opens the page.

Laureo can also see the automations you have running, the booking links people book you through, and your team chat. As questions, these are read-only:

• Automations: "which automations are on", "when did the lead-routing rule last run". It lists them with their status and their runs, and can tell you whether the rules are firing as they should. Cold outreach sequences are a separate thing and are not included here.
• Booking links: which links are live, how long each meeting is and who hosts it, and the bookings made through them.
• Team chat: your conversations and the teammates you can message.

Running an automation, pausing a booking page, marking meeting attendance, posting to team chat and clearing notifications are done on their own pages. Ask for one and Laureo gives you a button that opens the page.

Some kinds of change are never made without a card, including in automatic mode, which cannot skip them and no organization setting lifts:

• Money: anything that charges, pays out, refunds or moves funds.
• People and access: inviting, removing or changing what a teammate may do.
• Exports: a file of your records, or a link to one.
• Email to outside people: anything that reaches someone outside your organization, a calendar invitation included.
• Bulk changes and deletes: changing many records at once, or removing one.
• Automations: anything that starts or changes an automation.

Most of these are done on their own page today, so Laureo answers them with a button to that page. A few things are always yours alone, and Laureo hands them to you with that same button: connecting an outside account, entering a card, giving consent, completing a two-step sign-in, deleting your account, and entering a secret such as a key or a password.

Laureo can find your tasks, update one and mark one complete, each shown on a card first while you are in Ask first.

• Update task details: "Move the Acme task to next Tuesday" or "Reassign the onboarding task to Sam" edits the task in place. Reassignment respects the same permissions as editing the task by hand.
• Complete a task: "Mark the Acme follow-up done" completes it.
• Add a calendar event: Laureo can create an event on your connected calendar. It always shows a card first, because an invitation can reach other people.

Creating a new task, and reading what is on your calendar, are done on the Tasks and Calendar pages: ask for either and Laureo gives you a button that opens the page.

After a completed text turn, feedback and regenerate controls appear in a full-width utility row below approval and artifact actions. They stay hidden while a decision is pending so they never compete with the primary action.

Once you rate a message, the selected icon highlights (green for positive, red for negative) and cannot be changed.

When an answer read your records, a row under it names them: up to five names, then +N more. The row is built on the server from what the run actually read, as you, so it is a record of the answer rather than a claim about it. An answer that read nothing shows no row at all instead of an empty one.

Selecting a name opens that record in place, as a preview for a contact, a company, a deal or a project and as its page for the rest, and keeps this conversation with you in the desktop dock or mobile sheet, so checking a record never costs you the thread. A record you may not open is listed as plain text rather than as a link that would go nowhere.

The answer arrives as an ordinary message that grows as Laureo commits it. There is no blinking cursor and no shimmer. If your connection drops, reopen the conversation and the saved events replay from the last one you saw. The browser stream is a view of the work, never the work itself.

Stop is saved on the server and stops the run. Nothing new starts after it, and no further text is added to the answer. A change that was already being saved when you pressed Stop finishes once and records its receipt, so you always know what landed. Text and changes already committed stay in the conversation, honestly recorded, rather than being described as cancelled, and a stopped run never pretends it finished.

System notes

Facts about the run itself arrive as one short centred line, not as a message from Laureo. They carry no timestamp, no copy control and no feedback buttons, because there is nothing to rate. The wording is fixed:

• You pressed Stop: "You stopped this run."
• Cancelled before anything ran: "This run was cancelled. Nothing was changed."
• Cancelled after steps ran: "This run was cancelled. The steps above already ran."
• Failed before anything ran: "This run failed. Nothing was changed."
• Failed partway: "This run failed partway. The steps above already ran, and nothing after them did."
• You denied a proposal: "You denied this. Nothing was changed."
• A proposal ran out of time: "This proposal expired."
• A big job was accepted: "This is a large run. It will pause for approval before changing anything."
• A line was saved to or removed from your memory: "Saved to your memory." or "Removed from your memory.", quoting the line, with Undo beside it and a Manage link to the whole list.

Time separators

Messages no longer each wear a timestamp. Instead, a small centred line marks a real gap: when more than fifteen minutes passed or the day changed, you see Today 4:12 pm, Yesterday 9:40 am, 3 Sep, 4:12 pm, or the year as well for anything older. The exact time of a single message is still there on hover and for screen readers.

Follow-up chips

After a finished answer, up to three one-tap follow-ups appear under it. Pressing one sends exactly the words on it. They stay away while a run is going and while a proposal is waiting on you, so they never compete with a decision. See Voice & Follow-up Chips.

The run summary

A run that did several things closes with a short ledger under the answer: "Did 6 steps: 4 done, 1 skipped, 1 failed", then one line per step. Each step that landed carries its own Open link to what it created or changed; a skipped or failed step says why. The lists are read back from what the run actually recorded, so it is a record rather than a closing sentence Laureo composed. A run with nothing to report shows no summary rather than an empty one.

Every conversation is saved as you go. On the full page the list is a rail beside the chat; in the side panel and the home assistant, the Conversation history control opens the same list over the chat. Rows are grouped, in this order: Pinned, Today, Yesterday, Past 7 days, Past 30 days, Older. Days are counted in your own time zone. A pinned conversation sits under Pinned rather than under its date.

Each row shows the title and how long ago it was used. A conversation whose run is waiting on your approval carries a small dot before its title. A conversation with no title yet reads New chat, the same phrase as the button that creates one.

On a desktop screen you can widen the side panel by dragging its left edge, or by focusing that edge and using the left and right arrow keys. The width is remembered on that device.

Titles

A new conversation is named from your first message immediately, so the row never sits blank. After the first answer, Laureo replaces it with a short generated title. Once that generated title exists, renaming the conversation yourself is the last word and nothing renames it again. A rename made before the first answer arrives can still be replaced by that one generated title.

The row menu

Each row on the full page carries a ⋯ menu, reachable by touch as well as by hover:

• Pin to top and Unpin, which move it into or out of the Pinned group
• Rename, edited in place on the row
• Move to folder, which files it in one of your folders or takes it back out to All chats (see Folders below)
• Archive and Unarchive, which move it between the Conversations and Archived views without deleting anything
• Export, which builds a downloadable record of the conversation. It is prepared in the background: if it is not ready within a few seconds you see "Your export is still being prepared." and it downloads on its own when it is. A failure says "Could not export this conversation." and nothing is changed.
• Delete, which asks first: "Delete this conversation?" and "... and all of its messages will be removed. This cannot be undone." Laureo fences any active work and cancels pending proposals before it goes.

The history list inside the side panel is for choosing a conversation and starting a new one. It shows your folders too, for choosing. Rename, archive, export, delete and moving a conversation to a folder live on the full page.

Folders

Above the date groups, a Folders section lists All chats and each folder you made. All chats is where every conversation starts, and the list opens on it. Choose a folder to list only the conversations in it, and choose All chats to go back. The section header folds the section away; while it is folded, the header still names the folder on screen.

To make a folder, press New folder (the + beside Folders), type a name and press Enter. A name has up to 60 characters, two of your folders cannot share a name, and you can have up to 50 folders. Each folder has its own ⋯ menu to rename or delete it.

To file a conversation, choose Move to folder in its row menu, then pick a folder, All chats, or New folder to name a folder and move the conversation into it in one step. A conversation in a folder shows only in that folder, not under All chats. A pinned conversation stays pinned at the top of its folder.

Deleting a folder asks first: "Delete this folder?" Only the folder goes. The conversations in it are kept and go back to All chats.

Folders are yours alone, like your conversations, and a folder holds conversations, not other folders. The Archived view shows every archived conversation, filed or not, and an archived conversation keeps its folder, so unarchiving it puts it back there. Search looks through all of your conversations, whatever folder they are in.

Search

The box reads Search conversations and searches the whole of your history on the server, not just the rows already loaded. It matches four things, in this order of preference: the title, the text of messages, the labels on receipts, and the names of attachments. A hit shows a short excerpt under the title, and opening it takes you to the message that matched rather than to the top of the conversation. With no matches it says "No conversations match 'your term'."

Linking to a conversation

A conversation lives at /ai/<conversation id>, and that address opens it for you alone. Conversations are private to the person who started them, so sending the address to a colleague only shows them a conversation that is not available. Notifications about a finished run link straight to the answer inside it. Switching conversations on the full page keeps the address in step, so Back and Forward work the way you expect.

Other list controls

• New chat starts a fresh conversation. Its row appears at the top of Today straight away.
• Load older conversations at the bottom of the list fetches the next page.
• An empty list says "Your conversations will appear here.", and a list that could not load says "Could not load your conversations." with a Retry control.

The assistant keeps your recent exchanges word for word. Once a chat runs past that, it starts condensing the oldest part into a summary so the conversation can keep going. Two things tell you where you are:

• A line above the message box, once a chat is long enough for condensing to be near. It says whether earlier messages are still intact or have already been condensed, and offers one "New chat" link. If your next message looks like a change of subject, the same line says so instead.
• A notice in the conversation at the moment condensing happens, with the number of messages it covered. Expand "What the assistant remembers" to read the summary it kept.

Details from the very beginning of a condensed chat may be missing, so if you are moving to an unrelated question, a new chat gives the assistant a clean, focused context to answer from.

• "You are offline. Messages will fail until your connection is back." Your device cannot send a new message until connectivity returns. Work already accepted carries on regardless.
• "Live updates paused. Refresh to see new messages." The live view lost its connection. Nothing is lost: reconnecting replays the saved events in order.

Everything else Laureo can say when something goes wrong is listed in When something goes wrong.

Read-only and text-only turns can be regenerated as preserved alternatives. The earlier answer remains in history so audit context is not destroyed.

After a product, quote, send, or any other CRM or external effect commits, destructive edit-and-resend and regenerate are unavailable. Receipts remain immutable. Continue with a corrective request, or use an offered undo when supported.

Type @ followed by at least two letters to search your records. Pick one with Enter, Tab or a click and its name drops into your message. Arrow keys move through the list; Escape closes it without losing what you typed. Each row shows the record name, a short detail, and what kind of record it is.

Mentioning a company, person, deal or quote also attaches that record as context, exactly as picking it from Add context would, and it counts toward the same limit of 10 references on a message. A ticket mention is text in your message and nothing more, so use Add context if you want the ticket itself attached.

Naming records also narrows the answer. Once you have pointed a question at particular records, Laureo grounds the reply in them. It keeps the tools it would normally use, because a question about a deal still has to read that deal's own related rows to be answered at all.

The list only shows records you already have permission to see, and never shows anything in the recycle bin or an archived quote.

Open the three-dot menu on any conversation in the sidebar and choose Pin to top. Pinned chats gather in their own Pinned group above the date groups, so a thread you pinned months ago does not sink as you start new ones. Choose Unpin from the same menu to return it to its place by date.

Pins are yours alone. They change nothing about the conversation itself and nobody else sees them.

Hover over any message to reveal a copy button. Click it to copy the message text to your clipboard. This works for both your messages and AI responses.

On a narrow screen the assistant fills the screen rather than floating over it, and every control is sized for a fingertip.

• The conversation list on the full page slides in from the left. Close it by tapping outside it, by swiping it away, or with the close control in its header. A gesture is never the only way out.
• Menus open as bottom sheets. The permission mode menu, the approvals list, the work-in-other-chats list and every confirmation come up from the bottom edge, keep your place on the page behind them, close on a tap outside or on the back gesture, and sit clear of the home indicator and any camera cutout.
• The approvals chip lives in the top right corner beside the notification bell, since the bottom of the screen belongs to the navigation bar and the message box. It hides itself while you are inside the assistant, because the card is already in front of you.
• The keyboard does not cover the message box. When the on-screen keyboard opens, the conversation above squeezes up and the box and its Send button stay visible.
• Enter behaves as you set it. The return key on the on-screen keyboard shows Send or a new-line hint to match your Send messages with preference.
• A proposal card stacks on a narrow screen: field names sit above their values, and the buttons stack with Approve first.
• The working block wraps: activity and elapsed time on the first line, Stop on the second, and it shows two recent steps instead of three.