Show HN: Visual composer for Claude Code multi-agent workflows A new visual desktop app called Claude Workflow Composer (CWC) allows Claude Code users to build multi-agent workflows by dragging agents onto a canvas, connecting them with handoff arrows, and exporting working agent files directly into their Claude installation — eliminating the need for manual YAML editing in .md files. The tool, which runs locally via npx and opens in a browser at localhost:3579, generates orchestrator skills and agent configuration files for the approximately 115,000 Claude Code users who currently hand-wire agent pipelines without visual representation or sharing capabilities. n8n for coding agent workflows. A visual desktop app for composing multi-agent Claude Code https://claude.ai/code workflows — drag agents onto a canvas, wire handoffs, attach skills, and export a working workflow directly into your Claude installation. No YAML editing required. Built for the ~115k Claude Code users who are hand-wiring agent pipelines in .md files and wondering why there's no better way. Building multi-agent workflows in Claude Code today means: - Hand-writing agent .md files with YAML frontmatter - Manually authoring orchestrator skills with disable-model-invocation: true and sequenced handoff prose - No visual representation of the pipeline before running it - No way to share a complete, working workflow with someone else - No way to discover what good pipelines look like The authoring experience is entirely text-based. You can't see what you're building until you run it. npx claude-cwc Opens a browser at http://localhost:3579 . No code signing, no Gatekeeper friction — paste it in a terminal and you're in. npx claude-cwc stop Stop the server Or from source: npm run build && npm start Drag agents onto a canvas → Connect them with handoff arrows author trigger conditions → Edit each agent's system prompt, tools, skills, and completion criteria → Preview every file that will be written before exporting → Export → writes agent .md files + orchestrator SKILL.md to ~/.claude/ → Invoke the workflow by name in Claude Code The exporter writes directly to ~/.claude/ user-scoped or .claude/ inside any project directory project-scoped, version-controllable . Conflict detection ensures it never touches files it doesn't own. Drag an existing agent from the sidebar ~/.claude/agents/ onto the canvas to create a reference node — it points to that agent file by slug rather than duplicating it. Drag from "New / Blank Agent" to create a bespoke node — the exporter generates a new agent file for it. Connect nodes by dragging between handles. Each connection becomes a handoff with a trigger description and optional context artifacts files, text, JSON passed between agents. Mark any node as a terminal Complete , Escalated , or Aborted to define workflow end states. Edit any node's completion criteria, tool access, skills, and system prompt in the Node Panel . The first node can also have a start trigger describing what initiates the workflow. Real-time validation surfaces duplicate slugs, empty names, disconnected nodes, and missing completion criteria immediately in the top bar — before you export. Click Export in the top bar. Choose a target directory ~/.claude/ or any project's .claude/ . Review a preview of every file that will be written. Confirm to write. The exporter: Bespoke nodes → writes an agent .md file with frontmatter name, description, color, model, tools , system prompt, completion criteria, skill references, and an ownership comment. Reference nodes → writes nothing — the exportedSlug is set to the existing agent's slug so the orchestrator routes to it directly. Workflow skill → generates an orchestrator skill at .claude/skills/