Skip to content
Back

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
MCP
Live
  1. You
    to Planner

    Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.

to everyone
Dioxus
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.

Terminal
cargo install --git https://github.com/ismailqureshi72/Oxyn oxyn-cli
oxyn init
oxyn add crew-chat
Rust
use 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

Dioxus · rust
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.

Live
  1. You
    to Planner

    Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.

to everyone
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.

  1. You
    to Planner

    Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.

  2. Planner started Analyst
  3. Planner
    to Analyst

    Find where new users drop off in the current guide.

  4. Analyst
    to Planner

    Step 4 loses a third of readers – the API key part. Notes are in .

  5. PlannerHandoff
    to Editor

    Rewrite steps 3–5 around the key; keep each under 60 words.

  6. Editor
    to Builder

    Draft is ready – can you wire the new screenshots in?

  7. BuilderNeeds you
    to 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?

  8. Planner
    to Everyone

    Steps 3–5 are rewritten and up for review on the preview build.

to everyone
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.

  1. You
    to Planner

    Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.

  2. Planner started Analyst
  3. Planner
    to Analyst

    Find where new users drop off in the current guide.

  4. Analyst
    to Planner

    Step 4 loses a third of readers – the API key part. Notes are in .

    Tool calls
    4
    Tokens
    18.2k
    Took
    3m 41s
  5. PlannerHandoff
    to Editor

    Rewrite steps 3–5 around the key; keep each under 60 words.

  6. Editor
    to Builder

    Draft is ready – can you wire the new screenshots in?

  7. BuilderNeeds you
    to 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?

  8. Planner
    to Everyone

    Steps 3–5 are rewritten and up for review on the preview build.

to everyone
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.

  1. You
    to Planner

    Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.

  2. Planner started Analyst
  3. Planner
    to Analyst

    Find where new users drop off in the current guide.

  4. Analyst
    to Planner

    Step 4 loses a third of readers – the API key part. Notes are in .

  5. PlannerHandoff
    to Editor

    Rewrite steps 3–5 around the key; keep each under 60 words.

  6. Editor
    to Builder

    Draft is ready – can you wire the new screenshots in?

  7. BuilderNeeds you
    to 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?

  8. Planner
    to Everyone

    Steps 3–5 are rewritten and up for review on the preview build.

to everyone
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.

  1. You
    to Planner

    Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.

  2. Planner started Analyst
  3. Planner
    to Analyst

    Find where new users drop off in the current guide.

  4. Analyst
    to Planner

    Step 4 loses a third of readers – the API key part. Notes are in .

  5. PlannerHandoff
    to Editor

    Rewrite steps 3–5 around the key; keep each under 60 words.

  6. Editor
    to Builder

    Draft is ready – can you wire the new screenshots in?

  7. BuilderNeeds you
    to 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?

  8. Planner
    to Everyone

    Steps 3–5 are rewritten and up for review on the preview build.

to everyone
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.

  1. You
    to Planner

    Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.

  2. Planner started Analyst
  3. Planner
    to Analyst

    Find where new users drop off in the current guide.

  4. Analyst
    to Planner

    Step 4 loses a third of readers – the API key part. Notes are in .

  5. PlannerHandoff
    to Editor

    Rewrite steps 3–5 around the key; keep each under 60 words.

  6. Editor
    to Builder

    Draft is ready – can you wire the new screenshots in?

  7. BuilderNeeds you
    to 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?

  8. Planner
    to Everyone

    Steps 3–5 are rewritten and up for review on the preview build.

  • AnalystGemini 3.8 Flash
  • EditorSonnet 5.5
  • PlannerGemini 3.8
  • BuilderOpus 5.5
to everyone
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.

  1. You
    to Planner

    Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.

  2. Planner started Analyst
  3. Planner
    to Analyst

    Find where new users drop off in the current guide.

  4. Analyst
    to Planner

    Step 4 loses a third of readers – the API key part. Notes are in .

  5. PlannerHandoff
    to Editor

    Rewrite steps 3–5 around the key; keep each under 60 words.

  6. Editor
    to Builder

    Draft is ready – can you wire the new screenshots in?

  7. BuilderNeeds you
    to 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?

  8. Planner
    to Everyone

    Steps 3–5 are rewritten and up for review on the preview build.

to everyone
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.

  1. You
    to Planner

    Refresh the onboarding docs by Thursday – shorter steps, one screenshot per step.

  2. Planner started Analyst
  3. Planner
    to Analyst

    Find where new users drop off in the current guide.

  4. Analyst
    to Planner

    Step 4 loses a third of readers – the API key part. Notes are in .

  5. PlannerHandoff
    to Editor

    Rewrite steps 3–5 around the key; keep each under 60 words.

  6. Editor
    to Builder

    Draft is ready – can you wire the new screenshots in?

  7. BuilderNeeds you
    to 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?

  8. Planner
    to Everyone

    Steps 3–5 are rewritten and up for review on the preview build.

to everyone
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

PropTypeDefaultDescription
agentsOption<Vec<StreamAgent>>Default::default()The agents (the demo's when `None`).
messagesOption<Vec<StreamMessage>>Default::default()Messages in the order they were sent (the demo's when `None`; then sent ones are kept).
liveboolDefault::default()The run is still going: a Live dot, and messages come in one by one (`step` ms apart).
stepu641_400Gap between messages while live, ms.
selectedStringDefault::default()A message picked from the start (its details open, the rest fade).
focus_agentStringDefault::default()An agent tab picked from the start.
previewOption<(String, usize)>Default::default()An attachment preview open from the start: (message id, chip index).
mention_openboolDefault::default()The @ list open from the start.
composerbooltrueShow the composer.
max_heightu32Default::default()The stream scrolls past this height (px); 0 lets it grow.
placeholderString"Write to the crew – type @ to pick an agent"The composer's placeholder.
titleString"Agent chat"Label of the stream for assistive tech.
nowrequiredClockMs—The clock.
styleStringDefault::default()`clean`, `classic`, or empty to follow `data-cstyle`.
on_selected_changeEventHandler<String>—A message was picked (id) or let go (empty).
on_focus_agent_changeEventHandler<String>—A tab was picked (agent id) or let go (empty).
on_sendEventHandler<(String, Vec<String>, Option<String>)>—Sent: (text, to – agent ids or `all`, reply_to).

Read from the Rust signature and doc comments.

Keyboard interactions

KeyAction
TabThe tabs are one stop, the stream another; then the focused message's Reply and chips, then the composer
← →orHome EndBetween the agent tabs
↑ ↓orHome EndBetween the messages
EnterorSpacePicks the focused message and opens its details, or lets it go
EscapeLets 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
EnterSends 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 CrewChat from oxyn_dioxus and include STATUS_INDICATOR_CSS plus the token stylesheet once.
  • A GPUI version exists: CrewChatEl 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