Your own scrolling always wins (the reader owns the view)
Once you move a session's transcript yourself — with a finger, the mouse wheel, the keyboard, the scrollbar or any scroll control — nothing automatic moves it again while you stay on that session, except keeping you at the very bottom while you sit there. Opening the session fresh, sending a message, or tapping jump-to-latest hands the view back. Phone and desktop alike.
On this page
What it is
A session's transcript changes while you read it: replies stream in, images finish loading, older turns render, the keyboard opens, the header grows. Omniscio places the transcript for you when you open a session (at the live bottom for a running session, at the start of the reply you came to read, and so on). The moment you move the transcript yourself, that placement is over: nothing automatic moves it again during that visit, with one exception — if you are sitting at the very bottom, new output keeps you at the bottom so you can watch it arrive.
It applies on the phone and on desktop.
Where to find it
This is every session's transcript — the main panel of an open session, on desktop and on a phone. There is no separate screen and nothing to turn on.
The one control it involves is the down arrow at the bottom of the transcript: once you have scrolled away from the latest output it appears there, and tapping it takes you back to the bottom and puts you back in automatic following. When the app itself is drawing a card under the conversation — a land/status card, a scheduled message, your queued messages — that card sits below "the bottom", so the arrow lifts you to the conversation's end first and, tapped again from there, down onto the card.
There is no setting for any of this. It is simply how scrolling a transcript works.
How it behaves
What counts as "you moved it"
- Scrolling with a finger, the mouse wheel or a trackpad.
- Scroll keys (Page Up / Page Down, Home / End, the arrow keys, Space) outside a text box.
- Pressing and dragging the transcript's scrollbar.
- Any scroll control: the up and down arrows, the "N more replies" pill, the press-and-hold on the down arrow, the step keys (Shift+Up / Shift+Down), Ctrl+Home / Ctrl+End, and jumping to a search result.
Scrolling that you did not do — content collapsing, the browser keeping your place while something above you renders — never takes the view on your behalf.
Something that loads late above the reply you opened on — the Landed card, an image, a turn filling in — is put back: until you touch the wheel, the scrollbar, a scroll key or the screen, the app keeps that reply where it landed, even when the shift happens to look exactly like a scroll up (2026-11-19: a finished session was left half-scrolled when its Landed card arrived a moment late).
Where you end up
- You moved away from the bottom — the transcript stays exactly where you put it. A late image, a new reply, the keyboard opening, the header changing, a turn finishing: none of them move it. The down arrow shows, so jumping to the latest is always one tap away.
- You moved to the bottom (within about 32 pixels of it, in either direction — the same line at which the down arrow appears) — new output keeps you pinned to the bottom, the way a chat should.
- What "the bottom" means — the end of the conversation's last message, not the end of the scrollable page. Anything the app draws under a session's conversation (its land/status card, the scheduled-message card, the queued-message list) is below the bottom, so a session opening on a tall card still shows you the reply you came for; you scroll (or tap the down arrow twice) to reach the card. On a running session that is also where automatic following keeps you, so the agent's newest output is never pushed up by a card.
- Down on a card you are reading, not following — once you scroll past the conversation's end onto a card below it, nothing automatic pulls you back up; scroll back to the conversation's end and following resumes.
What hands the view back to the app
- Opening the session fresh, or coming back to it after switching away — it lands the usual way for its state.
- Sending a message yourself — you are taken to the bottom to see it, and follow the reply.
- Jump to latest (the down arrow, or its hold on the pill) — you follow new output again. Tapped a second time from the conversation's end, with a card below, it takes you onto the card instead.
- Scrolling back down to the bottom yourself.
A scheduled message you set up with Send Later still scrolls into view when its card appears; one the Inbox Pilot, another agent or a scheduled job queued only does so if you have not scrolled away from the bottom yourself.
Why it works this way
Earlier, each automatic correction guessed on its own whether you were still scrolling, from how long ago your finger last moved (a few seconds). Someone who scrolled and then read looked idle, and a tap on a scroll control was never seen at all, so a correction could take the page back — the reported "when I scroll up on mobile it still jumps me back down". Now one fact decides it for every correction: who moved the view last.
Related
- Real Conversation Layout — what the transcript shows and hides.
- More replies below — the unread-count pill that jumps the view to the latest.
- Send a message — sending is one of the actions that hands the view back to auto-scroll.
Last verified 2026-11-19