Omniscio

Customize the session menu (reorder + hide items)

Lets each person reorder the entries in a session's overflow menu and hide the ones they never use, so the menu shows what they reach for, in their order. The grouping into labelled, collapsible sections with a filter box ships for everyone; the customising half is behind an in-development flag that is off by default.

On this page

Let each person reorder the items in a session's ⋯ (more actions) menu and hide the ones they never use — so the menu shows what they reach for, in their order. It is a per-person preference that applies to every session, and it is currently behind an in-development flag (off by default, hidden until shipped).

What it is

Every session has a ⋯ button in its header that opens the session menu — Snooze, Pause, Send Later, Copy app link, Copy session reference (the session's pull request address, or its session ID when it has none), Copy PR number (only when the session has a pull request), Link pull request, Pop Out, Move to, Exports, and many more. That list is long, so it is grouped into labeled sections with a filter box above them: type a few letters and only matching rows stay, and a section whose rows all filter out disappears header and all.

Every section starts collapsed — Session, Organize, Share, Setup, View and This session — so the menu opens as a short list of section names. Tap one to open it right where it is; tapping another closes the first, so the menu never grows into a wall of rows. A collapsed section still names what it holds and opens in one click, and the filter box still finds an action inside a closed section, so nothing is hidden from you. The open menu also draws above the session's floating scroll buttons (the "N more replies" pill and the arrows), so they never cover it. This grouping ships for everyone — it is not behind the customization flag.

With the customization feature on, additionally:

  • The menu renders in the order the user chose, with the items they hid removed.
  • The bottom entry reads "Customize menu…" and jumps to the customizer. With the feature off it reads "Customize session bar…" instead. Either way it can never be hidden, so you can never strand yourself.

Where to find it

Settings → Sessions → "Session menu" card:

  • Reorder — drag a row by its grip handle, or use the up/down arrows (the arrows are the keyboard- and phone-friendly path).
  • Show/hide — the switch on each row; off hides that item from the menu. "Customize menu…" has no switch — it is always shown so you can never strand yourself.
  • Reset to default — restores the built-in order and clears the hidden set (nothing is hidden by default any more; compactness comes from the collapsed sections).

The customizer only lists items that can actually appear for you: developer-only rows (CPU Burst) show only in dev builds, desktop-only rows (Pop Out) only on desktop, the mobile Scroll Log only on mobile, and feature-gated rows (Trajectory, Attach to task, Hand off, Inbox Pilot) only when their own feature is on.

How it behaves

  • Per-person, every session — the order and hidden set are your own settings; they are not per-session and not shared.
  • Persists across restarts.
  • Feature-gated — but only the CUSTOMIZING half. The labeled, collapsible sections and the filter box render for everyone. While session-menu-customization is off (the default today) the menu simply ignores any saved order or hidden set, so someone who has never opened the customizer can never have a stored set applied to them.
  • Mobile — the same order/hidden choices apply to the mobile ⋯ menu; you set them from Settings (there is no right-click on a phone).
  • Pinning to the session bar is separate — pinning a command to the header bar (the existing "Session bar" feature) still moves it out of the menu; hiding is a separate switch. The two compose: a pinned command is on the bar, a hidden one is gone from the menu, and both can be true.

Mark as Read / Mark as Unread

One entry in the This session section is not a setting at all — it is how you tell a session "I have seen this, stop flagging it at me" without doing anything to the work.

When a session is waiting on you it carries an attention badge. Reading the session does not clear it — the badge stays until the work is actually dealt with, which is deliberate, because "I looked" and "I handled it" are different things. Mark as Read is the middle ground: it acknowledges the badge so the row stops pulling your eye, and leaves the session exactly as it was. Marking it does not reply, resume, archive or change the session's status, and it does not affect anything the agent is doing.

The menu shows one of the two, never both, depending on where the session stands:

  • Mark as Read — shown while the badge is still unacknowledged; choosing it acknowledges it.
  • Mark as Unread — shown once it has been acknowledged; choosing it puts the badge back, so the session starts flagging at you again.

Either way a confirmation appears with an undo, so a mis-click is one keypress from reverted. The acknowledgement is remembered per session and survives a restart — and it is yours alone, not something a teammate or another machine sees.

This is not "mark the messages read": a session has no unread-message count. The only thing this touches is the attention badge, which is why it lives in the session menu next to the other attention controls rather than anywhere in the transcript.

Last verified 2026-09-28