n8n for coding agent workflows. A visual desktop app for composing multi-agent Claude 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.

The Problem

Building multi-agent workflows in Claude Code today means:

1. Hand-writing agent .md files with YAML frontmatter
2. Manually authoring orchestrator skills with disable-model-invocation: true and sequenced handoff prose
3. No visual representation of the pipeline before running it
4. No way to share a complete, working workflow with someone else
5. 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.

Quick Start

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

How It Works

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.

Build

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.

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/<workflow-slug>/SKILL.md with disable-model-invocation: true. The orchestrator body is produced by BFS-traversing the node/edge graph into natural-language steps.
• Rename handling → if a node was renamed, the old owned file is deleted and the new one is written.
• Conflict detection → every file carries an ownership HTML comment. Before overwriting or deleting, the exporter verifies ownership — it never touches files created by other workflows or by hand.

Run

From any Claude Code session, invoke the workflow by its skill name:

/workflow-name

The orchestrator skill delegates every implementation step to sub-agents via the Agent tool. Each step references an agent by name; Claude Code resolves it to the agent's .md file and loads its system prompt, tools, and completion criteria.

Delete

POST /api/export/delete scans every exported file, checks its ownership comment, and only removes files owned by the current workflow. Reference nodes have nothing to delete — they didn't write any files.

Features

• Visual canvas — React Flow with background grid, minimap, zoom controls, and drag-to-connect
• Left sidebar — My Agents (searchable, draggable from ~/.claude/agents/) and Skills (searchable, draggable onto selected nodes)
• Right panels — Node Editor (name, description, criteria, tools, skills, system prompt, terminal type) and Edge Editor (trigger, label, context artifacts)
• Export modal — target selection, full file preview, warning display before writing anything
• Auto-save — 500ms debounced save to ~/.cwc/workflows/, no manual saving needed
• Recent files — home screen shows last 10 workflows, persisted to ~/.cwc/recents.json
• Markdown preview — click any agent or skill card to view its source file
• Open in editor — view any agent or skill file in your system editor
• Claude Code detection — warns on startup if ~/.claude/ is missing

Architecture

Client (React + React Flow)       Server (Express :3579)
┌─────────────────────────┐       ┌─────────────────────┐
│ TemplatePicker           │ ──►  │ /api/workflows      │
│ TopBar                   │ ◄──  │ /api/recents        │
│ Sidebar (Agents/Skills)  │ ──►  │ /api/agents         │
│ Canvas (React Flow)      │ ──►  │ /api/skills         │
│ NodePanel / EdgePanel    │ ──►  │ /api/export         │
│ ExportFlow (modal)       │ ──►  │ /api/export/preview │
│ useWorkflow (reducer)    │      │ /api/export/delete  │
│ useAutoSave (debounced)  │      │ /api/health         │
└─────────────────────────┘       └─────────────────────┘
                                          │
                                          ▼
Core Library                     ┌─────────────────────┐
                                  │ bfs.ts               │
                                  │ conflict-detector.ts │
                                  │ exporter.ts          │
                                  │ file-writer.ts       │
                                  │ prose-generator.ts   │
                                  │ skill-resolver.ts    │
                                  │ slugify.ts           │
                                  └─────────────────────┘

Storage:
  ~/.cwc/
    recents.json          Recent file paths (max 10)
    workflows/            Saved .cwc workflow files
    server.pid            PID of running server
  ~/.claude/
    agents/*.md           Agent definitions (read + written)
    skills/*/SKILL.md     User skills (read by sidebar)
    plugins/cache/...     Plugin skills (read by sidebar)

Key Concepts

Why Open Source

This tool has filesystem access to ~/.claude/. Open source is the trust model — no data leaves your machine, no cloud dependency. The local Node.js server is the entire backend. You can read every line of code that touches your files.

Development

npm run dev:server          # Watch-mode server compilation
npm run dev:client          # Vite dev server with HMR (port 5173, proxies /api to :3579)
npm test                    # Run all tests (Vitest)
npm run typecheck           # Type-check server + client
npm run build               # Production build (server + client)

Tests

89 tests across 16 files covering:

• BFS traversal: linear chains, back-edges, fan-out, multi-root, terminal edges
• Prose generation: start triggers, bold wrapping, context artifacts, Oxford comma, back-edge ordering
• File writer: frontmatter, skills block, ownership comments, workflow skill generation
• Exporter: full integration with real temp filesystem, rename cleanup, skill resolution, re-export, conflict warnings
• Validation: empty workflows, missing names, duplicate slugs, disconnected nodes
• Graph layout: horizontal spacing, fan-out vertical spacing, back-edge stability
• HTTP endpoints: all 12 API routes tested with real server instances
• Slugify: special chars, truncation, hyphen collapse, empty input
• Conflict detection: owned, foreign, absent, malformed states
• Skill resolution: namespaced (plugin) and non-namespaced (user) skill lookup

Contributing

PRs welcome. The codebase is TypeScript end-to-end (client + server + core library). Run npm test and npm run typecheck before submitting.

If you build a workflow you're proud of, share the .cwc file — that's how the community library grows.

License

MIT