RadarTopicsBuildersWeeklyReads
Open Source Radar
breaking-brake/

cc-wf-studio

GitHubWebsite

CC Workflow Studio is a TypeScript-based toolkit that provides a visual editor and CLI/MCP server integrations for designing AI agent workflows, exporting to Markdown, and running workflows from VS Code, CLI, or MCP clients.

5.3kstars
571forks
50issues
2025since
Star historydaily snapshots by VibeCrowd

Collecting history — the radar snapshots this repo daily. The trend line appears after 3 days of data (1 so far).

Alternatives & relatedmatched by topic overlap
Reviewgenerated from repository data · Aug 5, 2026

What it is

CC Workflow Studio is a visual workflow editor and supporting tooling to design AI agent orchestrations. It exports workflows as Markdown-compatible formats for use with AI agents and provides interfaces via a VSCode extension, CLI, and MCP server. Supported agents include Claude Code and several code/CLI-based agents; the project emphasizes visual design, per-node agent skills, and MCP integration.

How it works

The project provides a visual workflow canvas in the VSCode extension, with a CLI interface and an MCP server for editing and running workflows. Workflows are stored as JSON files on disk (e.g., .vscode/workflows/*.json) and can be exported to Markdown formats (e.g., a .md slash command or agent skill). The extension can edit workflows with AI via an Edit with AI flow, which can launch native AI editing through the MCP server. The system supports multiple agent types and corresponding skill/agent directories on disk (e.g., .claude/, .codex/, .cursor/). The README includes a Mermaid example showing the relationships between the VSCode extension, MCP server, and CLI.

Getting started

Install and run via the VSCode extension or CLI:

  • VSCode extension: code --install-extension breaking-brake.cc-wf-studio
  • CLI: npx @cc-wf-studio/cli --help The workflow workflow.json is saved under .vscode/workflows/ and can be exported to Markdown or run from the editor.

Recent releases

Latest releases include:

  • cc-wf-studio@3.36.0 (2026-07-11): Minor Changes, feature branchSession node type for Claude Code–only human-in-the-loop work
  • @cc-wf-studio/mcp@0.1.5 (2026-07-11): Patch Changes, updated dependencies to align with core changes
  • @cc-wf-studio/core@0.4.0 (2026-07-11): Minor Changes, feature branchSession node type
  • @cc-wf-studio/cli@0.2.2 (2026-07-11): Patch Changes, dependency updates to fix alerts and transitive deps
  • cc-wf-studio@3.35.1 (2026-06-14): Patch Changes, added zod-based, target-scoped node property schemas

Traction

This project has 5342 stars and 571 forks, with 50 open issues. It uses TypeScript and is licensed with no license listed in the repository metadata.

Behind the repo

Not provided in the material.

Caveats

License is listed as none; open issues count is 50. Created 2025-11-01; last push 2026-08-02. The README notes AGPL-3.0-or-later for the VSCode extension and MIT licenses for core libraries, but the repository license field shows none listed. The project is split into multiple packages (core, cli, mcp, vscode) with their own licenses.

Agent skills inside · 11
All skills →
pr-to-mainCreate a PR to the main branch for feature/fix changes in this pnpm + Changesets monorepo. Use when the user says "PRを作成", "mainにPR", or wants to submit changes for review. Always run this in the monorepo-aware way — identify the affected package(s) and make sure a changeset exists, because the release pipeline is Changesets-driven.Code Review & Qualityjira-driven-planningJiraチケットの要件とConfluenceの関連ドキュメントを基に、Frontend/Backend/Infrastructureに分割した実装計画を策定するプランニングスキル。Jiraチケット情報とConfluence検索結果が前段で取得済みであることを前提とし、構造化された実装計画を出力する。「プランニング」「実装計画策定」「タスク分割」などの文脈で使用。Frontendnext-qaRun one unattended iteration of the QUALITY-ASSURANCE loop — steward any in-flight QA PR, then build ONE queued `qa` issue (test infrastructure, unit tests, regression tests for known bugs) on a branch off auto-qa and open a PR that squash-merges on green CI. Adds tests and tooling only; never edits product source. Use when the user says "QAタスク", "next qa", "テストを進めて", or wants autonomous progress on the quality track.Testing & QAnext-taskRun one unattended IMPLEMENTATION iteration of the autonomous value-creation loop — steward any in-flight PR, fix interrupts (red CI / security / human bugs), or else build ONE queued `idea` issue on a branch off auto-dev and open a PR that squash-merges on green CI. Ideation lives in the next-idea skill; this skill consumes its queue. Use when the user says "次のタスク", "next task", "続きをやって", or wants autonomous progress without specifying what to do.Securitypr-to-main-cleanupClean up merged feature branches after PR to main is merged. Use when the user says "ブランチ削除", "cleanup", "マージ後の片付け", or wants to delete a merged branch.Otherworkflow-schema-tuningUse when modifying `resources/workflow-schema.json` in cc-wf-studio to influence how AI agents generate workflows via the cc-workflow-ai-editor skill. Triggers include "AIが特定のノードタイプを選んでくれない", "ワークフロー生成のバイアスを調整したい", "スキーマの description を変えたい", "新しいノードタイプを追加したい", "嘘の制約がスキーマに混じっていないか確認したい". Covers what the schema actually does (instructions to AI, not runtime constraints), the design philosophy (align direction, do not prescribe rules), the build pipeline (.json → .toon auto-generated), and known bias sources to audit.Security
SharePost on XLinkedIn
All trending reposRevenue-verified startups →