CloudCC VS Code Extension
CloudCC VS Code extension for creating, pulling, and publishing common metadata (components, classes, triggers, schedules, and client scripts). It auto-syncs cloudcc-dev-skill by default.
Requirements
- VS Code
^1.95.0 (Cursor is also supported)
- Node.js 16+
- Install
cloudcc-cli globally (ensure cloudcc is in PATH to avoid confusion with the system C compiler cc). If MCP uses a separate entry, make sure that command is also available in PATH.
npm install -g cloudcc-cli
cloudcc -v
Feature Overview
- Quick right-click actions:
create / pull / publish
- Batch actions:
pull all / publish all (multi-select supported, up to 50 items)
- Entry-file publishing supports nested directories under
plugins, classes, triggers, schedule, script, and html (requires cloudcc-cli >= 2.5.5)
- Explorer folder creation writes directly below the selected nested resource folder (requires
cloudcc-cli >= 2.5.6)
- Component file Pull updates the selected nested entry directory, while folder Pull All writes directly below the selected Explorer folder (requires
cloudcc-cli >= 2.5.6)
- Auto-checks
cloudcc-cli availability on startup and shows guidance when needed
- Uses
cloudcc consistently for command execution (aligned with cloudcc-cli MCP cliRunner, avoiding accidental use of system cc)
- Added command:
Configure CloudCC Dev Skill (User) for manual user-level skill sync
- Auto-syncs
cloudcc-dev-skill on startup when the installed cloudcc-cli package contains this skill
Init Project command: verifies Node (node -v, minimum 14.19.0), then cloudcc-cli / cloudcc on PATH; skips cloudcc create project . if package.json already exists at the target root; otherwise runs it in the CloudCC terminal; then syncs cloudcc-dev-skill from the global cloudcc-cli package (same as Configure CloudCC Dev Skill)
- Explorer folder context menu: nested Create, Publish, Pull, and Init submenus (
explorerResourceIsFolder); Explorer file context keeps flat Publish/Pull entries when applicable (no submenus)
Common Commands
- Component:
cloudcc.createPlugin / cloudcc.pullComponent / cloudcc.publishPlugin
- Class:
cloudcc.createClass / cloudcc.pullClass / cloudcc.publishClass
- Trigger:
cloudcc.createTriggers / cloudcc.pullTriggers / cloudcc.publishTriggers
- Schedule:
cloudcc.createTimer / cloudcc.pullSchedule / cloudcc.publishTimer
- Client Script:
cloudcc.createScript / cloudcc.pullScript / cloudcc.publishScript
- HTML Component:
cloudcc.publishHtml / cloudcc.publishAllHtml
- Project:
cloudcc.initProject
- Skill configuration:
cloudcc.configureSkill
cloudcc-dev-skill Sync
The extension syncs cloudcc-dev-skill to all supported user-level skill locations:
~/.cursor/skills/cloudcc-dev-skill/
~/.copilot/skills/cloudcc-dev-skill/
~/.codex/skills/cloudcc-dev-skill/
~/.claude/skills/cloudcc-dev-skill/
On startup, it checks whether the globally installed cloudcc-cli package includes cloudcc-dev-skill:
- Included: auto-installs or updates based on
version / releaseDate in config.json.
- Not included: silently skips without affecting other commands.
Local Development
npm install
npm run compile
npm run watch
Package for release:
npx vsce package
Release Notes
Release v0.5.4
- Date: 2026-09-02
- Scope: Patch
- Iteration:
- Bumped the extension version to
0.5.4
- Fixed Windows
Pull All Components list loading when VS Code uses PowerShell but background commands run through cmd.exe
- Replaced shell-built background CloudCC commands with atomic argument arrays for components, classes, triggers, schedules, and client scripts
- Preserved workspace paths containing spaces and shell metacharacters without passing quote characters into the CLI
- Resolved Pull All commands against the Explorer item's workspace folder, including multi-root workspaces
- Made single-resource Pull commands switch to the owning workspace and quote resource paths for PowerShell and Command Prompt
- Launched the CloudCC Node entry directly on Windows to avoid
.cmd shim argument parsing differences
Release v0.5.3
- Date: 2026-09-02
- Scope: Patch
- Iteration:
- Bumped the extension version to
0.5.3
- Fixed component file Pull to pass the absolute
.vue entry and update its existing nested directory
- Fixed folder Pull All Components to use the selected Explorer folder as the target parent
- Prevented remote component paths from producing repeated category/component directory nesting
- Required
cloudcc-cli >= 2.5.6 for the new entry-file and target-directory component pull behavior
- Reused the existing
CloudCC terminal for publishing instead of creating a separate CloudCC Publish terminal
Release v0.5.2
- Date: 2026-09-02
- Scope: Full
- Iteration:
- Added nested-directory entry-file publishing under
plugins, classes, triggers, schedule, and script
- Added single and batch publishing for
html/**/index.html
- Switched publishing to absolute entry-file paths and shell-free CLI argument execution
- Added recursive batch discovery requiring a sibling
config.json, with deterministic entry selection
- Added a publish-only
cloudcc-cli >= 2.5.5 compatibility check without changing pull or sync flows
- Fixed CLI version detection when
cloudcc --version writes its version text to stderr
- Added a dedicated
CloudCC Publish integrated terminal with live ANSI-colored stdout/stderr for single and batch publishing
- Updated component, class, trigger, schedule, and client-script creation to pass the selected Explorer folder as an absolute
--target-dir
- Added a create-only
cloudcc-cli >= 2.5.6 compatibility check and preserved command-palette default-root behavior
- Fixed component file Pull to pass the absolute
.vue entry and update its existing nested directory
- Fixed folder Pull All Components to use the selected Explorer folder as the target and avoid repeated remote category paths
Release v0.5.1
- Date: 2026-04-10
- Scope: Patch
- Iteration:
- Bumped extension version to
0.5.1
- Tightened JavaScript and Java file context-menu
when conditions to match real path segments instead of broad substring patterns
- Fixed false-positive command visibility in projects whose root folder names contain words like
schedule, so class files only show class-related actions unless they are actually inside schedule/timer folders
Release v0.5.0
- Date: 2026-04-09
- Scope: Patch
- Iteration:
- Bumped extension version to
0.5.0
- Hardened
cloudcc-dev-skill sync to continue processing other target locations when one path fails
- Removed per-path warning popups for skill sync failures to reduce noisy notifications during startup and init flows
Release v0.4.9
- Date: 2026-04-09
- Scope: Full
- Iteration:
- Bumped extension version to
0.4.9
- Switched trigger creation (
cloudcc.createTriggers) back to integrated terminal command execution to match user shell runtime on Windows and avoid host-process command resolution failures
- Switched client script creation (
cloudcc.createScript) to the same terminal-based execution path for consistency with trigger creation behavior
- Wrapped encoded JSON payload with quotes in create commands so PowerShell/cmd keeps it as a single argument and prevents JSON parse errors caused by argument splitting
Release v0.4.8
- Date: 2026-04-08
- Scope: Full
- Iteration:
- Bumped extension version to
0.4.8
- Removed
Configure CloudCC Dev MCP from contributed menus/command list to keep the UI focused on CloudCC project workflows
- Expanded
cloudcc-dev-skill sync targets to cover all user-level skill directories: Cursor, Copilot, Codex, and Claude
Release v0.4.7
- Date: 2026-04-02
- Scope: Full
- Iteration:
- Bumped extension version to
0.4.7
- Added
homepage in package.json pointing to the CloudCC Help Center documentation for common developer tools
Release v0.4.6
- Date: 2026-04-02
- Scope: Full
- Iteration:
- Bumped extension version to
0.4.6
- Explorer context menus: folder selections use submenus Create, Publish, Pull, and Init; file selections show flat Publish/Pull commands only (no nesting)
Init Project: require Node >= 14.19.0 via node -v, then existing cloudcc-cli / cloudcc checks; if package.json exists at the target directory root, skip cloudcc create project . but continue; always run cloudcc-dev-skill sync from global cloudcc-cli after the checks (shared implementation with Configure CloudCC Dev Skill)
Release v0.4.5
- Date: 2026-04-02
- Scope: Full
- Iteration:
- Bumped extension version to
0.4.5
- Added
Init Project (cloudcc.initProject): opens the CloudCC terminal, changes to the target folder, and runs cloudcc create project . (Explorer folder right-click or Command Palette; multi-root workspaces prompt for a folder)
- Added Explorer folder menu entries for
Configure CloudCC Dev Skill (User) and Configure CloudCC MCP (Fallback) alongside Init Project, grouped after the main create/pull/publish items (cloudcc@2, explorerResourceIsFolder)
- Windows: folder
cd uses PowerShell Set-Location -LiteralPath when the integrated shell is PowerShell, and cd /d for cmd
Release v0.4.4
- Date: 2026-04-01
- Scope: Full
- Iteration:
- Bumped extension version to
0.4.4
- Updated the VS Code
cloudcc-dev-skill target path to ~/.copilot/skills/cloudcc-dev-skill/
- Synced documentation to reflect the new VS Code skill storage location
Release v0.4.3
- Date: 2026-04-01
- Scope: Full
- Iteration:
- Added
cloudcc-dev-skill auto-sync on extension activation as the default onboarding path
- Added
Configure CloudCC Dev Skill (User) command for manual skill installation/update
- Changed MCP setup to fallback mode with
Configure CloudCC MCP (Fallback) for manual configuration only
- Added version-aware skill update checks using
cloudcc-dev-skill/config.json (version, releaseDate)
- Added safe skip behavior when installed
cloudcc-cli does not include cloudcc-dev-skill
Release v0.4.2
- Date: 2026-04-01
- Scope: Full
- Iteration:
- Bumped extension version to
0.4.2
- Carried forward the unified
cloudcc command path and direct cloudcc --version availability check behavior introduced in v0.4.1
Release v0.4.1
- Date: 2026-04-01
- Scope: Full
- Iteration:
- Bumped extension version to
0.4.1
- Standardized CLI invocation to
cloudcc across platforms, removing the Windows-specific cloudcc.cmd branch
- Updated
cloudcc availability detection to execute cloudcc --version directly as the installation check
Release v0.4.0
- Date: 2026-04-01
- Scope: Full
- Iteration:
- Bumped extension version to
0.4.0
- Hardened
cloudcc availability checks to avoid false negatives across platforms by relying on command execution exit status
- Refined class creation flow to avoid duplicate installation failure popups when users choose upgrade/cancel actions
Release v0.3.9
- Date: 2026-04-01
- Scope: Full
- Iteration:
- Bumped extension version to
0.3.9
- Kept the startup auto-MCP bootstrap and CLI recovery notes from v0.3.8 as the current baseline behavior
Release v0.3.8
- Date: 2026-04-01
- Scope: Full
- Iteration:
- Added
onStartupFinished activation to run startup checks reliably after IDE launch
- Improved MCP bootstrap diagnostics: when
cloudcc exists but cc-mcp is missing in extension PATH, the extension now shows a clear guidance message
- When
cloudcc-cli is globally installed but cloudcc is missing, the extension now offers an in-app upgrade/reinstall action instead of only showing a warning
- Bumped extension version to
0.3.8
Release v0.3.7
- Date: 2026-04-01
- Scope: Full
- Iteration:
- Bumped extension version to
0.3.7
- Project convention: all entries under this
## Release Notes section (headings, dates, bullets) stay English-only when adding or editing
- Updated
cloudcc-extension-release-workflow skill to require English-only release notes and current env references (cloudcc, cc-mcp)
Release v0.3.6
- Date: 2026-04-01
- Scope: Full
- Iteration:
- Switched terminal and child-process CLI from
cc to cloudcc to match cloudcc-cli’s bin name and avoid clashing with the system C compiler
- Updated environment docs: verify install with
cloudcc -v; MCP still uses cc-mcp when configured separately
- Added
Configure CloudCC MCP (User) command for manual user-level MCP setup
- Automatically appends CloudCC MCP config on activation when
cc-mcp exists and the entry is missing
- Clearer
cloudcc-cli install checks and warnings when the package is global but cloudcc is not on PATH
Release v0.3.5
- Date: 2026-01-19
- Scope: Full
- Iteration:
- Cleaned up chat-related features and migrated them to cloudcc-cli MCP
- Added cloudcc-cli detection capability
Release v0.3.4
- Date: 2025-07-16
- Scope: Full
- Iteration:
- Added bulk publish support for triggers, schedules, scripts, and classes
Earlier releases are preserved in Git history.
Legacy Release History (Original)
ReleaseV0.3.5
Release Date: 2026-1-19
Release Scope: Full
Release Content
- Iteration
- Clean up chat-related features, migrate all to cloudcc-cli MCP
- Add cloudcc-cli detection feature
ReleaseV0.3.4
Release Date: 2025-7-16
Release Scope: Full
Release Content
- Iteration
- add publish all triggers
- add publish all timer
- add publish all script
- add publish all classes
- add publish all script
ReleaseV0.3.3
Release Date: 2025-7-7
Release Scope: Full
Release Content
- Iteration
- add pull all triggers
- add pull all timer
- add pull all script
ReleaseV0.3.2
Release Date: 2025-7-1
Release Scope: Full
Release Content
ReleaseV0.3.1
Release Date: 2025-4-2
Release Scope: Full
Release Content
- Iteration
- upload cloudccdev prompt
- script client delete all
- Improve startup speed
ReleaseV0.3.0
Release Date: 2025-3-7
Release Scope: Full
Release Content
- Iteration
- Add search progress prompt
ReleaseV0.2.9
Release Date: 2025-3-6
Release Scope: Full
Release Content
ReleaseV0.2.8
Release Date: 2025-3-6
Release Scope: Full
Release Content
ReleaseV0.2.7
Release Date: 2025-3-6
Release Scope: Full
Release Content
- Iteration
- Dynamically obtain object field information
ReleaseV0.2.6
Release Date: 2025-2-13
Release Scope: Full
Release Content
ReleaseV0.2.5
Release Date: 2025-2-13
Release Scope: Full
Release Content
ReleaseV0.2.4
Release Date: 2025-2-13
Release Scope: Full
Release Content
ReleaseV0.2.3
Release Date: 2025-2-12
Release Scope: Full
Release Content
ReleaseV0.2.2
Release Date: 2025-2-12
Release Scope: Full
Release Content
ReleaseV0.2.1
Release Date: 2025-2-11
Release Scope: Full
Release Content
ReleaseV0.2.0
Release Date: 2025-2-10
Release Scope: Full
Release Content
ReleaseV0.1.9
Release Date: 2025-2-8
Release Scope: Full
Release Content
ReleaseV0.1.8
Release Date: 2025-2-8
Release Scope: Full
Release Content
ReleaseV0.1.7
Release Date: 2025-2-5
Release Scope: Full
Release Content
- Iteration
- Adjusted object properties
ReleaseV0.1.6
Release Date: 2025-1-24
Release Scope: Full
Release Content
- Iteration
- Rollback production trigger timing folder function
ReleaseV0.1.4
Release Date: 2025-1-21
Release Scope: Full
Release Content
- Iteration
- Directory structure adjustment
ReleaseV0.1.3
Release Date: 2025-1-20
Release Scope: Full
Release Content
- Iteration
- Added directory layer for creating triggers and client scripts
ReleaseV0.1.2
Release Date: 2025-1-14
Release Scope: Full
Release Content
- Iteration
- Changed 'time' to 'schedule'
ReleaseV0.1.1
Release Date: 2025-1-10
Release Scope: Full
Release Content
- Iteration
- Added platform selection for client script creation
- Added right-click publish function for file editing
- Chinese to English translation
ReleaseV0.1.0
Release Date: 2025-1-9
Release Scope: Full
Release Content
ReleaseV0.0.9
Release Date: 2024-5-16
Release Scope: Full
Release Content
- Iteration
- Optimized trigger creation process
ReleaseV0.0.8
Release Date: 2024-5-14
Release Scope: Full
Release Content
- Iteration
- Adjusted publishing component logic
ReleaseV0.0.7
Release Date: 2024-5-11
Release Scope: Full
Release Content
- Iteration
- Removed script content from client scripts
ReleaseV0.0.6
Release Date: 2024-5-10
Release Scope: Full
Release Content
- Iteration
- Added client script publishing function
ReleaseV0.0.5
Release Date:
Release Scope: Full
Release Content
- Iteration
- Added trigger creation and publishing function
- Added timer creation and publishing function
- Added class creation and publishing function
- Added new component creation and publishing function
ReleaseV0.0.4
Release Date: 2023-09-20
Release Scope: Full
Release Content
- Optimization
- Upgraded compatibility with cloudcc-cli-1.5.1
- Added file creation function
ReleaseV0.0.3
Release Date: 2022-11-17
Release Scope: Full
Release Content
- Optimization
- Set VS version compatibility to 1.6.0
ReleaseV0.0.2
Release Date: 2022-11-17
Release Scope: Full
Release Content
ReleaseV0.0.1
Release Date: 2022-11-17
Release Scope: Full
Release Content
- Iteration
- Added component packaging and publishing function
| |