Merge ComfyUI-devtools and ComfyUI_frontend

[christian-byrne]

https://github.com/Comfy-Org/ComfyUI_devtools should be included in the ComfyUI_frontend as well since it is highly coupled with e2e testing in ComfyUI_frontend and there is no material benefit to it being split. The ability to have separate versioning has been a crutch rather than a benefit.

┆Issue is synchronized with this Notion page by Unito

[christian-byrne]

@snomiao Does this issue make sense or do you think I should provide more context? I want to avoid having this as a separate repo.

[snomiao]

let sno make draft pr for this issue， ctx is enough

[snomiao]

let sno make draft pr for this issue， ctx is enough

🔍 Investigation Steps

Phase 1: Repository Analysis

1. Analyze ComfyUI_frontend codebase structure and dependencies
2. Examine ComfyUI-devtools repository structure and functionality
3. Identify integration points and coupling between repos
4. Review e2e testing dependencies and patterns

Phase 2: Technical Assessment
5. Map shared dependencies and potential conflicts
6. Analyze build systems and tooling overlap
7. Identify migration requirements for devtools components
8. Assess impact on existing workflows and CI/CD

Phase 3: Implementation Planning
9. Design merge strategy and directory structure
10. Plan dependency consolidation approach
11. Create migration timeline and rollback strategy
12. Document breaking changes and upgrade path

Status: 🟡 In Progress | Agent: 159 | Branch: issue-4683-merge-comfyui-devtools-and-comfyuifrontend

[snomiao]

let sno make draft pr for this issue

🔍 Investigation Complete - Full Report

📋 Summary

Issue: Merge ComfyUI-devtools and ComfyUI_frontend
Assessment: ✅ FEASIBLE - The merge is technically straightforward and will eliminate unnecessary complexity

---

🔍 Technical Analysis

Current Architecture

ComfyUI_frontend (1.26.5):

• Full-featured frontend with Vue 3, TypeScript, Vite
• 131 dependencies, comprehensive testing suite
• Large codebase: ~40k+ files with sophisticated build system

ComfyUI_devtools (Small repo):

• Purpose: Developer testing tools (Custom Node)
• Size: 6 files, ~56KB total
• Core Components:
  • __init__.py - Server endpoints (/api/devtools/*)
  • dev_nodes.py - 15+ testing nodes
  • fake_model.safetensors - Test fixture

Integration Points Found

1. CI/CD Dependencies:

   • test-ui.yaml:33-38 - Auto-clones devtools for e2e tests
   • i18n-custom-nodes.yaml:35-39 - Translation workflow dependency

2. Runtime Dependencies:

   • ComfyPage.ts:208,255 - Uses /api/devtools/* endpoints
   • dialog.spec.ts:169 - References devtools repo in comments
   • browser_tests/README.md:19-20 - Setup documentation

---

🎯 Recommended Merge Strategy

Phase 1: Direct Integration

ComfyUI_frontend/
├── src/
│   └── devtools/           # NEW: Devtools functionality
│       ├── endpoints.py    # Server endpoints (from __init__.py)
│       ├── dev_nodes.py    # Development nodes
│       └── fixtures/       
│           └── fake_model.safetensors
├── browser_tests/          # EXISTING: Already uses devtools
└── package.json           # UPDATE: Add Python deps if needed

Phase 2: Integration Benefits

• Simplified CI/CD: Remove external repo checkout steps
• Version Consistency: Single release cycle
• Unified Development: Devtools evolve with frontend
• Reduced Maintenance: One less repo to manage

---

⚠️ Migration Considerations

Low Risk Items ✅

• File Size: Devtools is tiny (~56KB vs 40k+ files)
• No Version Conflicts: Simple Python files, no complex deps
• API Compatibility: Existing /api/devtools/* endpoints work as-is
• Test Dependencies: Already integrated in browser tests

Action Items

1. Move devtools files to src/devtools/ or tools/devtools/
2. Update CI workflows - remove external checkout steps
3. Update browser test docs - remove clone instructions
4. Add Python integration if needed (minimal)

---

📊 Impact Assessment

Benefits ✅

• Developer Experience: Single repo clone
• Maintenance: Unified release process
• CI/CD Efficiency: Faster builds (no external deps)
• Version Management: Consistent devtools-frontend compatibility

Risks ⚠️

• Minimal Migration Work: ~3-4 file moves + CI updates
• No Breaking Changes: Same API endpoints
• Backward Compatibility: Existing workflows unaffected

---

🚀 Implementation Plan

Effort: ~2-4 hours
Risk Level: Low
Breaking Changes: None

1. Create src/devtools/ directory structure
2. Move Python files from ComfyUI_devtools repo
3. Update CI workflows (remove checkout steps)
4. Update documentation
5. Test e2e workflows
6. Archive ComfyUI_devtools repo

Status: 🟢 READY FOR IMPLEMENTATION
Next Step: Create draft PR with file migration

---

Investigation by @snomiao on branch issue-4683-merge-comfyui-devtools-and-comfyuifrontend

[snomiao]

🔍 Investigation Started

I've started investigating your question/issue. Agent 12 is analyzing the codebase and will provide a detailed report soon.

• Agent ID: 12
• Status: Investigating
• Branch: issue-4683-merge-comfyui-devtools-and-comfyuifrontend

I'll update this comment with my findings once the investigation is complete.