Agent / Tasks Pro Tasks grouped by project with progress rings, what each is doing and a Needs you tag. The work area holds the decision waiting (Decide answers it inline), steps, what happened so far, artifacts and what was decided.
⌘K Thread Inbox 5 Agents Tasks Memory Skills Workspace
Schedules Activity Usage Permissions Settings
Tidewater 4 Event pipeline Choosing a queue Needs you 2/4 44m Client dashboard Picking an empty state Needs you 1/3 418m Weekly note Ready to send Needs you 2/3 442m Welcome emails Drafting the copy 1/3 412m Platform 3 Billing hooks Shipping to staging 3/4 46m API sunset Settling the v1 end date Needs you 2/4 43h Support triage Rolling out to every queue 2/3 425m Benchkit 2 Launch post Settling on a tone Needs you 1/4 41h Eval suite Running the evals 3/5 42m
Collect Tidewater's order events and keep a day of them to replay after a bad release.
Needs you 1 decision waiting Which queue should the event service use? Decide
Status Choosing a queue 2/4
Project Tidewater
Started Mon, 3 Nov
Steps Draft the event schema , done Load test at 20k a minute , done Choose a queue Needs you , now Ship to staging , todo So far Asked you which queue fits Load test held at 20k events a minute Wrote the design note and the schema Artifacts 4 pipeline-design.md load-test.csv event-schema.json staging Decided Which format for the events? JSON with a version field · 3 days ago State Data Loading Empty Done tab
1440 × 900 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 ProRendered from Rust at build time · goes live when visible
When to use Every task the agents run, grouped by project, with what each one needs from you. 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 / Tasks 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.
Usage The code is part of Oxyn Pro The preview is free. Pro opens the code of every Pro component, screen and template.
Get ProExamples Sample Sample data in the Inset frame.
⌘K Thread Inbox 5 Agents Tasks Memory Skills Workspace
Schedules Activity Usage Permissions Settings
Tidewater 4 Event pipeline Choosing a queue Needs you 2/4 44m Client dashboard Picking an empty state Needs you 1/3 418m Weekly note Ready to send Needs you 2/3 442m Welcome emails Drafting the copy 1/3 412m Platform 3 Billing hooks Shipping to staging 3/4 46m API sunset Settling the v1 end date Needs you 2/4 43h Support triage Rolling out to every queue 2/3 425m Benchkit 2 Launch post Settling on a tone Needs you 1/4 41h Eval suite Running the evals 3/5 42m
Collect Tidewater's order events and keep a day of them to replay after a bad release.
Needs you 1 decision waiting Which queue should the event service use? Decide
Status Choosing a queue 2/4
Project Tidewater
Started Mon, 3 Nov
Steps Draft the event schema , done Load test at 20k a minute , done Choose a queue Needs you , now Ship to staging , todo So far Asked you which queue fits Load test held at 20k events a minute Wrote the design note and the schema Artifacts 4 pipeline-design.md load-test.csv event-schema.json staging Decided Which format for the events? JSON with a version field · 3 days ago State Data Loading Empty Done tab
1440 × 900 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 ProFlat The same screen in the Flat frame.
⌘K Thread Inbox 5 Agents Tasks Memory Skills Workspace
Schedules Activity Usage Permissions Settings
Tidewater 4 Event pipeline Choosing a queue Needs you 2/4 44m Client dashboard Picking an empty state Needs you 1/3 418m Weekly note Ready to send Needs you 2/3 442m Welcome emails Drafting the copy 1/3 412m Platform 3 Billing hooks Shipping to staging 3/4 46m API sunset Settling the v1 end date Needs you 2/4 43h Support triage Rolling out to every queue 2/3 425m Benchkit 2 Launch post Settling on a tone Needs you 1/4 41h Eval suite Running the evals 3/5 42m
Collect Tidewater's order events and keep a day of them to replay after a bad release.
Needs you 1 decision waiting Which queue should the event service use? Decide
Status Choosing a queue 2/4
Project Tidewater
Started Mon, 3 Nov
Steps Draft the event schema , done Load test at 20k a minute , done Choose a queue Needs you , now Ship to staging , todo So far Asked you which queue fits Load test held at 20k events a minute Wrote the design note and the schema Artifacts 4 pipeline-design.md load-test.csv event-schema.json staging Decided Which format for the events? JSON with a version field · 3 days ago State Data Loading Empty Done tab
1440 × 900 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 ProLoading Skeletons where the data will land.
State Data Loading Empty Done tab
1440 × 900 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 ProEmpty Nothing yet: each region says what will appear and how to start.
⌘K Thread Inbox 5 Agents Tasks Memory Skills Workspace
Schedules Activity Usage Permissions Settings
No tasks yet
Ask for an outcome in the thread, or start one with New task.
State Data Loading Empty Done tab
1440 × 900 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 ProFinished The Done tab with a finished task open.
⌘K Thread Inbox 5 Agents Tasks Memory Skills Workspace
Schedules Activity Usage Permissions Settings
Platform 1 Release notes 2.3 Sent to the team 3/3 41d Benchkit 1 Price page copy Merged 2/2 42d
Collect Tidewater's order events and keep a day of them to replay after a bad release.
Status Sent to the team 3/3
Project Platform
Started Mon, 3 Nov
Steps Draft the event schema , done Load test at 20k a minute , done Choose a queue , done Ship to staging , now So far Asked you which queue fits Load test held at 20k events a minute Wrote the design note and the schema Artifacts 4 pipeline-design.md load-test.csv event-schema.json staging Decided Which format for the events? JSON with a version field · 3 days ago State Data Loading Empty Done tab
1440 × 900 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 ProCost Oxyn: what each task has cost so far.
⌘K Thread Inbox 5 Agents Tasks Memory Skills Workspace
Schedules Activity Usage Permissions Settings
Tidewater 4 Event pipeline Choosing a queue Needs you €0.25 2/4 44m Client dashboard Picking an empty state Needs you €0.32 1/3 418m Weekly note Ready to send Needs you €0.39 2/3 442m Welcome emails Drafting the copy €0.46 1/3 412m Platform 3 Billing hooks Shipping to staging €0.53 3/4 46m API sunset Settling the v1 end date Needs you €0.60 2/4 43h Support triage Rolling out to every queue €0.67 2/3 425m Benchkit 2 Launch post Settling on a tone Needs you €0.74 1/4 41h Eval suite Running the evals €0.81 3/5 42m
Collect Tidewater's order events and keep a day of them to replay after a bad release.
Needs you 1 decision waiting Which queue should the event service use? Decide
Status Choosing a queue 2/4
Project Tidewater
Started Mon, 3 Nov
Steps Draft the event schema , done Load test at 20k a minute , done Choose a queue Needs you , now Ship to staging , todo So far Asked you which queue fits Load test held at 20k events a minute Wrote the design note and the schema Artifacts 4 pipeline-design.md load-test.csv event-schema.json staging Decided Which format for the events? JSON with a version field · 3 days ago State Data Loading Empty Done tab
1440 × 900 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 ProFolded Oxyn: groups start folded.
⌘K Thread Inbox 5 Agents Tasks Memory Skills Workspace
Schedules Activity Usage Permissions Settings
Tidewater 4 Event pipeline Choosing a queue Needs you 2/4 44m Client dashboard Picking an empty state Needs you 1/3 418m Weekly note Ready to send Needs you 2/3 442m Welcome emails Drafting the copy 1/3 412m
Collect Tidewater's order events and keep a day of them to replay after a bad release.
Needs you 1 decision waiting Which queue should the event service use? Decide
Status Choosing a queue 2/4
Project Tidewater
Started Mon, 3 Nov
Steps Draft the event schema , done Load test at 20k a minute , done Choose a queue Needs you , now Ship to staging , todo So far Asked you which queue fits Load test held at 20k events a minute Wrote the design note and the schema Artifacts 4 pipeline-design.md load-test.csv event-schema.json staging Decided Which format for the events? JSON with a version field · 3 days ago State Data Loading Empty Done tab
1440 × 900 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 ProAPI reference TasksScreen Prop Type Default Description layoutString"inset"`inset` or `flat`. stateString"sample"A state key. heightu32640Height px. costboolDefault::default()Oxyn: a cost column on each row. foldedboolDefault::default()Oxyn: groups start folded.
Read from the Rust signature and doc comments.
Keyboard interactions Key Action Tab Sidebar, page, then each control in reading order ← or → in a tab row Move between tabs Escape Close an open menu or popover; clear a search Enter on a group Fold or unfold it Enter on Decide Show the answers inline
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. Progress rings are hidden; each row states its steps as text; group heads report aria-expanded. 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 520 px the steps, files and age columns hide. Edge cases (spec) Authored on the 1440 × 900 stage (rule R1) and scaled to its column; the full view (/screens/agent-tasks/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 age hides; under 520 px the status sentence, steps, files and cost hide. 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 TasksScreen from oxyn_dioxus and include STATUS_INDICATOR_CSS plus the token stylesheet once. A GPUI version exists: TasksEl in oxyn_gpui. Keep its states and timings as they ship; restyle it through the CSS variables rather than by hand.