Task inboxPro
All your background agent tasks in one calm list – live clocks and status tags, filter tabs with rolling counts, rows that unfold to the last steps with Approve, Reject, Retry or Open, and glide to their new place.
oxyn add task-inbox- Read the schema and 3 migrations6m ago
- Wrote the migration and a rollback4m ago
- Dry run on staging: 48,112 rows in 41s2m ago
- Waiting for your approval to run on productionnow
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.
Rendered from Rust at build time · goes live when visible
When to use
- Collect every background agent task in one calm board – what waits for you, what runs and what finished – with the last steps and the decision one click away.
When not to use
- An agent asks before it acts: use Approval Card instead.
- Several open requests in one card: use Approval pager instead.
- An agent's question in its own card above the composer: use Decision Card instead.
Installation
Task 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.
oxyn add task-inboxUsage
The preview is free. Pro opens the code of every Pro component, screen and template.
Examples
Default
The board, with the waiting migration open on Reject / Approve; clocks tick and the release notes finish by themselves.
- Read the schema and 3 migrations6m ago
- Wrote the migration and a rollback4m ago
- Dry run on staging: 48,112 rows in 41s2m ago
- Waiting for your approval to run on productionnow
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
List
List layout: the same tasks as full-width rows under their headers.
- Read the schema and 3 migrations6m ago
- Wrote the migration and a rollback4m ago
- Dry run on staging: 48,112 rows in 41s2m ago
- Waiting for your approval to run on productionnow
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Closed
Every card folded.
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
Classic
Classic style: hairline cards and bold title-case headers.
- Read the schema and 3 migrations6m ago
- Wrote the migration and a rollback4m ago
- Dry run on staging: 48,112 rows in 41s2m ago
- Waiting for your approval to run on productionnow
Code Pro
The preview is free. Pro opens the code of every Pro component, screen and template.
API reference
TaskInbox
| Prop | Type | Default | Description |
|---|---|---|---|
tasks | Vec<InboxTask> | Default::default() | Tasks (the demo when empty). |
title | String | "Agent inbox" | Heading after "Agents /". |
view | String | "board" | `board` or `list`. |
open | String | Default::default() | The card open at the start. |
openable | bool | true | Show an Open button on running and done tasks. |
nowrequired | ClockMs | — | The clock. |
style | String | Default::default() | `clean`, `classic`, or empty to follow `data-cstyle`. |
on_action | EventHandler<(String, String)> | — | (`approve` | `reject` | `retry` | `open` | `view`, task id or view). |
Read from the Rust signature and doc comments.
Keyboard interactions
| Key | Action |
|---|---|
| Tab | The layout switch, then the cards and their buttons |
| EnterorSpace | Unfold or fold a card |
| Esc | Fold the card |
Accessibility
- Columns are labelled sections; cards are buttons with aria-expanded.
- The layout switch is a radiogroup; a status line reads "2 need you, 2 running".
- Status tags carry words as well as colour.
Responsive behaviour
- Fills its container up to 740 px; below 620 px the board stacks into one column.
Edge cases (spec)
Up to 740 px; below 620 px the board stacks into one column.
Notes for AI
- Import
TaskInboxfromoxyn_dioxusand includeSTATUS_INDICATOR_CSSplus the token stylesheet once. - A GPUI version exists:
TaskInboxElinoxyn_gpui. - Props to set first:
now. - It reads a clock (
now) for live timers; pass one clock for the whole page rather than one per component. - Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.