breaking-brake/cc-wf-studio

CC Workflow Studio

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 16 minutes ago
Added to GitGenius on September 12th, 2026
Created on November 1st, 2025
Open Issues & Pull Requests: 45 (+0)
GitHub issues: Enabled
Number of forks: 568
Total Stargazers: 5,379 (-1)
Total Subscribers: 19 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

CC Workflow Studio is a Visual Studio Code extension that lets developers design AI agent workflows visually on a canvas and export them as Markdown that AI agents can understand natively.

The tool solves the problem of translating visual workflow designs into formats that AI agents can execute. Instead of writing prompt specifications or guessing at the right structure, developers design workflows graphically and the tool exports them in the specific format each agent expects—whether that is Claude Code's agent directory structure, GitHub Copilot Chat prompts, or skill files for other platforms. This bridges the gap between how humans naturally think about workflows visually and how AI agents consume instructions through structured text files.

The extension supports a wide range of AI agents including Claude Code, GitHub Copilot Chat, GitHub Copilot CLI, OpenAI Codex CLI, Zoo Code, Gemini CLI, Antigravity, and Cursor, with each exporting to that agent's native format. Developers who work with multiple AI coding assistants will find the unified canvas approach valuable for avoiding repetitive manual formatting. The tool is not limited to the VSCode interface; the same workflow definitions can be driven through a command-line interface or an MCP server, allowing integration into different development environments and automation pipelines.

The project maintains active development across multiple distribution channels including the VS Code Marketplace and OpenVSX, with published packages for both CLI and MCP server implementations. Development activity shows sustained work on expanding agent support and maintaining compatibility across different platforms and interfaces.