Ext Ops Panel
Open dashboard
Comparison

sessions-dashboard vs agent-flow

sessions-dashboard is a plugin bundle for AI coding tools published by channyzf6. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). agent-flow is a plugin bundle for AI coding tools published by Charles Tao. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-27. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacesessions-dashboardagent-flow
Claude Code: claude-plugins-community Listed
Version: 0.5.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Community marketplace charlie0113-t/claude-agent-flow Not listed Listed
Version: 0.1.0
Forks (GitHub): 5
Stars (GitHub): 26
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

sessions-dashboard vs agent-flow
Factsessions-dashboardagent-flow
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)26 (better)
Forks (GitHub) (differs)0 (worse)5 (better)
Last releaseNot publishedNot published
Where it runsInstalls as a plugin bundleInstalls as a plugin bundle
TransportNot statedNot stated
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Parts of the bundle (differs)1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/channyzf6/sessions-dashboardgithub.com/charlie0113-t/claude-agent-flow
Changes in the last 7 days00
First seen (differs)2026-10-112026-10-15

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

sessions-dashboard

In its own words, on Claude Code: claude-plugins-community:

Live browser dashboard of every CLI agent session you're running on one screen. See what each session is doing in real time, organize them into named groups that persist across restarts, and jump straight to a session's terminal in one click (macOS / Windows + WezTerm).

agent-flow

In its own words, on Community GitHub marketplaces:

/flow opens a live, read-only tree of the session's subagents and teammates beside the transcript: status, current tool call, waits for approval, elapsed time, tokens; prints the same tree as text where no pane can be drawn

How to run each

sessions-dashboard As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install sessions-dashboard@claude-community

agent-flow As a Claude Code plugin

Claude Code
/plugin marketplace add charlie0113-t/claude-agent-flow
/plugin install agent-flow@claude-agent-flow

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of agent-flow publish no settings it asks for, so we do not compare settings.

What it can do: sessions-dashboard · What it can do: agent-flow · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built