build69
build69  /  Components  /  App  /  Inbox

Inbox

v1.0.34Updated 20 Oct 2026

Inbox / messaging page — three-pane, email client, chat messenger, unified and support-ticket layouts. Full-page copy-paste template; baked-in demo content (edit the JSX to customise).

Preview

Live · 18 stories
Three PaneOpen ↗
▸Why this is recommendedinboxmessagesemailchat+4

Inbox — three pane.

Recommended for+14
  • ✓Inbox / messaging screens
  • ✓Support apps
Tags+6
inboxmessagesemailchatapppagethreepane
Features+4
  • i18n: a labels prop overrides every built-in string; English defaults, brand-free copy
  • Three-pane, email-client, chat-messenger, unified and split-reading layouts
  • Support-tickets / conversation variants
  • Self-contained — no required props
Not recommended for−2
  • ✕Public marketing pages

Install

Ask your agent, or call the MCP tool directly. The resolved bundle is written into your project.

get_registry_item({ name: "Inbox" })

Usage

import { InboxThreePane } from '@/components/pages/inbox';

<InboxThreePane />

Tick variants in the left menu — each adds a tab with that variant’s real story source, the same code the preview above renders.

Props

PropTypeRequired
className

Optional wrapper class override (copy-paste block, baked-in content)

string—
threads

InboxThreePane and InboxEmailClient only: the threads to show; defaults to the built-in demo mailbox.

InboxThread[]—
threadsByTab

InboxTabbed only: the threads in each tab, as Record<"primary" | "updates" | "spam", InboxThread[]>; defaults to the built-in demo mailbox.

InboxTabThreads—
labels

Override every built-in string and aria-label (i18n). Merged over DEFAULT_INBOX_LABELS (106 English keys); every template in the file accepts it. The rendered DEFAULTS are English — page templates used to hardcode their copy, which no consumer could translate or ship. MCP feedback fb_ba2ec12f.

Partial<InboxLabels>—

Related