Crew chat
What agents say to each other – a quiet chat where every message shows who it is from and who it is for, handoffs and questions for you tagged, files as chips that open a preview, details under a message, and a composer that names agents with @.
oxyn add crew-chat- Youto Planner
Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
rsx! {
CrewChat {
agents: Some(run.agents()),
messages: Some(run.messages()),
live: run.is_live(),
now: clock.now(),
on_send: move |(text, to, reply_to)| run.post_from_you(text, to, reply_to),
}
}Rendered from Rust at build time · goes live when visible
When to use
- What agents say to each other: a quiet chat where every message shows who it is from and who it is for, handoffs and questions for you are tagged, files are chips that open a preview, a picked message shows its details, and a composer names agents with @ or answers a question.
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
Crew chat is free and MIT. The oxyn CLI copies its code, and the components it needs, into src/oxyn/ of your Dioxus or GPUI project, so it is yours to change.
cargo install --git https://github.com/ismailqureshi72/Oxyn oxyn-cli
oxyn init
oxyn add crew-chatuse crate::oxyn::{CrewChat, STATUS_INDICATOR_CSS};Rather depend on the crate? cargo add oxyn-dioxus oxyn-core --git https://github.com/ismailqureshi72/Oxyn, then use oxyn_dioxus::{CrewChat, STATUS_INDICATOR_CSS};
Usage
rsx! {
CrewChat {
agents: Some(run.agents()),
messages: Some(run.messages()),
live: run.is_live(),
now: clock.now(),
on_send: move |(text, to, reply_to)| run.post_from_you(text, to, reply_to),
}
}Examples
Live
The run comes in message by message – the sender's mark twinkles and Writing… shimmers first – with a Live dot.
- Youto Planner
Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
Code
rsx! {
CrewChat {
agents: Some(run.agents()),
messages: Some(run.messages()),
live: run.is_live(),
now: clock.now(),
on_send: move |(text, to, reply_to)| run.post_from_you(text, to, reply_to),
}
}Settled
The whole run: a quiet start line, an answer with its files, a handoff, and a question that needs you with Reply.
- Youto Planner
Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
- Planner started Analyst
- Plannerto Analyst
Find where new users drop off in the current guide.
- Analystto Planner
Step 4 loses a third of readers – the API key part. Notes are in Notion.
- PlannerHandoffto Editor
Rewrite steps 3–5 around the key; keep each under 60 words.
- Editorto Builder
Draft is ready – can you wire the new screenshots in?
- BuilderNeeds youto YouRefresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
The guide uses the old dashboard. Should the screenshots show the new one, or wait for its launch?
- Plannerto Everyone
Steps 3–5 are rewritten and up for review on the preview build.
Code
rsx! {
CrewChat {
agents: Some(run.agents()),
messages: Some(run.messages()),
live: run.is_live(),
now: clock.now(),
on_send: move |(text, to, reply_to)| run.post_from_you(text, to, reply_to),
}
}Details
A message picked: the rest fades and its details drop in under it.
- Youto Planner
Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
- Planner started Analyst
- Plannerto Analyst
Find where new users drop off in the current guide.
- Analystto Planner
Step 4 loses a third of readers – the API key part. Notes are in Notion.
- Tool calls
- 4
- Tokens
- 18.2k
- Took
- 3m 41s
- PlannerHandoffto Editor
Rewrite steps 3–5 around the key; keep each under 60 words.
- Editorto Builder
Draft is ready – can you wire the new screenshots in?
- BuilderNeeds youto YouRefresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
The guide uses the old dashboard. Should the screenshots show the new one, or wait for its launch?
- Plannerto Everyone
Steps 3–5 are rewritten and up for review on the preview build.
Code
rsx! {
CrewChat {
agents: Some(run.agents()),
messages: Some(run.messages()),
live: run.is_live(),
now: clock.now(),
on_send: move |(text, to, reply_to)| run.post_from_you(text, to, reply_to),
}
}Agent tab
An agent tab picked: only what it sent or got stays.
- Youto Planner
Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
- Planner started Analyst
- Plannerto Analyst
Find where new users drop off in the current guide.
- Analystto Planner
Step 4 loses a third of readers – the API key part. Notes are in Notion.
- PlannerHandoffto Editor
Rewrite steps 3–5 around the key; keep each under 60 words.
- Editorto Builder
Draft is ready – can you wire the new screenshots in?
- BuilderNeeds youto YouRefresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
The guide uses the old dashboard. Should the screenshots show the new one, or wait for its launch?
- Plannerto Everyone
Steps 3–5 are rewritten and up for review on the preview build.
Code
rsx! {
CrewChat {
agents: Some(run.agents()),
messages: Some(run.messages()),
live: run.is_live(),
now: clock.now(),
on_send: move |(text, to, reply_to)| run.post_from_you(text, to, reply_to),
}
}Attachment preview
A file chip opened: the preview window over the stream, Escape or × closes it.
- Youto Planner
Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
- Planner started Analyst
- Plannerto Analyst
Find where new users drop off in the current guide.
- Analystto Planner
Step 4 loses a third of readers – the API key part. Notes are in Notion.
- PlannerHandoffto Editor
Rewrite steps 3–5 around the key; keep each under 60 words.
- Editorto Builder
Draft is ready – can you wire the new screenshots in?
- BuilderNeeds youto YouRefresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
The guide uses the old dashboard. Should the screenshots show the new one, or wait for its launch?
- Plannerto Everyone
Steps 3–5 are rewritten and up for review on the preview build.
search("onboarding guide drop off") search("api key step completion") read(analytics/funnel.csv) read(notion: Docs research)
Code
rsx! {
CrewChat {
agents: Some(run.agents()),
messages: Some(run.messages()),
live: run.is_live(),
now: clock.now(),
on_send: move |(text, to, reply_to)| run.post_from_you(text, to, reply_to),
}
}Mention
@ in the composer: the agents with their models, arrows and Enter to name one.
- Youto Planner
Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
- Planner started Analyst
- Plannerto Analyst
Find where new users drop off in the current guide.
- Analystto Planner
Step 4 loses a third of readers – the API key part. Notes are in Notion.
- PlannerHandoffto Editor
Rewrite steps 3–5 around the key; keep each under 60 words.
- Editorto Builder
Draft is ready – can you wire the new screenshots in?
- BuilderNeeds youto YouRefresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
The guide uses the old dashboard. Should the screenshots show the new one, or wait for its launch?
- Plannerto Everyone
Steps 3–5 are rewritten and up for review on the preview build.
Code
rsx! {
CrewChat {
agents: Some(run.agents()),
messages: Some(run.messages()),
live: run.is_live(),
now: clock.now(),
on_send: move |(text, to, reply_to)| run.post_from_you(text, to, reply_to),
}
}Narrow
Narrow: bubbles wrap and the tabs scroll sideways.
- Youto Planner
Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
- Planner started Analyst
- Plannerto Analyst
Find where new users drop off in the current guide.
- Analystto Planner
Step 4 loses a third of readers – the API key part. Notes are in Notion.
- PlannerHandoffto Editor
Rewrite steps 3–5 around the key; keep each under 60 words.
- Editorto Builder
Draft is ready – can you wire the new screenshots in?
- BuilderNeeds youto YouRefresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
The guide uses the old dashboard. Should the screenshots show the new one, or wait for its launch?
- Plannerto Everyone
Steps 3–5 are rewritten and up for review on the preview build.
Code
rsx! {
CrewChat {
agents: Some(run.agents()),
messages: Some(run.messages()),
live: run.is_live(),
now: clock.now(),
on_send: move |(text, to, reply_to)| run.post_from_you(text, to, reply_to),
}
}Classic
Classic style: tabs in a grey strip, flat grey bubbles, a flat composer.
- Youto Planner
Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
- Planner started Analyst
- Plannerto Analyst
Find where new users drop off in the current guide.
- Analystto Planner
Step 4 loses a third of readers – the API key part. Notes are in Notion.
- PlannerHandoffto Editor
Rewrite steps 3–5 around the key; keep each under 60 words.
- Editorto Builder
Draft is ready – can you wire the new screenshots in?
- BuilderNeeds youto YouRefresh the onboarding docs by Thursday – shorter steps, one screenshot per step.
The guide uses the old dashboard. Should the screenshots show the new one, or wait for its launch?
- Plannerto Everyone
Steps 3–5 are rewritten and up for review on the preview build.
Code
rsx! {
CrewChat {
agents: Some(run.agents()),
messages: Some(run.messages()),
live: run.is_live(),
now: clock.now(),
on_send: move |(text, to, reply_to)| run.post_from_you(text, to, reply_to),
}
}API reference
CrewChat
| Prop | Type | Default | Description |
|---|---|---|---|
agents | Option<Vec<StreamAgent>> | Default::default() | The agents (the demo's when `None`). |
messages | Option<Vec<StreamMessage>> | Default::default() | Messages in the order they were sent (the demo's when `None`; then sent ones are kept). |
live | bool | Default::default() | The run is still going: a Live dot, and messages come in one by one (`step` ms apart). |
step | u64 | 1_400 | Gap between messages while live, ms. |
selected | String | Default::default() | A message picked from the start (its details open, the rest fade). |
focus_agent | String | Default::default() | An agent tab picked from the start. |
preview | Option<(String, usize)> | Default::default() | An attachment preview open from the start: (message id, chip index). |
mention_open | bool | Default::default() | The @ list open from the start. |
composer | bool | true | Show the composer. |
max_height | u32 | Default::default() | The stream scrolls past this height (px); 0 lets it grow. |
placeholder | String | "Write to the crew – type @ to pick an agent" | The composer's placeholder. |
title | String | "Agent chat" | Label of the stream for assistive tech. |
nowrequired | ClockMs | — | The clock. |
style | String | Default::default() | `clean`, `classic`, or empty to follow `data-cstyle`. |
on_selected_change | EventHandler<String> | — | A message was picked (id) or let go (empty). |
on_focus_agent_change | EventHandler<String> | — | A tab was picked (agent id) or let go (empty). |
on_send | EventHandler<(String, Vec<String>, Option<String>)> | — | Sent: (text, to – agent ids or `all`, reply_to). |
Read from the Rust signature and doc comments.
Keyboard interactions
| Key | Action |
|---|---|
| Tab | The tabs are one stop, the stream another; then the focused message's Reply and chips, then the composer |
| ← →orHome End | Between the agent tabs |
| ↑ ↓orHome End | Between the messages |
| EnterorSpace | Picks the focused message and opens its details, or lets it go |
| Escape | Lets go of the message or tab; drops the reply; closes the preview |
| @ | Opens the agents in the composer – type to filter, arrows, Enter or Tab to name one |
| Enter | Sends from the composer; Shift+Enter starts a new line |
Accessibility
- A polite live log; each message is named by author, recipient, time and content.
- Roving focus: one message and one tab are in the tab order; tabs are toggle buttons with aria-pressed in a labelled toolbar.
- The @ list is a listbox tied to the field with aria-expanded; the preview is a modal dialog that hands focus back to its chip.
- Needs you and Handoff are words, not just colours; pixel marks and logos are hidden from assistive tech.
Responsive behaviour
- 760 px up to its container; bubbles hug their words up to 560 px.
- Under 520 px the gutters shrink; the tabs scroll sideways with a fade at the edge; the preview fits the component.
Edge cases (spec)
760 px up to its container; under 520 px the gutters shrink; the tabs scroll sideways with an edge fade.
Notes for AI
- Import
CrewChatfromoxyn_dioxusand includeSTATUS_INDICATOR_CSSplus the token stylesheet once. - A GPUI version exists:
CrewChatElinoxyn_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.