Skip to content

YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context

refactor(app): move notification bell from window chrome into Pipes view (#4063)

Louis Beaumontd0aa2f7ea22e
diff --git a/apps/screenpipe-app-tauri/app/home/page.tsx b/apps/screenpipe-app-tauri/app/home/page.tsx
index 207e92f02..8184fd1b2 100644
--- a/apps/screenpipe-app-tauri/app/home/page.tsx
+++ b/apps/screenpipe-app-tauri/app/home/page.tsx
@@ -45,7 +45,6 @@ import { ChatHistoryView } from "@/components/chat/chat-history-view";
import { mountPiEventRouter } from "@/lib/stores/pi-event-router";
import { mountPipeRunRecorder } from "@/lib/events/pipe-run-recorder";
import { mountPipeWatchWriter } from "@/lib/events/pipe-watch-writer";
-import { NotificationBell } from "@/components/notification-bell";
import { RecordingStatus, type RecordingDevice } from "@/components/recording-status";
import Timeline from "@/components/rewind/timeline";
import { useQueryState } from "nuqs";
@@ -905,14 +904,16 @@ function HomeContent() {
{/* Sidebar */}
<TooltipProvider delayDuration={0}>
{/* Top-left chrome strip — pinned next to the macOS traffic
- lights: sidebar toggle, search, recording-status dot and
- notification bell. No wordmark, no header row (Claude /
- Codex style). When the sidebar is collapsed it is hidden
- entirely and the strip floats over the content, reduced to
- toggle + status dot. The h-8 drag region already keeps the
- top band free of interactive content, so nothing collides.
- Fixed positioning anchors the strip to the viewport so it
- isn't clipped by AppSidebar's overflow. */}
+ lights: sidebar toggle, search and recording-status dot.
+ No wordmark, no header row (Claude / Codex style). When
+ the sidebar is collapsed it is hidden entirely and the
+ strip floats over the content, reduced to toggle + status
+ dot. The h-8 drag region already keeps the top band free
+ of interactive content, so nothing collides. Fixed
+ positioning anchors the strip to the viewport so it isn't
+ clipped by AppSidebar's overflow. The notification bell
+ lives in the Pipes view header (pipe-store.tsx) since
+ notifications are pipe output. */}
<div
className={cn(
// top-0.5 + items-center puts each icon's center at y≈15px,
@@ -979,7 +980,6 @@ function HomeContent() {
onToggleMeeting={() => void toggleMeeting()}
isTranslucent={isTranslucent}
/>
- {!sidebarCollapsed && <NotificationBell />}
</div>
{/* Collapsed = hidden. No icon-rail fallback — the floating
diff --git a/apps/screenpipe-app-tauri/components/pipe-store.tsx b/apps/screenpipe-app-tauri/components/pipe-store.tsx
index d146a3b7b..b754e2537 100644
--- a/apps/screenpipe-app-tauri/components/pipe-store.tsx
+++ b/apps/screenpipe-app-tauri/components/pipe-store.tsx
@@ -64,6 +64,7 @@ import { MemoizedReactMarkdown } from "@/components/markdown";
import remarkGfm from "remark-gfm";
import posthog from "posthog-js";
import { PipesSection } from "@/components/settings/pipes-section";
+import { NotificationBell } from "@/components/notification-bell";
import { ChatPrefillData } from "@/lib/chat-utils";
import { useFeedbackStore } from "@/lib/stores/feedback-store";
// --- Types ---
@@ -374,6 +375,12 @@ export function PipeStoreView() {
{label}
</button>
))}
+ {/* Notifications are pipe output, so the bell lives here rather
+ than in the global window chrome. mb-3 cancels the tabs'
+ pb-3 so the bell centers on the tab labels, not the row. */}
+ <div className="ml-auto mb-3">
+ <NotificationBell />
+ </div>
</div>
{/* Tab content */}
diff --git a/apps/screenpipe-app-tauri/e2e/specs/windows-user-journey.spec.ts b/apps/screenpipe-app-tauri/e2e/specs/windows-user-journey.spec.ts
index 976b75426..bfc7e94a9 100644
--- a/apps/screenpipe-app-tauri/e2e/specs/windows-user-journey.spec.ts
+++ b/apps/screenpipe-app-tauri/e2e/specs/windows-user-journey.spec.ts
@@ -68,6 +68,14 @@ async function postNotification(id: string, title: string, body: string): Promis
}
}
+// The notification bell lives in the Pipes view tab bar (notifications
+// are pipe output), not the global window chrome — navigate there first.
+async function openPipesView(): Promise<void> {
+ const navPipes = await $('[data-testid="nav-pipes"]');
+ await navPipes.waitForDisplayed({ timeout: t(20_000) });
+ await navPipes.click();
+}
+
async function clickFirstDisplayed(selector: string, timeoutMs = t(15_000)): Promise<void> {
const deadline = Date.now() + timeoutMs;
@@ -721,6 +729,7 @@ describe("Windows user journey", function () {
const itemSelector = `[data-testid="notification-bell-item-${notificationId}"]`;
const expandedSelector = `[data-testid="notification-bell-expanded-${notificationId}"]`;
+ await openPipesView();
const bell = await $(bellSelector);
await bell.waitForDisplayed({ timeout: t(20_000) });
await bell.click();
@@ -801,6 +810,8 @@ describe("Windows user journey", function () {
const homeSection = await $('[data-testid="section-home"]');
await homeSection.waitForExist({ timeout: t(20_000) });
+ // "Back to app" lands on the chat view; the bell is in the Pipes view.
+ await openPipesView();
const reopenedBell = await $(bellSelector);
await reopenedBell.waitForDisplayed({ timeout: t(20_000) });
await reopenedBell.click();
diff --git a/docs/mockups/notification-bell-pipes-view.png b/docs/mockups/notification-bell-pipes-view.png
new file mode 100644
index 000000000..3fb50e06a
Binary files /dev/null and b/docs/mockups/notification-bell-pipes-view.png differ