Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

improvement: increase max node limit to 100 with user-configurable setting#678

Merged
breaking-brake merged 1 commit intomainbreaking-brake/cc-wf-studio:mainfrom
improvement/increase-node-limit-to-100breaking-brake/cc-wf-studio:improvement/increase-node-limit-to-100Copy head branch name to clipboard
Mar 23, 2026
Merged

improvement: increase max node limit to 100 with user-configurable setting#678
breaking-brake merged 1 commit intomainbreaking-brake/cc-wf-studio:mainfrom
improvement/increase-node-limit-to-100breaking-brake/cc-wf-studio:improvement/increase-node-limit-to-100Copy head branch name to clipboard

Conversation

@breaking-brake
Copy link
Copy Markdown
Owner

@breaking-brake breaking-brake commented Mar 23, 2026

Summary

Increase the workflow node limit from 50 to 100 (default) and expose it as a user-configurable VSCode setting (cc-wf-studio.workflow.maxNodes).

What Changed

Before

  • Workflow node limit was hardcoded to 50 in multiple places
  • Sub-Agent Flow node limit was hardcoded to 30
  • Users could not adjust the limit

After

  • Default node limit increased to 100 for both workflows and Sub-Agent Flows
  • New VSCode setting cc-wf-studio.workflow.maxNodes (range: 10-500, default: 100)
  • All hardcoded limits replaced with centralized getMaxNodes() utility function

Changes

  • package.json - Add cc-wf-studio.workflow.maxNodes configuration property
  • src/extension/services/workflow-settings-service.ts - New settings service with getMaxNodes()
  • src/shared/types/workflow-definition.ts - Update default constants to 100
  • src/extension/commands/save-workflow.ts - Use getMaxNodes() instead of hardcoded 50
  • src/extension/utils/validate-workflow.ts - Use getMaxNodes() instead of constant
  • src/extension/services/refinement-service.ts - Use getMaxNodes() instead of hardcoded 30
  • src/webview/src/services/workflow-service.ts - Use VALIDATION_RULES constant instead of hardcoded 50
  • resources/workflow-schema.json & .toon - Update all maxNodes values to 100

Testing

  • Manual E2E testing completed (boundary values: 99, 100, 101)
  • Build passes (npm run format && npm run lint && npm run check && npm run build)

🤖 Generated with Claude Code

Summary by CodeRabbit

  • New Features

    • Added a new configuration property to customize the maximum number of nodes allowed in workflows, with a default limit of 100 nodes.
  • Improvements

    • Increased the default maximum workflow nodes from 50 to 100.
    • Increased the default maximum sub-agent flow nodes from 30 to 100.
    • Workflow validation now dynamically enforces configured node limits.

…tting

- Add cc-wf-studio.workflow.maxNodes setting (default: 100, range: 10-500)
- Replace hardcoded node limits with centralized getMaxNodes() function
- Update schema files and validation rules to reflect new default

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Mar 23, 2026

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

This PR makes workflow node limits configurable via VSCode extension settings. It replaces hardcoded validation constants with a dynamic getMaxNodes() function, increases default limits (workflow: 50→100, sub-agent flow: 30→100), and adds configuration schema properties with customizable constraints.

Changes

Cohort / File(s) Summary
Configuration & Schema
package.json, resources/workflow-schema.json, resources/workflow-schema.toon
Added new extension configuration property cc-wf-studio.workflow.maxNodes with constraints (default 100, min 10, max 500). Increased workflow-level limit from 50 to 100 and sub-agent flow limit from 30 to 100 across all schema files.
Validation Rules
src/shared/types/workflow-definition.ts
Updated exported VALIDATION_RULES constants: workflow max nodes 50→100, sub-agent flow max nodes 30→100.
Configuration Service
src/extension/services/workflow-settings-service.ts
New module exporting getMaxNodes() function that reads VSCode configuration cc-wf-studio.workflow.maxNodes with fallback to base validation rules.
Validation & Command Logic
src/extension/commands/save-workflow.ts, src/extension/utils/validate-workflow.ts, src/webview/src/services/workflow-service.ts
Updated workflow validation to use dynamic getMaxNodes() instead of hardcoded limits; error messages now interpolate configured maximum values.
Refinement Service
src/extension/services/refinement-service.ts
Replaced hardcoded SUBAGENTFLOW_MAX_NODES constant with getMaxNodes() calls; updated refinement prompts and validation to use dynamic limits.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 Where once limits hardcoded in place,
Now config takes over with flexible grace!
Fifty to hundred, the nodes leap and bound,
Dynamic settings make magic abound,
A workflow set free by the settings we make,
Sweet configurability—for customization's sake! 🎛️

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and accurately summarizes the main change: increasing the max node limit to 100 and making it user-configurable, which aligns with all file modifications across the changeset.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch improvement/increase-node-limit-to-100

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@breaking-brake breaking-brake merged commit e4318db into main Mar 23, 2026
3 of 4 checks passed
@breaking-brake breaking-brake deleted the improvement/increase-node-limit-to-100 branch March 23, 2026 02:35
@breaking-brake breaking-brake mentioned this pull request Mar 23, 2026
braking-brake-semantic-release Bot pushed a commit that referenced this pull request Mar 23, 2026
## [3.30.3](v3.30.2...v3.30.3) (2026-03-23)

### Bug Fixes

* canvas toolbar toggles getting stuck open on rapid hover ([#679](#679)) ([7b42494](7b42494))

### Improvements

* add minimap 3-state display mode with scroll auto-show ([#677](#677)) ([fb26d73](fb26d73))
* add PulseMCP discovery link to MCP server selection ([#674](#674)) ([e6f2b6c](e6f2b6c))
* add SkillsMP discovery link to Skill Browser dialog ([#675](#675)) ([7638fdf](7638fdf))
* add sub-agent discovery link to Sub-Agent Creation dialog ([#676](#676)) ([3523da8](3523da8))
* increase max node limit to 100 with user-configurable setting ([#678](#678)) ([e4318db](e4318db))
@braking-brake-semantic-release
Copy link
Copy Markdown

🎉 This PR is included in version 3.30.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Morty Proxy This is a proxified and sanitized view of the page, visit original site.