claudeflow

claudeflow

A real Claude Code session is never one task. You start a feature, ask a side question mid-turn, leave a /loop watching a deploy and fan out three subagents to chase a bug, and it all lands in one interleaved transcript.

streams, the claudeflow mod, sorts that work into semantic streams as it happens and gives each one its own colour, status and history.

@image[01.jpg]

What it does

• Navigator pane: every stream beside the transcript, with its main turn and subagents, live status, what each is doing now, elapsed time, tool count and loop countdowns.
• Pill bar: one pill per stream above the prompt, coloured by health; number keys jump between them.
• Stream stripes: a thin pastel line down every prompt, reply and tool row. Focus a stream and the rest fold away.
• Semantic routing: structure first (subagents, loops, follow-ups, #tags), then one small Haiku call for anything new. Prompts sent mid-turn go to the right stream.
• History in parallel: existing sessions are filed into streams in the background.
• Updates without a restart: an update button appears when any installed plugin has a newer release.

The status card

Type status and a card opens above the prompt with every piece of work in the session: what is running, what is waiting for you, what failed and what is done, plus git state, tickets named in prompts and plan limits. It is answered locally, so it costs no model call and works while a turn is running.

@image[02.jpg]

On your phone

Driving Claude Code from the Claude app over Remote Control, streams opens as a touch accordion: one card per stream, what needs you first, and a one-tap yes for a stream waiting on your answer.

@image[03.jpg]

Install

claude plugin marketplace add macleodlabs-ai/claudeflow
claude plugin install streams@claudeflow