How a session works

A session is one conversation with Nomi about one brand, with everything that conversation made kept beside it. This page covers where sessions live, how to find one again, and what you can do to one.

One session, one brand

Your brand sits at the top of the rail, shown as its mark, and the brand showing there scopes the whole app. A session belongs to the brand you started it in and stays there, so Nomi answers out of that brand's DNA, products and markets, and never mixes two. Switching brands from an open session takes you to a new session in the selected brand. Opening a link to an existing session switches the app to that session's brand before showing its conversation. If the switch fails, use Retry.

Finding it again

Recent conversations sit under Recents in the Agent's sidebar, newest first. Search in the rail, or mod + K, looks through sessions, creatives and collections at once. Opening a session shows its newest message, so you pick up where the conversation ended.

You do not have to name anything. Nomi names the session after the first exchange, from what the conversation did rather than from your opening line, and the name appears the next time you move around the app.

A mark on the right of a row says what the session is up to:

• A pulsing dot while Nomi is working on it.
• A blue dot when there is a reply you have not opened. It says whether you have looked, in this browser.
• An amber raised hand when the turn ended on a question for you. It stays up until the next reply lands, opened or not.

Keeping one at the top

Recents is ordered by when a session was started, so a conversation you come back to every day slides down the list as you begin new ones. Pinning takes it out of that order.

Press the ⋯ on a row and choose Pin to top. A Pinned block appears above Recents holding it, and the session leaves Recents while it is pinned. The block belongs to you alone: pinning a session other people can see does not move it in their sidebar.

Once there is a Pinned block you can drag rows around it with the pointer.

• Drag inside the block to change the order. Pinned sessions stay in the order you put them in, not in date order.
• Drag one out of the block to unpin it. It returns to Recents in its own place in the date order.
• Drag a session from Recents into the block to pin it at the position you drop it.
• Drag any session onto a space in the block above to file it there. This is what Move to… in the same ⋯ does.

Unpin the last one and the Pinned block goes away again. Unpin in the ⋯ does the same thing without a drag, and it is the way to do it from a keyboard or on a phone.

What it makes stays in the Library

Everything a session generates also lands in the Library the moment the job exists. Sessions are conversations, not folders, so nothing has to be saved.

Reading a reply

When Nomi did some work to answer, the reply opens with Worked for and how long it took, with a line under it. Press it to read what Nomi did on the way, in order: each search, page and lookup, the pictures it rendered or looked at, and its reasoning. Everything Nomi wrote to you stays under the line, in the order it said it, with anything it made to show you, such as a chart or a set of figures.

A link in a reply appears as a small chip with the site's icon and name, and links side by side share one chip that counts the rest. Sources beside the reply's controls lists every page Nomi read for it; press a row to open the page. Text Nomi marks as a value, such as a handle, a code or a price, is set in a different type so it does not blend into the sentence.

On a phone a session is the conversation alone: there is no Strategise and Generate switch, the pictures Nomi makes appear in the chat, and the copy and vote controls sit under the last reply only.

Hover your own message to see when you sent it and to copy it. Your last message also offers Edit: change the words and press Send, and Nomi answers the corrected message in place of the old one, which leaves the conversation together with its reply. The pictures and products you sent with it go again. Anything the old reply made stays in the Library. You can edit only your last message, and not while Nomi is still replying.

Subagents

When a task splits into parts that do not depend on each other, Nomi can hand each part to a subagent, and they work at the same time while Nomi waits for them. There are three kinds: a researcher looks things up in what the brand knows, on the web and in competitors' ads; a copywriter writes; a critic judges work against the brand. Each keeps one face and one colour.

While they work, the reply shows one line, Running and how many, open so you can see each one: what it was given, how long it has been at it, and what it is doing now. When they are done the line reads Ran and how many, with the time, and it folds under Worked for with the rest of the work. Press a subagent to see the searches, pages and lookups it used, and Open its session under them to read its whole answer, which is a record you read and do not write in; the pages it read are listed under Sources too. Nomi's answer is written from what they found.

A subagent cannot ask you anything, start another subagent, make a creative or launch an ad, and each one stops after 90 seconds. Their work costs credits like the rest of the reply, and Stop stops them too. Reading a brand or a product runs the same way, as one subagent. A subagent's own session is not listed in your sessions and cannot be shared or moved by itself: it follows the session that started it.

Reading something Nomi wrote

When Nomi writes a brief, a script or a research report, the conversation gets a card saying what it wrote and how long it is. Preview opens it in a panel beside the conversation, so you can read it without losing the thread you were on. The panel reads only; nothing you do in it changes the document.

Press the ⋯ in the panel to Open in editor, and the document takes the screen with its own toolbar. That is the only place it can be edited, and it is where your typing is saved. The back arrow returns you to the panel, and closing the panel returns you to the conversation. On a phone there is no room for a panel beside the conversation, so a document opens straight in the editor.

Nomi picks the work back up when a batch lands

When a job is more than one step, Nomi writes out the steps first, then proposes the first batch of renders. You confirm them once, for the whole batch. When every render in that batch has finished, Nomi comes back on its own: a line appears in the conversation saying what landed, it looks at the batch and says one line about it, and it proposes the next step. It does not grade the ads or fix one on its own: a correction starts when you ask for it. You confirm again. Nothing is generated and nothing is charged until you do.

It only does this while there are steps left in what it said it would do. A single ad off a single message is finished when it is made, so nothing carries on after it. It also stops after three of these in a row, so a job that never ends cannot keep going without you.

Ads it made are shown to it once, on the turn they land, and after that it knows them by name and shape rather than by looking at them. That is why it is worth saying what is wrong with one while it is still on screen: that one is too busy, redo it is understood there, and a week later it is not.

If a render fails, the line says which one and why, and Nomi says what it is doing about it.

Adding pictures

Send waits while your selected pictures are being prepared. A message can carry up to four pictures, including references already attached. If a picture cannot be prepared, Nomi tells you so you can add it again; it does not send your draft automatically.

Stopping a message

Press Stop while attachments or a new conversation are still being prepared to prevent the message from being sent. Leaving the conversation during that preparation also prevents a late send. If preparation fails, you can try again.

Once a message has been sent, Stop asks the server to cancel that reply. A delayed Stop request from an earlier reply does not prevent stopping the next one. The conversation stays connected while it stops, and keeps any partial answer with a Stopped notice. Work already started by a tool, including a render, may still finish. If Nomi cannot receive Stop, it tells you and keeps the reply connected so you can try again. Closing the tab alone does not cancel work.

When a reply loses its connection

Once Nomi has started an identified reply, a connection interruption keeps the text already received on screen, including replies started in your current tab. Reconnecting to your reply… means Nomi is retrieving the existing answer. It does not send your message again or start another generation. If the saved answer reports a failure, that failure and its recovery action replace the reconnecting status.

Retrying a reply

When a reply fails or is stopped, Retry under it starts a new attempt using the original message, pictures, product/reference context and annotation instructions. Changing the current composer selection does not change that retry. This also works after reopening the session when the original inputs are still available.

If Nomi cannot restore an older message or one of its pictures, it asks you to attach the pictures and send a new message. A retry uses normal usage limits and the conversation's current history, so the answer can differ.

If a message is sent twice

If the same message request arrives again, Nomi keeps the existing message and does not run another turn. Reload the conversation to see its saved reply. A new message you type is a separate request.

If an ad needs another pass, say what to change; the render Nomi proposes waits for the permission mode and confirmation shown on its card. Nomi asks you with a question card only when you have to choose between options, such as a market or a product, never whether it may render or fix something.

Acting on a session

Hover a row in Recents and press the ⋯. Inside a session, the same menu sits beside the name at the top.

Rename

Rename turns the row into a field. Type over it and press Enter. Up to 120 characters.

Branch

Branch makes a second session that already knows everything the first one knows. Nomi copies the conversation across, so the branch has exactly the same context, and opens with one line saying where it came from. The carried half sits behind a carried over line you can expand.

From the ⋯ you branch the whole conversation. From an individual reply, you branch up to and including that reply, which is how you take one answer in a new direction and leave the rest. Either way you land in the new session, and its row wears a small branch mark.

The controls for the newest reply stay under it: Copy, Branch from here, a thumb up and a thumb down, and Sources when Nomi read pages on the web to answer. An older reply shows the same row, with the time it landed, when your pointer is on that turn. A thumb you have pressed stays on screen after the pointer leaves, so you can see what you voted.

A branch of a session that is in a space stays in that space, so the people working on the campaign see it too.

Share

Share session opens a picker of the people on your brand's team. Tick the row for everyone on the team and the whole team can open it; tick people by name and Nomi makes a space, moves the session into it and puts them in the room, so the next session you start there is theirs too. Either way they see the whole conversation and everything it has made. Only the person who started a session, and a brand admin, get the option at all, and it is not offered on a session that is already in a space.

Delete

Parallel sessions and waiting decisions

Different sessions can run at the same time. Each session runs one agent turn at a time, so a message saying Nomi is still finishing applies only to that conversation.

Only one question or proposal panel is active above the composer. An open question takes priority. Other proposals stay queued and appear after the current decision is resolved; a batch still uses its own version arrows and confirms only the batch shown.

If your browser loses a stream while the server is still replying, Nomi reconnects to that answer instead of starting a second turn. The saved reply replaces the partial one when it lands.

Notes from another session

Nomi can pass something from one session to another in the same brand when the work needs it: a decision made there, a correction or a task. It only reaches sessions you can open yourself. The note lands in the other session as a line reading Note from and the name of the session it came from, with the words under it, and Nomi reads it the next time it works there. Press the name to go to where it came from. If you cannot open that session yourself, the line reads Note from another session, without its name.

If Nomi is working in that session on a reply you started, the note joins the reply it is writing; a reply someone else started gets it as a note, read next time. Nomi can also start a reply there when that session is idle, which costs credits like any reply. A reply someone else's message started, or one a teammate adds a message to while it runs, can only do what each of them may: video, campaigns and your company's apps stay off unless every one of them has them, and a fresh read of the brand needs every one of them to be a brand admin. It starts at most one such reply per message you send, a reply started that way can pass work on only once more, and a session stops being woken after three of these since you last wrote in it. In the session that sent it, the step reads Sent a note to and the session's name.

When Nomi is temporarily unavailable

If Nomi cannot finish a reply, your message and any partial work stay in the conversation. The failure remains visible after a reload, and you can retry the latest reply later. A temporary service outage does not mean you need to buy more Nomi credits.

Archive and restore a session

Use Archive in a session’s three-dot menu to remove it from the active sidebar without deleting its messages or creatives. Open the filter icon beside Recents and choose Archived to find it again. Archived rows are labeled; Restore returns the session to Active. Archiving a session does not archive its creatives or stop a reply already running. In a shared session, this organization change is shared with its participants.

With the menu open, press A to archive or restore, or D to open the permanent-delete confirmation. The menu shows both keys. These shortcuts do not run while you type in a field.

If a document preview cannot load, use Retry. When you leave the editor with Back, Nomi waits for pending edits to save before opening the preview; if saving fails, your draft stays open.

If a research card cannot read its latest progress, Nomi retries briefly, then shows Research progress unavailable with Try again. The research may still be running. Try again checks the same run; it does not start or charge for a new research request.