Skip to content
Back

AI Chat / ProgressPro

A chat whose tool calls open into cards, with the work beside it: steps ticking off, what it made and the uploads, apps, web pages and skills it used.

oxyn add chat-progress

Three people start Monday. Plan their first week and pair each with a buddy – the intake form is in Drive, the wiki in Notion.

I read the first-week pages and last spring's notes. The weeks that went well all had the same three parts: accounts on day one, one buddy, and a small task shipped by Friday.

Here is the week now:

  • Monday: laptops, accounts and lunch with their buddy
  • Tuesday to Thursday: one shadow day per team
  • Friday: a small first task, shipped together

Why is the new designer paired with someone from sales?

The intake form lists the designer under the team that hired the role, which is sales this quarter. I matched by the work instead, so the new pair is with the brand designer; the sheet is updated.

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

  • A chat whose tool calls open into cards, with its working notes in a column inside the page.

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

AI Chat / Progress 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 chat-progress

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.

Three people start Monday. Plan their first week and pair each with a buddy – the intake form is in Drive, the wiki in Notion.

I read the first-week pages and last spring's notes. The weeks that went well all had the same three parts: accounts on day one, one buddy, and a small task shipped by Friday.

Here is the week now:

  • Monday: laptops, accounts and lunch with their buddy
  • Tuesday to Thursday: one shadow day per team
  • Friday: a small first task, shipped together

Why is the new designer paired with someone from sales?

The intake form lists the designer under the team that hired the role, which is sales this quarter. I matched by the work instead, so the new pair is with the brand designer; the sheet is updated.

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.

Three people start Monday. Plan their first week and pair each with a buddy – the intake form is in Drive, the wiki in Notion.

I read the first-week pages and last spring's notes. The weeks that went well all had the same three parts: accounts on day one, one buddy, and a small task shipped by Friday.

Here is the week now:

  • Monday: laptops, accounts and lunch with their buddy
  • Tuesday to Thursday: one shadow day per team
  • Friday: a small first task, shipped together

Why is the new designer paired with someone from sales?

The intake form lists the designer under the team that hired the role, which is sales this quarter. I matched by the work instead, so the new pair is with the brand designer; the sheet is updated.

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.

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.

Ask for something that takes a few steps

You'll see each step and every tool it calls as it goes.

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

Working

A turn still working: the column ticks steps off live.

Three people start Monday. Plan their first week and pair each with a buddy – the intake form is in Drive, the wiki in Notion.

I read the first-week pages and last spring's notes. The weeks that went well all had the same three parts: accounts on day one, one buddy, and a small task shipped by Friday.

Here is the week now:

  • Monday: laptops, accounts and lunch with their buddy
  • Tuesday to Thursday: one shadow day per team
  • Friday: a small first task, shipped together

Why is the new designer paired with someone from sales?

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

ChatProgressScreen

PropTypeDefaultDescription
layoutString"inset"`inset` or `flat`.
stateString"sample"`sample`, `loading`, `empty` or `working`.
heightu32640Height px.
nowrequiredClockMs—The clock.

Read from the Rust signature and doc comments.

Keyboard interactions

KeyAction
TabSidebar, page, then the work area
←or→ on a hairlineResize the sidebar or work area
EscapeClose an open menu; clear search
EnterorSpace on a tool cardOpen its input and output

Accessibility

  • The sidebar is a labelled nav; the open chat has aria-current and unread chats say so.
  • Menus open from a trigger that reports aria-expanded; their items are menuitemradio and Escape shuts them.
  • Hairlines are separators with a value and arrow keys; skeletons are hidden from screen readers.

Responsive behaviour

  • Under 860 px of width the work area becomes a sheet opened from the top bar.
  • Under 640 px the sidebar slides in from the menu button and the composer drops its labels.
Edge cases (spec)

Every screen is authored on the 1440 × 900 stage (rule R1) and scaled to its column; the full view (/screens/<slug>/full) renders at the real viewport with the state bar under it (R2). Under 860 px of real width the work area becomes a sheet opened from the top bar; under 640 px the sidebar slides in from a menu button and the composer's approval and model chips drop their labels (icons stay). Every label in a row, chip or card title 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 ChatProgressScreen from oxyn_dioxus and include STATUS_INDICATOR_CSS plus the token stylesheet once.
  • A GPUI version exists: ChatProgressEl in oxyn_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.

Guides

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