AgentsFlow banner
pumanitro pumanitro

AgentsFlow

Design community

Description

Electron + Next.js desktop UI for Claude Code background agents — pinned to-do list, embedded xterm, git sidebar, image paste.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

Peers Flow

![Peers Flow — tracked peers, a rotating account pool with live plan-usage meters, and pinned conversations grouped under separators](./assets/screenshots/peers-flow.png)

Electron + Next.js desktop UI for **Claude Code's background agents** — track the sessions this app launches, treat them like a to-do list, inspect each one's working tree without leaving the window, and let your agents **delegate work to one another across directories**.

Status: early. Built against Claude Code CLI **v2.1.139+** (`claude agents` / `claude --bg`).

Why

Built to scratch four specific itches working with Claude Code day-to-day:

  1. Agent management in the CLI is ugly. claude agents is functional but unpleasant to live in — no real overview, no pinning, no per-directory grouping. Peers Flow turns background sessions into a visual to-do list scoped to the agents you launched from this app.
  2. No native Markdown editor. When an agent is working in a repo full of .md files, there's nowhere to read or edit them comfortably without alt-tabbing to another app. Peers Flow ships an Obsidian-style live Markdown editor inline, next to the chat.
  3. No tree preview. Watching agents touch a codebase is hard without seeing the working tree. Peers Flow shows a git status-colored file tree per session, with an embedded shell, so you can inspect changes the moment the agent finishes — no terminal-juggling.
  4. No communication between directory agents. Each claude session is an island — an agent in one directory can't ask one in another to do something, even when that other directory has exactly the skills or connections (a Slack login, a database) the task needs. Peers Flow makes every tracked directory a peer and hands agents a delegate tool, so one can pass a self-contained goal to another and rely on the result.

Highlights

  • Peers that delegate to each other (MCP) — every tracked directory is a peer: an agent rooted there with its own s