Skip to content
Back

Agent InboxPro

Questions agents are waiting on: a 320 px list tinted by project with Open / Done tabs, one question at a time with its answers, and the task behind it in the work area. One keystroke answers and the next question glides in.

oxyn add inbox

Inbox

5

Event pipeline· 4m ago

Which queue should the event service use?

Orders land in bursts of up to 20k a minute. The service has to retry, and to replay a whole day of events after a bad release.

The code is part of Oxyn Pro

The preview stays free for everyone. Pro opens the code of every Pro component, screen, agent-app template, block and kit, plus the Pro CLI.

Get Pro

Rendered from Rust at build time · goes live when visible

When to use

  • Every question agents are waiting on, answered one at a time with a single keystroke.

When not to use

  • Mail folders with counts and labels beside a message list: use Inbox sidebar instead.
  • The app frame: use App shell instead.
  • An assistant docked beside a page: use AI side panel instead.

Installation

Agent Inbox is part of Oxyn Pro; the preview is free. Pro items install with the oxyn CLI once your licence is signed in; until then Pro members copy the code from this page.

Terminal
oxyn add inbox

Usage

Dioxus · rust
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Examples

Sample

Sample data in the Inset frame.

Inbox

5

Event pipeline· 4m ago

Which queue should the event service use?

Orders land in bursts of up to 20k a minute. The service has to retry, and to replay a whole day of events after a bad release.

Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Flat

The same screen in the Flat frame.

Inbox

5

Event pipeline· 4m ago

Which queue should the event service use?

Orders land in bursts of up to 20k a minute. The service has to retry, and to replay a whole day of events after a bad release.

Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Loading

Skeletons where the data will land.

Inbox

0

Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Empty

Nothing yet: each region says what will appear and how to start.

Inbox

0

No questions yet.

Nothing needs you yet

When an agent needs a decision, the question waits here with its options.

Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Answered

Just answered: the next question has glided in, with Undo.

Inbox

4

Client dashboard· 18m ago

Which empty state goes on the dashboard?

New accounts open the dashboard before any orders exist. Two drafts are ready; pick the one to build.

Sent “Kafka”

Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Peek

Oxyn: a peek at the next question.

Inbox

5

Event pipeline· 4m ago

Which queue should the event service use?

Orders land in bursts of up to 20k a minute. The service has to retry, and to replay a whole day of events after a bad release.

NextWhich empty state goes on the dashboard?

Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

Hold

Oxyn: stay on the answered question.

Inbox

5

Event pipeline· 4m ago

Which queue should the event service use?

Orders land in bursts of up to 20k a minute. The service has to retry, and to replay a whole day of events after a bad release.

Code Pro
The code is part of Oxyn Pro

The preview is free. Pro opens the code of every Pro component, screen and template.

Get Pro

API reference

InboxScreen

PropTypeDefaultDescription
layoutString"inset"`inset` or `flat`.
stateString"sample"A state key.
heightu32640Height px.
peek_nextboolDefault::default()Oxyn: a peek at the next question under the answer bar.
holdboolDefault::default()Oxyn: stay on the answered question instead of gliding to the next.

Read from the Rust signature and doc comments.

Keyboard interactions

KeyAction
TabSidebar, page, then each control in reading order
←or→ in a tab rowMove between tabs
EscapeClose an open menu or popover; clear a search
1–9 on a questionAnswer with that choice; the next question glides in
YorNFirst or second answer
↑or↓ then EnterPick and send
LLater: move it to the end

Accessibility

  • The Fieldwork sidebar is a labelled nav with aria-current on this page.
  • Tabs are a tablist with arrow keys; menus report aria-expanded and close on Escape.
  • Skeletons are hidden from screen readers; every action reports what it did in a polite live region.
  • Answers are a radiogroup; the question region names its shortcuts with aria-keyshortcuts; Undo sits in a status toast.

Responsive behaviour

  • Authored on the 1440 × 900 canvas; the full view lays it out at the real width.
  • Under 640 px the sidebar slides in from the menu button and top-bar actions keep their icons with hidden labels.
  • Under 760 px the list stacks above the question.
Edge cases (spec)

Authored on the 1440 × 900 stage (rule R1) and scaled to its column; the full view (/screens/inbox/full) renders at the real viewport with the state bar under it (R2). Under 640 px the sidebar slides in from a menu button. Under 760 px the list stacks above the question (max 42 % of the height); under 520 px the question title is 19 px. Every label in a row, chip or card ellipsises in a flex child with min-width 0 (R5); scripts/ovl.py finds no text overlap at 1440, 768 and 390 in light and dark.

Notes for AI

  • Import InboxScreen from oxyn_dioxus and include STATUS_INDICATOR_CSS plus the token stylesheet once.
  • A GPUI version exists: InboxScreenEl in oxyn_gpui.
  • Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.

Guides

Oxyn · 74 free components · 264 Pro components · 96 screens · 20 blocks · Dioxus and GPUI