Notification and Inbox
Respond to original session requests and view shared work updates and unread indicators
Notification is a City-level Power built into Desktop by default. Each City has one notification state. Inbox, conversation indicators, navigation dots, and the application badge all consume its shared snapshot and refresh when data changes.
Browse Inbox
The Sidebar offers three categories:
- Needs attention: respondable requests and unread failures.
- Notifications: ordinary notifications, including read records.
- All: all Inbox items, deduplicated.
The main area presents an item list with titles, summaries, sources, and times. Selecting an item opens its details on the right when the main area is wide enough, keeping the list visible. In a narrow area, details replace the list and provide a Back action. Entering Inbox does not automatically select an item. Clearing the selected update closes its details without opening or marking the next item as read.
Inbox uses Downcity's borderless layout. The entire list panel has a consistent subtle background to distinguish it from the detail body; hovered and selected items use separate interaction backgrounds. Agent items lead with an avatar, repeated beside the source name in details. An unconfigured avatar or unavailable Agent directory uses the default Agent icon; Power updates without an Agent use a business icon. Avatars and names come from Desktop's current directory. The desktop list stays 360px wide at the same position before selection, while details are open, and after closing them. The title, count, refresh, organization menu, and scrolling messages share one subtle panel with consistent padding. Each item has an independent 32px avatar column aligned with the top of the text. The first text row shows the sender followed immediately by the time, the second shows the actual notification title, and up to two lines summarize the actual body below. Empty summaries are omitted. Request summaries use only public questions or descriptions, never private input or raw approval parameters. The attention dot stays at the upper right; the menu has a separate lower-right slot, appears on hover or keyboard focus, and stays visible on touch without covering the dot or changing text width. Session and group notifications, including request headings, use the source session title. Results and errors remain in the body, and original question and approval prompts are preserved. Renaming a session refreshes the displayed title without changing read state or notification time. An unnamed session displays “未命名会话”; unavailable sources retain their saved titles. Task notifications keep task titles. Details omit missing body content. The 36px list header contains only the category, count, refresh, and more menu. The right area stays blank until selection. Details and forms fill the remaining width with consistent padding; long code and Markdown stay within the available area. The detail toolbar is also 36px high, with matching lightweight navigation buttons. Form actions use shared 32px primary and secondary buttons.
Item states share the Rail's attention colors: amber for requests needing a response, red for failures, and blue for success and informational notifications. Reading removes the dot while preserving the business outcome; a read failure still indicates failure, not recovery. Requests that can no longer receive a response show a neutral interrupted state.
Pending requests
Pending requests are questions and approvals from the Agent's original Session. Opening Inbox, selecting a request, or viewing its source does not finish it. A request leaves the queue only after a successful response or when the original request becomes invalid. Respondable requests count toward the badge; interrupted requests remain visible with an explanation.
In Desktop, the conversation that initiated a task also presents questions, approvals, and private input from every level of its delegation chain above the chat input, including work delegated to other Agents. Sources show the task name and executing Agent, with execution details available on demand; arrows switch between requests. Inbox and the conversation show the same original request, and responding in either removes it from pending in the other. Unrelated tasks keep their requests in their own conversations and Inbox.
Answers and approvals submitted in Inbox or the initiating conversation go back to the original Session. Private questions use the Session's dedicated submission channel; plaintext answers are not stored in notifications. An unreachable source is shown as unknown, with its last known content retained. Refresh to retry after the connection recovers. A busy or timed-out request query, or a source being deleted, archived, or cleared, also retains the last known requests and disables responses until a successful refresh. A failed read does not mean a request has been handled.
Details contain the question, approval, or private input form. Matching question or approval titles appear once; multiple questions retain their individual prompts and navigation. Background refresh preserves selection and entered values. Switching, closing, or viewing the source asks before discarding unsubmitted edits. Submission disables duplicate responses and shows the result in place, with an explicit action to move to the next item.
Notifications and reading
Ordinary Agent replies create unread indicators in conversations and Chat navigation. They do not appear in Inbox Notifications or increase the application badge. Agent conversation failures and background Work Main results and failures enter Inbox. A Main collects its Children's results; Task, Memory, Messenger, and other business Powers publish at their own delivery boundaries. Group failures enter Inbox; successful group completion does not publish an ordinary update. Questions and approvals reference the member's original Interaction.
Notifications retains read records. Use Mark as read in a notification row's menu or view that notification's details in a focused, visible window. The list header's organization menu offers Mark all notifications as read: it acknowledges only ordinary Inbox notifications in the snapshot at the time of the click, across all categories, and keeps their records. New matters and newer versions arriving afterward remain unread. Opening the Inbox list does not mark all notifications as read. Viewing the original conversation in a focused, visible window marks its ordinary notifications as read. Entering a Power workspace does not mark all of its notifications as read.
Notification row menus offer Clear this notification, and the header menu offers Clear read notifications. Clearing removes only ordinary Inbox notifications, leaving conversation, Task, and Group execution history intact. A later event for the same matter can notify again. Clear read notifications only affects read ordinary Inbox notifications in the snapshot at the time of the click, across all categories. Every shortcut checks the notification ID and content timestamp, so a delayed operation cannot consume newer content. Questions, approvals, and private input requests remain original Interactions; marking or clearing notifications never finishes them. Actions disable repeat submission while running and retain content with an error message if they fail.
The application badge and Inbox navigation number count respondable pending requests plus unread Inbox failure matters. Success and informational updates stay in Inbox with unread dots and do not increase the application number. Conversation reply unread state is also excluded. The sidebar and navigation tooltip explain the pending-request and unread-failure components; the Notifications category separately shows the unread notification count. The Sidebar Inbox number is red only when unread failures exist, amber when only pending requests remain, and a blue dot indicates ordinary unread updates.
Power supplies pending_request_count (respondable original requests), unread_update_count (all ordinary unread Inbox updates), unread_failure_count (the failure subset), and badge_count (pending requests plus unread failures) in one snapshot. The list, navigation, and system badge share these values. Desktop consumes the final badge_count directly.
Notifications represent matters that need attention. Each Agent conversation or group conversation updates one record; successive Task runs update the same task matter. A new result replaces the summary and becomes unread, while execution history stays with its source. Repeating the same original event preserves read state. Explicit outcome fields distinguish success and failure. Publisher withdrawal removes only the notification; it never completes tasks, accepts results, or approves operations.
Sources and lifecycle
View source opens the current conversation or business result. Session identity is independent of its Workspace binding. Archiving or deleting a source, or removing its Agent or Group, retains the notification summary and read state. Details explicitly show archived, removed, or unknown/unreachable sources. An unavailable source cannot create a replacement conversation.
Notification startup does not read conversation history. Source changes refresh the view; reading or explicitly refreshing notifications checks only the sources they reference. Reading Inbox or refreshing the badge only reads a snapshot; it never writes, migrates, or deletes notifications. Original Sessions supply accurate request origins. Unknown origins remain visible, and a live original request remains respondable; storage categories are never used to guess business roles.
System integration uses the application icon badge, subject to platform support.
Task banners and in-app notifications
Task reminders, results awaiting acceptance, successful executions, failures, triggers that cannot start, and missed arrangements enter in-app notifications and request a Desktop system banner. System display failures do not affect task state or in-app matters. Banners do not own separate unread state: clicking only opens the task or execution record, and dismissing one neither clears Inbox nor accepts work. System notifications require a running app and operating-system permission; restarting does not replay historical banners. See Task Power.