Omniscio

Shares view (master/detail sidebar + in-app webview viewer for shared links)

Shares is inside the System group in the sidebar — expand System and click Shares. It opens a Cron-Jobs-shaped master/detail layout: a 268 px sidebar on the left lists every shared link you've created, and the right pane shows the currently-selected share with a three-mode in-app webview viewer (edit / view / fullscreen) and inline controls for label / expiration / view-cap / notify / password / send / revoke / delete / republish.

On this page

audience: customer kind: library roadmap: cat-artifact-sharing-omniscio-shares summary: > Shares is a built-in tool listed on the Installed Plugins page (its In side nav switch adds a side nav row) that opens a Cron-Jobs-shaped master/detail layout: a 268 px sidebar on the left lists every shared link you've created, and the right pane shows the currently-selected share with a three-mode in-app webview viewer (edit / view / fullscreen) and inline controls for label / expiration / view-cap / notify / password / send / revoke / delete / republish. title: Shares view (master/detail sidebar + in-app webview viewer for shared links) category: cloud-teams group: sharing related:

  • shares-view-part-2
  • artifact-sharing
  • share-artifacts
  • share-cli
  • share-comments
  • share-workspace-only
  • daily-digest last_verified: '2026-09-23' verified_against:
  • src/renderer/src/features/shares media: [] video: tutorial-shares index_title: > Shares view (sidebar entry for managing shared links + in-app webview viewer) index_summary: > Tools-page entry (its In side nav switch adds a side nav row) listing every share — threads, artifacts, digests — with Kind/Status filter chips, per-row Copy / Edit / Revoke / Delete actions, and a Publish-pasted-content button; replaces the old Settings → Sharing list, leaves only Firebase Configuration + an "Open shares in app" toggle in Settings. The detail pane has a three-mode viewer (edit / view / fullscreen): edit mode shows all editing controls, view mode renders the share in an Electron <webview> with a floating auto-hide toolbar (Edit, Maximize, Open in browser, Copy URL), and fullscreen mode portals the viewer to cover the whole window (Escape to exit). Share URLs clicked anywhere in Omniscio are automatically intercepted and opened in-app instead of launching an external browser; the "Open shares in app" setting (sharesOpenInApp) swaps CLI-published URLs to deep links (omniscio://share/<token>) that open directly in the viewer. SHARE_UPDATE IPC backs the inline edit form


audience: customer kind: library roadmap: cat-artifact-sharing-omniscio-shares summary: > Shares is a built-in tool listed on the Tools page (its In side nav switch adds a side nav row) that opens a Cron-Jobs-shaped master/detail layout: a 268 px sidebar on the left lists every shared link you've created, and the right pane shows the currently-selected share with a three-mode in-app webview viewer (edit / view / fullscreen) and inline controls for label / expiration / view-cap / notify / password / send / revoke / delete / republish. title: Shares view (master/detail sidebar + in-app webview viewer for shared links) category: cloud-teams group: sharing related:

  • shares-view-part-2
  • artifact-sharing
  • share-artifacts
  • share-cli
  • share-comments
  • share-workspace-only
  • daily-digest last_verified: '2026-11-05' verified_against:
  • src/renderer/src/features/shares media: [] video: tutorial-shares index_title: > Shares view (sidebar entry for managing shared links + in-app webview viewer) index_summary: > Tools-page entry (its In side nav switch adds a side nav row) listing every share — threads, artifacts and digests — with Kind filter tabs, search, Live / Archived sections and a Publish-pasted-content button; click a row to copy, edit, revoke or delete it in the detail pane. It replaces the old Settings → Sharing list, leaving only Firebase Configuration + an "Open shares in app" toggle in Settings. The detail pane has a three-mode viewer (edit / view / fullscreen): edit mode shows all editing controls, view mode renders the share in an Electron <webview> with a floating auto-hide toolbar (Edit, Maximize, Open in browser, Copy URL), and fullscreen mode portals the viewer to cover the whole window (Escape to exit). Share URLs clicked anywhere in Omniscio are automatically intercepted and opened in-app instead of launching an external browser; the "Open shares in app" setting (sharesOpenInApp) swaps CLI-published URLs to deep links (omniscio://share/<token>) that open directly in the viewer. SHARE_UPDATE IPC backs the inline edit form

Shares view (master/detail sidebar + in-app webview viewer for shared links)

What it is

Shares is a built-in tool listed in the System section of the Installed Plugins page (its In side nav switch adds a row for it to the side nav). It gives every shared link one home outside Settings: a master/detail layout whose left sidebar lists every shared link you've created and whose right pane shows the selected share with a three-mode in-app viewer and inline editing controls.

Every editing surface is inline in the right pane; the only dialog left is Publish pasted content, which launches new pasted-text shares.

Threads, artifacts, and daily digests all show up in this one place. From here you can: filter, search, copy a link, rename it, change its expiration, set a view cap, enable view-notifications, set/change/remove a password, send via Gmail/SMS/Slack, revoke an active link, delete an inactive one, republish a revoked/expired link at a new URL, or publish brand-new pasted content. See artifact-sharing.md and share-artifacts.md for the publish-side details.

Where to find it

Shares on the Installed Plugins page (side nav bottom → Installed Plugins, System section). Turn on its In side nav switch to keep a row for it in the side nav.

How it behaves

The master pane (Shares sidebar)

  1. Open the view. Click Shares on the Installed Plugins page (or its side nav row, if you added one). The integration mounts the Shares sidebar in the normal sub-sidebar slot and an empty-state card in the right pane.

  2. Header. "Shares (N)" count on the left + a + Publish button on the right. Clicking the button opens the Publish pasted content modal — the same modal that's always handled paste-publishes.

  3. Search. Below the header, a single search input matches by label, URL token, ISO createdAt, ISO expiresAt, and the human-readable expiry string (so 5 days left / Expired are searchable too). Placeholder: Search by label, URL, or date.

  4. Filter by Kind. Segmented tab strip with four buttons: All / Threads / Artifacts / Digests. "Threads" covers conversation / message / selection scopes (artifactKind is null or thread); "Artifacts" covers HTML, MD, SVG, Image, PDF, Text, Code, React, pasted-text, mc-board (Mission Control board/dashboard snapshots); "Digests" covers the daily-digest scope.

  5. Up to three collapsible sections (no status pills). The list always shows everything, split into sections. New comments is pinned first (only while Share comments is on — see share-comments.md): any share with unread comments lands here whatever its state, even a revoked or expired one. Then Live (neither revoked nor expired), then Archived & expired (revoked OR expired), which is collapsed by default so dead links stay out of the way; each header shows a (count) and a chevron, and archived rows render dimmed when expanded. A section with no rows is not shown, and with nothing unread and nothing archived the whole list renders flat. Kind + search filter first, then each surviving row falls into its section. A row stays in the archive for the whole retention window (dataRetentionDays, 30 days by default), so a dead link waits there to be Republished rather than vanishing when it expires. A share that expired on its own is badged Expired; one you took down yourself is badged Revoked.

    Above the list, a Mentioned you section collects your @mentions on other people's shares. It appears only while Share comments is on and there is at least one, as its own collapsible header with a count; clicking a mention opens that share in the in-app viewer and marks the mention read.

  6. Each row is a full-width button (screen readers announce it as a button in the Shares list), laid out like a Cron-jobs row so the label is never squeezed. Line 1 is the label on its own line (truncating with an ellipsis, never to a single letter), with a small amber lock icon when password-gated and a muted bell icon when notifications are muted. Line 2 is one muted metadata line — Kind · scope · expiry (e.g. HTML · Conversation · 5 days left; kind and scope are translated words, never raw values) — followed by an eye-icon N/CAP view counter when a view cap is set. A share with comments carries a muted total comment count, plus the accent "N new" pill when some are unread; both are main-computed, so desktop and phone agree. A single Revoked (red) or Expired (grey) badge is pinned to the right on archived rows; live rows carry no status badge. Kind, scope and Protected are plain text, and the truncated URL is dropped from the row — it is still searchable and shown in full in the detail pane. The selected row gets the standard inbox-row "active" styling.

  7. Click to select. Clicking a row updates selectedShareId in the store; the right pane swaps to the new share. On mobile, the same click also drives a drill-down via useMobileNavStore.getState().navigateTo('session-detail'), the standard detail slot where RoutedPanel renders the Shares detail pane, so it fills the screen.

  8. Middle-click opens in the browser. Middle-clicking a row opens the share's published page in your system default browser (via openExternalUrlForce) — the same non-destructive action as the detail pane's "Open in browser" button, with no confirm dialog. Uses the inbox-row gesture (onMouseDown + e.button === 1 + e.preventDefault(), which also keeps the middle-click autoscroll circle from appearing). Revoke stays available in the detail pane.

  9. Drag and drop to publish. Drop one or more files anywhere onto the sidebar (the whole sidebar lights up with a dashed accent border and a "Drop files to publish" overlay). Release and Omniscio publishes each file as its own share, then refreshes the list. Files must live inside an active session's working folder, ~/Claude, or a folder you have granted Omniscio access to — drop something from your Desktop or Downloads and you'll see a single error toast naming the file and the reason. Mixed batches surface a single warning toast like "Published 3, 1 failed: foo.docx — …" instead of one toast per file. Web / mobile shows a "Drag-and-drop publishing requires the desktop app" failure (the renderer can't resolve OS paths there).

  10. Auto-refresh. An app-wide subscriber (SharesLiveSync, mounted in GlobalModals) hydrates on mount in the desktop app only — the web/mobile bundle reads nothing at boot — and re-pulls on every SHARE_UPDATED push, so the list reflects your shares on every view — even when this panel is closed. The sidebar has no listener of its own and the detail pane reads from the store, so nothing is fetched twice. Because SharesLiveSync knows your own shares, an agent-published share of your own opens in the in-app viewer with its full metadata (label, staleness) rather than the minimal build-from-token card; a share you don't own also opens in-app from its token. The phone refreshes itself too: SHARE_UPDATED is in the phone push filter's INBOX_ALLOWED_CHANNELS, so a share created, revoked, updated or deleted on the desktop re-reads the phone's list, @mentions and unread total. Because the phone never hydrates at boot, a tapped share link resolves on demand: the share-URL resolver pulls the owned list right then, once — hasLoadedOnce is what stops a second tap re-reading it — so the Shares view always has the row it was asked to open. The push carries only { action } and is coalesced on the push bus, so a burst of view-count updates reaches the phone as at most two re-reads per 50 ms burst. Locked by tests/unit/features/shares/shares-live-sync.web-gate.test.tsx.

  11. Empty states. First-time visit (no shares yet): centered card with "No shares yet" + a "Publish pasted content" CTA button. Filtered to nothing: "No shares match this filter" with a hint about adjusting the search / filter chips plus a one-click "Clear search & filters" link that empties the search box and resets the type filter to All.

Keyboard

  • Open Shares from anywhere: Alt+Shift+H (the openShares action, rebindable in Settings > Keybindings). It does nothing while Shares is hidden from the sidebar, and it never fires while you are typing in a text box.
  • Move through the list: with a share row focused, Up and Down move focus to the previous or next share (wrapping at both ends), and Home / End jump to the first or last. Arrows move focus only; press Enter or Space to open the focused share. Arrow keys in the search box keep working as normal text editing.

Touch targets on phones

  • Every small control in the panel has a 44px touch target on touch screens (it looks unchanged on a desktop): the section toggles, "Clear search & filters", the edit form's four checkbox rows (Limit total views, Notify me, Allow comments, Mute notifications), the Comments and Resolved toggles, the "Send to…" toggle, Delete, and Settings > Sharing's Firebase Configuration toggle.

Pointing at controls

  • The assistant can point at every control in the panel by its data-ui-anchor, including the view-limit box (shares-metadata-view-cap-input), the notify / Allow comments / mute checkboxes (shares-metadata-notify-on-view, shares-metadata-allow-comments, shares-metadata-mute-notifications), the reply snippet (share-comment-reply-context), the Gmail / text message / Slack send tiles (shares-detail-send-channel-gmail / -sms / -slack), the header Copy URL button (shares-detail-copy-url) and the send message box (shares-detail-send-message).

The detail pane (Shares detail)

The right pane is empty (with a friendly explainer) until a row is selected. Once selected, the pane is a stacked column inside an max-w-3xl container, vertically scrollable on overflow.

  1. Header band. Title (truncated <h2> of share.label), a status pill (Active green / Revoked red / Expired grey / View cap reached amber), scope chip, artifact-kind chip, Protected amber lock badge if password-gated, and a relative "Created N minutes/hours/days ago" timestamp. On the right: one icon toolbar of same-size icon buttons, each with a hover tooltip, matching the in-share viewer toolbar. In order: View (Eye, desktop only, hidden on a phone, see On a phone) switches the pane into in-app view mode (see mode system below); Open in browser launches the URL in the system browser via openExternalUrlForce (bypasses share URL interception); Copy URL (CopyConfirmButton, icon variant, with the check-mark confirmation). A thin divider follows, then two desktop-only actions that put the share's content to work:
    • Export to Context Dock (library icon, shown only while Context Dock (Local) is switched on) reads the share's text and saves it as a new Context Dock (Local) document titled with the share's label, the share's address on its first line. A toast confirms it with an Open action that jumps to Context Dock (Local).
    • Start a session (message-plus icon) reads the share's text and opens the shared Start session window: the Message box starts with a short prompt naming the share, and the page's text rides in a collapsed, editable Shared page text box (no Base branch picker). Pick the repo, edit either box, and start. The session receives your message, then a short "About this item" note Omniscio adds from the stored share (its title, kind, public link, dates, whether the link is live or revoked, and the routes to read its status and comments or revoke it), then the page text.
    • Both read the PUBLISHED page (what the link actually serves), so they work for every report and page, not only shares whose source file is still on this computer. The read always declares itself a machine read, so it never counts as a view. Both are disabled, with the reason in the tooltip, for a revoked or expired share, a password share, a view-limited share, and an image, PDF or app share (nothing to read as text). A long page is trimmed at 200,000 characters with a "truncated" note. Neither has a keyboard shortcut: they are occasional actions and the Shares pane has no key layer of its own. From the CLI, POST /share/export-to-context-dock with { "shareId": "<id>" } does the export headlessly.
  2. Three-mode viewer. The detail pane has three modes, tracked via a viewMode state ('edit' | 'view' | 'fullscreen'):
    • Edit mode (default). Shows the header band pinned at the top, the inline edit form, password sub-form, Send panel, comments, and destructive footer — all the editing controls, in their own scrolling region below the 16:9 preview — the one viewer host, which no mode change tears down and rebuilds.

    • View mode. Replaces the edit form with a full-height ShareViewerWebview — an Electron <webview> rendering the share in its own process. It handles loading, error and crash: an opaque spinner covers the page until it draws its first content and then fades in, so a font-heavy share never flashes white first; a failed load shows an error overlay with an Open in browser fallback, and a crashed renderer shows a Reload button. A floating auto-hide toolbar overlays the top with Edit (back to edit mode) and Maximize (fullscreen), plus Refresh, Open in browser, Copy URL and Screenshot. Refresh reloads the share's top frame, re-embedding the whole nested artifact tree fresh — it recovers a view an in-artifact link navigated off, or any share that rendered wrong (desktop-only, disabled until the page has loaded). Screenshot captures the entire scrolling page, not just the visible part, and copies the PNG to the clipboard (desktop-only, inert until the page has finished loading; see Full-page screenshot in part 2). The toolbar fades after 3 seconds of no interaction and returns on hover, a tap, or keyboard focus; a tap on the faded toolbar only reveals it, and the next tap presses the button. Edit mode has no floating toolbar (the header band carries the way into View), and the edit-mode preview is muted whenever it scrolls off screen, while view and fullscreen always play.

    • Fullscreen mode. The SAME viewer host and the same <webview> guest — only its box changes: it covers the whole window with an opaque background. The toolbar shows an Exit full screen button instead of Edit/Maximize, and a focus trap plus capture-priority Escape come on with it. Exits via Escape or the toolbar's Exit button, both returning to view mode.

      One viewer for the whole pane. The viewer host is a single element mounted for edit / view / fullscreen alike and only its styling changes, because a <webview> that remounts is a <webview> that re-navigates. The header band is pinned above the viewer rather than scrolling with the Edit form. Below the viewer, a share that HAS comments shows the Comments card in its own bounded, separately scrolling region; a share with no comments renders the viewer alone. The viewer itself is never inside anything that scrolls — the guest must not keep playing out of sight, and the floating toolbar is the only way back to Edit. A #comments deep link opens straight in view mode already scrolled to the comments, and Ctrl+Enter submits only in edit mode.

  3. Inline metadata + edit form (replaces the old SharesEditModal). One form region inside the pane; Ctrl+Enter / Cmd+Enter submits the patch. Fields:
    • Label. Text input, max 200 chars, required (an empty value disables Save).
    • Expires. A datetime-local input — a share's expiry is always a concrete instant. A past time marks the share Expired on the next refresh. There is no "Never expires" checkbox and no way to re-mint a permanent link: the form writes a concrete date and never null.
    • View cap. A "Limit total views" checkbox plus a number input (1 – 999,999). Below it, when viewCount > 0, a hint reads Currently N views or Currently N views of CAP. The Cloud Function refuses to serve the share once view_count >= view_cap.
    • Notify on view. A "Notify me when someone views this share" checkbox. When enabled, the desktop fires a "Share viewed: <label>" notification when the poller sees a view_count increase; notifications coalesce to at most one per share per rolling hour and carry the running total. Clicking it brings the app forward and opens that share.
    • Mute notifications. A "Mute notifications for this share" checkbox that overrides BOTH "notify on view" AND the global comment inbox alerts for this share. View counts, comment counts and pushes still update normally; only OS notifications and inbox items are suppressed. Stored locally in SQLite (mute_notifications column), not Firestore.
    • Save / Cancel footer. Save is disabled until the form is dirty AND valid. Cancel reverts every field to the server's state. Neither button closes the pane — the pane is always open.
  4. Password protection (replaces the old SharesEditModal protection section). A dedicated sub-card with three states:
    • No password set → Set password, which reveals a password input + "Save password". The plaintext is hashed in the renderer via SubtleCrypto (PBKDF2-SHA256, 600,000 iterations, 16-byte random salt, 32-byte derived key) and only the hex-encoded { passwordHash, passwordSalt } ship across IPC — plaintext never crosses the boundary.
    • Password already set → Change password (same flow) + a red Remove that sends nulls to clear the gate. An amber Protected lock badge appears beside the section header.
    • Save fires separately from the label/expiration patch, so protection changes apply immediately, independent of the main Save button. An eye-icon toggle shows/hides the plaintext while typing.
  5. Send share (replaces the old SharesSendModal). Collapsed by default — a Send to… row expands a 3-tile channel picker (Gmail / SMS / Slack), recipient input, optional message and a Send / Cancel footer. The recipient label and hint adjust per channel:
    • Gmail wants an email address, sent as a new thread.
    • SMS wants an E.164 phone number.
    • Slack wants a raw channel ID (starts with C, D or G). Recipient is required (1000-char cap); message is optional (5000-char cap, blank-line-separated above the URL). Submit calls ipc.invoke(IPC.SHARE_SEND, { shareId, channelKind, recipient, message? }). On success the panel collapses with a toast; on failure it stays open with the channel's error verbatim so you can fix the recipient and retry. While the Send panel is open, the form-level Ctrl+Enter submit is disabled so it doesn't fight the channel submit.
  6. Comments section. When the share has commentsEnabled, a collapsible "Comments" section appears showing mirrored comment activity from the linked public share page. It is one element rendered by whichever layout is live, so it is reachable in view mode too (below the viewer) and not only inside the edit form — a #comments deep link opens the share in view mode already scrolled to its newest comment. In view mode the section is gated on the share's main-computed commentCount > 0, so a comment-less share renders no Comments card there. The inline edit form also exposes an "Allow comments" toggle to enable or disable commenting per share.
  7. Destructive actions footer. A final card with four buttons:
    • Republish — visible only when the share is revoked OR expired. Confirms, mints a fresh URL via republishShare, revokes the old row server-side, and clears selectedShareId so the sidebar re-surfaces the new row.
    • Update — visible only for an ACTIVE artifact share with an on-disk source. Confirms (it overwrites what the live link serves), then refreshes the share's content IN PLACE from its source file via updateShareInPlace, so the same URL serves the new content and the toast reads "Share updated (same link)". On the rare relay fallback it publishes a new link, retires the old, lands on the new row, and reads "Published a new link…". Distinct from Republish, which deliberately mints a fresh URL. See share-artifacts.md § Update in place.
    • Revoke — visible only while the share is active. Confirms, calls revokeShare, marks the row Revoked. Signed out, Revoke is refused: the toast reads "Sign in to Omniscio before revoking this share. Nothing was changed.", the share stays live exactly where it was, and nothing moves to Archived & expired. Sign in, then revoke again.
    • Delete — always visible, red-bordered. Confirms (danger variant), calls deleteShare, and navigates back to projects on mobile so the deleted row isn't stuck on screen. Signed out, Delete is refused: the toast reads "Sign in to Omniscio before deleting this share. Nothing was deleted.", the share stays exactly where it was, and no expired copy is left behind. Sign in, then delete again.

Sending a share via channel

The inline Send to… sub-panel hands the share URL to Gmail, SMS or Slack: Omniscio builds the body (optional note + share URL), dispatches through the matching service, and writes a row to share_send_log so you can audit every send, successful or failed.

  • Outcome. A success toast fires and the sub-panel collapses ("Share sent via Gmail"); a structured failure (e.g. Slack channel_not_found) leaves it open so you can fix the recipient and retry. Revoked, expired or unpublished shares fail the pre-flight check with Share is revoked / Share has expired / Share has not been published before any channel call.
  • Audit. Every send writes a share_send_log row — pending on insert, then sent (stamps sentAt, clears the error) or failed (records the channel's error string, leaves sentAt null). The pending row is inserted before dispatch, so a thrown channel call still leaves an audit trail. List them with ipc.invoke(IPC.SHARE_SEND_LOG_LIST, { shareId }), newest-first.

How protection enforcement works

The Cloud Function that serves shares (the same one that mints the OG unfurl and renders the public page) reads password_hash, password_salt, view_cap and view_count from the Firestore mirror on every request:

  • View cap. If view_cap is non-null and view_count >= view_cap, the CF returns a 410 "share view cap reached" page without counting a view.
  • Password gate. If password_hash is set, the CF serves a password prompt. On submit it runs the same PBKDF2 derivation (600,000 iterations, SHA-256, the same salt) and constant-time-compares the result. A mismatch re-renders the prompt with an error; a match sets a short-lived signed unlock grant and serves the share. The plaintext never leaves the verifier function. The grant travels inside the single __session cookie, because Firebase Hosting strips every other cookie; the counted-view and workspace grants ride in the same cookie. A recording's video plays in a sandboxed frame that gets no cookie when a browser blocks third-party cookies, so the server writes a six-hour pass tied to that one share into the frame's video addresses.
  • View counter. Every successful render by a person atomically increments view_count and stamps last_viewed_at; that pair is the whole per-view record, with no per-view event row. A view-capped share keeps one dedupe doc per viewer network (a salted hash of the network prefix, with an expiry) so a reload does not consume another view — see share-view-events.md for the privacy model. A machine fetch is never counted and never consumes the cap; share-artifacts part 2 § Per-share protection lists everything refused (including the x-share-view-no-count header our own fetchers send). The desktop poller reads changed shares about once a minute while shares are being viewed, slows to at most once every 5 minutes when nothing is happening, and snaps back to a minute as soon as a view or comment lands; it mirrors the count and last-viewed time into the local SQLite shares row. After each poll, a share with notify_on_view = 1 whose count advanced can fire a desktop notification — at most one per share per rolling hour, carrying the running total. The row write is committed before the notification fires, so a crash mid-fire costs at most one missed notification, never a double-fire.

Smart Share Reaper

A background sweep runs for every account. It finds shares and screen recordings that never expire, are over a year old AND effectively unviewed — never viewed at all, or last viewed more than 90 days ago. Rather than deleting anything outright, it gives each one a 90-day grace expiry and drops a single inbox card asking you to Keep it. Keep clears the grace expiry, so the link goes back to never expiring, and snoozes the next check for a year. If you do nothing, the link expires when the 90 days are up and is taken offline. The sweep runs quietly alongside the regular share housekeeping, every six hours.

On a card about a screen recording, Delete is permanent. It stops the link and also erases the recording from your computer — the video, its thumbnail, captions and transcript, and its place in your library. Choose Keep, or simply ignore the card (the link then expires but the recording stays), if you want to keep the file.

On a phone

The phone (and any Web Access browser) has no Electron <webview>, so SharesDetailPane renders SharePhoneCard in the preview's place:

  • The card. The share's title, its views (Viewed N of CAP when a cap is set, otherwise Views: N), its expiry text, and a large Open share button that opens the public link in the phone's own browser. Pointer labels: shares-phone-card and shares-phone-card-open.
  • No View or Full screen. The header's View button is hidden, the viewer and its toolbar are never mounted, and a #comments link lands on the normal layout instead — the comments are in it, so nothing is lost and the phone can never be stranded in a view with no way back.
  • Everything else stays. Rename, expiry, view cap, password, Send to…, comments, Revoke, Delete and Republish all work on the phone exactly as on the desktop.

Desktop-only pieces, and why (the card says this in one line, so nothing quietly disappears):

Piece Why it is desktop-only
In-app preview, View and Full screen They render the share in an Electron <webview>, which a phone browser cannot load.
Screenshot Full-page capture drives the Chrome DevTools protocol against that <webview>.
Refresh It reloads the <webview>'s top frame through the same desktop-only route.
Drag-and-drop publishing The renderer cannot resolve a dropped file's path on the phone; a drop shows "Drag-and-drop publishing requires the desktop app".

The Shares integration's mobile decision in the UI registry stays ready, because the panel renders and works on a phone; the pieces above are the parts of it that do not.

Speed cost

What Shares costs the app, in the four numbers every soft-launch feature reports. Measured Nov 5, 2026; on-screen open time measured Nov 7, 2026.

Cost Number How it was measured
Startup Nothing on the startup path. The Shares poller starts after the window is up and runs its first check 60 seconds later; one live check took 553 ms, almost all of it waiting on the network. The startup task (2380-share-view-event-poller) is deferred and the poller is registered with immediate: false; the tick time is the live install's share-view-poller lastTickDurationMs from GET /diag/background.
Memory 80–116 MB per hidden preloaded share page, at most two alive. Opening the panel itself: see the open-time row. Each preloaded page is its own renderer process (measured 2026-10-12, see the prewarm note above).
Download size 63–110 KB for the panel, read from the app's own files (nothing from the internet) the first time Shares opens: the list 20 or 35 KB and the detail pane 43 or 75 KB; the viewer popup adds 9 or 12 KB. Each share page itself loads from the share server, or from the local share cache for your own shares. File sizes of the lazy-loaded SharesSidebar, SharesDetailPane and FloatingShareViewer chunks in the built renderer (out/renderer/assets, Nov 5 build). The build carries two copies of each part, so both sizes are given.
Open time Listing shares: about 10 ms in the main process for 619 shares (909 KB of list data). On screen, with 601 shares: 283 ms median (188–447 ms) from opening Shares to the first share row drawn, and 600 ms median (388–645 ms) from clicking a share to all 20 of its comments drawn. Runs: panel 188, 281, 283, 320, 447 ms; comments 388, 395, 600, 629, 645 ms. List read: GET /share/list?includeRevoked=true on the live install, the same read the panel makes; 10 runs against 10 runs of a trivial request, medians 139 ms and 131 ms, both carrying the ~120 ms start-up of the calling tool. On screen: Five cold runs of tests/e2e/ui/shares-speed-cost.spec.ts on the cloud E2E runner (the repository's end-to-end run, Nov 7, 2026), one after another, each in a fresh test app seeded with 600 placeholder shares plus one share carrying 20 placeholder comments. The panel clock starts on Enter on the sidebar's Shares row and stops when the first shares-sidebar-row is in the page; the comments clock starts on the share-row click and stops when all 20 comment rows are in the page.

How often it checks: once a minute while shares are being viewed or commented on, slowing to once every 5 minutes when nothing is happening (see "How protection enforcement works" above).

Measure or re-measure the on-screen open time: run tests/e2e/ui/shares-speed-cost.spec.ts through the repository's end-to-end run; it runs 5 cold runs, each seeding 600 placeholder shares, and prints the panel and comment open times as [shares-speed-cost]. The cloud E2E road returns no console output for a passing test, so to read the numbers back the Nov 7 measurement added a temporary last check that failed with all five runs in its message, then removed it.

Last verified 2026-11-05