CC Workflow Studio

You think visually. AI thinks in .md. CC Workflow Studio speaks both.

Design workflows on a canvas. Export as Markdown your AI agent already understands. No more prompt-guessing.

Why CC Workflow Studio? - Speaker Deck Link

---

Supported Agents

Agent	Export Format	Requires
Claude Code	.claude/agents/ .claude/commands/	Claude Code
GitHub Copilot Chat	.github/prompts/	Copilot Chat
GitHub Copilot CLI	.github/skills/	Copilot CLI
OpenAI Codex CLI	.codex/skills/	Codex CLI
Zoo Code (formerly Roo Code)	.roo/skills/	Zoo Code
Gemini CLI	.gemini/skills/	Gemini CLI
Antigravity	.agent/skills/	Antigravity
Cursor	.cursor/agents/ .cursor/skills/	Cursor

Note: Agents other than Claude Code require activation from Toolbar's More menu.

---

Use it without VSCode, too

The VSCode extension is the most ergonomic editor, but it isn't the only entry point. The same workflow.json drives a CLI and an MCP server — pick whichever interface fits the situation.

flowchart LR
    Wf(["workflow.json"])

    subgraph IDE["🪟 VSCode Extension"]
        Canvas["React Flow canvas+ editor + Slack share"]
    end

    subgraph Mcp["🔌 MCP Server"]
        AIClient["Claude Code,MCP Inspector, ..."]
        McpServer["@cc-wf-studio/mcp(stdio: <code>ccwf-mcp</code>)"]
        AIClient --> McpServer
    end

    subgraph Cli["💻 CLI"]
        CliBin["@cc-wf-studio/cli(<code>ccwf render | validate | export | run | preview | canvas | mcp</code>)"]
    end

    Wf <-->|edit| Canvas
    Wf <-->|read / write| McpServer
    Wf <-->|read / write| CliBin

    Canvas -.->|writes skills + agents| Output["Agent skills on disk(.claude/, .codex/, .cursor/, ...)"]
    McpServer -.-> Output
    CliBin -.-> Output

Interface	Try it	Best for	Docs
VSCode extension	code --install-extension breaking-brake.cc-wf-studio	Designing workflows visually	packages/vscode
CLI (ccwf)	npx @cc-wf-studio/cli --help	Terminal / CI / SSH / Codespaces — render, validate, preview, export, run a workflow without VSCode	packages/cli
MCP server (ccwf-mcp)	Add to your MCP client's .mcp.json so Claude Code (or any MCP client) can read and edit workflows over stdio	Letting an external AI client read and edit your workflows through MCP tools	packages/mcp

There is no "VSCode-only" path: a workflow you draw in the canvas is the same file ccwf preview will render in a browser, and the same file an external Claude Code can edit through MCP.

---

✨ Edit with AI: AI agents (Claude Code, GitHub Copilot, etc.) create workflows through natural language via MCP Server

---

▶️ Run workflows directly from the editor – See your AI automation in action instantly

---

Key Features