Skip to content

feat(cloud): verify Run on Cloud workflow handoffs - #1008

Closed
wealthwiselabs wants to merge 65 commits into
mainfrom
esun/feat/run-on-cloud-skill
Closed

wealthwiselabs wants to merge 65 commits into
mainfrom
esun/feat/run-on-cloud-skill

Conversation

@wealthwiselabs

@wealthwiselabs wealthwiselabs commented Oct 14, 2026 •

Copy link
Copy Markdown

Run on Cloud now checks whether the original workflow can run in the standard environment or an existing compatible Build before converting it or creating a custom environment. The handoff verifies required inputs, approved model bytes, an actual job, and the exact saved document and editor target before reporting success.

What changes

  • Adds the workflow-first Run on Cloud skill and inventory. Routing preserves original dependencies where supported, checks reusable Builds before conversion, distinguishes verified lossless changes from approved lossy changes, and supports new or specifically named updates. Workspace, costs, quotas, GPU/region and worker bounds remain explicit decisions.
  • Inventory separates dependency coverage from runtime input readiness, follows executable outputs and active subgraphs, retains uncertain identities, discovers effective Desktop model/input roots, and reports the complete deployment asset plan. Oversized optional responses remain unavailable evidence rather than partial success.
  • model upload previews the exact file/workspace/type, binds upload to the approved SHA256 and an immutable snapshot, checks destination collisions, and verifies returned identity/loader paths. Deduplication requires identical bytes already owned by the workspace; public visibility alone is insufficient. Existing Build/deployment uploads retain per-file approval, ledger and immediate byte/target rechecks. No universal upload manifest is introduced.
  • Read-only deploy ui verifies the current OAuth workspace, editor eligibility, ready deployment and served release. workflow ui --saved-file <saved_file_id> additionally verifies the exact authenticated userdata UUID/path/raw-content snapshot and publishes ?savedFile=<UUID> only when private_saved_file_links_enabled is literal true. Standard and custom environment selection remain explicit; discovery does not mutate compute.
  • Cloud save exposes the actual userdata saved_file_id separately from the mirrored record's workflow_id. Record UUIDs, matching names and equal content cannot certify file identity. Legacy positional/record links require regeneration. Older-server saves remain successful without a usable file ID; the skill reports verified sidebar/environment/API recovery without repeating saves or uploads.
  • Canvas validation follows the frontend's recursive schemas and WHATWG URL behavior, including supported legacy space/Unicode model URLs. UUID validation matches the pinned frontend consumer. Preflight retains whole-submitted-graph class checks while verifying private models on the execution graph. Build repair requires a supported installation mechanism before another paid cut and stops after the allowed repair attempts.
  • Desktop discovery requires direct endpoint and local process/filesystem provenance before deriving roots or an interpreter, including shared-filesystem/namespace and Windows path guards. which/env report the selected workspace separately from registry candidates. Auth/watch recovery preserves accepted job IDs, bounded retries and watch_auth_lost exit 75; recovery commands work outside Build-spec folders. Preview rendering, asset query encoding, prompt-template packaging and output sanitization are included.

Validation

  • Current head f2d3800f9d incorporates main bb1b6a6f43 through an ordinary merge. The changelog is the exact duplicate-free union of19old/9main/21merged entries, with the released suffix byte-identical to main. All772automatic paths remain exact. Five saved-file identity/skill/test files remain byte-identical to5317.
  • Auth composition preserves both contracts: an upload's expected sign-in is checked before refresh/clear or peer adoption, including under the shared lock; a late401 can adopt a same-account peer's newer token without spending its refresh token again. Both optional arguments are forwarded together. Account/workspace replacement, allow-clear behavior and watch-auth-lost handling remain intact. Root and fix(auth): coalesce peer refreshes and recover interrupted watches #1044 auth source bytes match; the new same-account peer regression passes, and dropping rejected-token forwarding is RED in the matched-source control.
  • All267upstream asset assertions and the branch tag-encoding case survive. Three initial failures were explicit test-double signature mismatches after composing the refresh API; adding the optional rejected-token argument to those stubs restores the owning232tests without changing assertions. A separate1pass/2fail control reproduces a new upload test binding a temporary resolver into lazy CLI modules; module-scoped fixture readiness materializes the actual declared command registry before the target mock, without invoking commands or callbacks. The same control then passes3/3. No runtime routing change, assertion/deadline/skip/baseline/CI-policy change or real installer/upload operation was used.
  • Fresh affected composition passes 3,390 tests, zero failures/skips, six deprecation warnings, in35.67seconds. It covers auth/credentials/token holders, mocked upload/storage/completion/polling/account replacement, build/deploy watchers, saved-file links and workflow UI, local transfer/assets routing and discovery. This is a scoped run, not a new whole-project result. Whole-tree Ruff lint/format, ADR, staged whitespace, normal native hooks and independent source/preservation review pass. The tested/reviewed tree c4d921cfd0 is preserved and the worktree is clean.
  • New hosted CI must validatef2d; no manual CI/CLA retry was requested. Earlier5317hosted completion and all older full-suite evidence keep their exact historical source attribution. Per-file skill upload approval and immediate bytes/destination recheck remain unchanged; generated opaque-ID consumer cleanup still waits for normal backend/types/frontend-main landing.

Historical5317 and earlier validation

  • Prior head 5317dc5bac incorporates main acfd665a99 through an ordinary merge. The only manual resolution is the changelog: its 19 pending entries are the exact duplicate-free union of the branch's 18 and main's seven, and the 1.24.0-and-older released suffix is byte-identical to main. All 776 other paths match Git's automatic merge result.
  • Fresh affected composition passed 5,371 tests, with three existing skips and 37 deprecation warnings, across 134 files: workflow/edit/CQL, build/inventory, models/download and all three knowledge modules. Incoming canonical-ID suggestions remain advisory; they do not auto-resolve, download or run a model. No real installer upgrade, E2E installation or live Cloud write was executed.
  • Whole-tree Ruff lint/format and ADR checks, normal native commit/push hooks, staged whitespace and independent merge-preservation review pass. The reviewed tree is unchanged after hooks. Dependencies and lockfiles are unchanged; validation uses the existing lock-matching packaging 25 environment.
  • Saved-file identity/UI helpers, both Run-on-Cloud skills and saved-link tests retain the previous head's exact bytes. Per-file upload approval and immediate byte/destination rechecks, refusal of unsafe deletes, literal CLI publication gates and all record/node/model identity rules remain intact. No test assertion, timeout, skip, baseline, trust, authorship or CLA policy changed.
  • Historical whole-suite results remain attributed to their actual source: fa4df716c7 passed 13,527 / 40 skips, and 2024c3ba94 passed 13,736 / 40 skips. The prior 7de6247 main composition passed 5,005 / three skips, with 2,487 feature checks at its recorded validation head. Those are historical records, not a whole-project rerun on 5317dc5bac. Existing coverage includes the 826 frontend canvas-consumer fixtures and 269 pinned frontend UUID cases; the fresh affected composition above validates this new merge.
  • Earlier test-only fixture corrections preserve valid workflow/JSON inputs, exact nonempty DER-root assertions, class-local no-network UI preflight isolation and the real resilient catalog-loader boundary. The changelog's actual saved_file_id versus nullable workflow-record identity warning remains preserved. Current-head hosted code checks have now completed successfully, including verified actual pytest and Windows/Linux/macOS E2E steps. The existing unsigned CLA check remains failed. No manual CI/CLA retry or identity-bound action was performed.

Prerequisites and rollout

Independently reviewable CLI prerequisites: #1043 Desktop discovery, #1044 auth/watch recovery, #1045 dry-run node pins, and #1046 normal sidebar saves. Their commits are integrated with regular merges; merging them first removes their corresponding diff here while preserving contributors.

Existing Cloud OAuth/editor-listing groundwork is Cloud #16318. Stable userdata identity/snapshot support is Cloud #17240, consumed with the matching frontend #21946. Advertise private_saved_file_links_enabled only after the matching backend and browser consumer are deployed. It gates CLI publication, not browser loading. This PR performs no production deployment, capability enablement or public workflow publishing.

Ordinary main merges through 7de6247 preserve the released changelog history and all branch-specific pending entries. Source-validation head: 1d6d3f5932. Fresh affected workflow/build/models/CQL/download validation passed 5,005 tests with three existing skips; feature-specific checks passed 2,487. Whole-tree Ruff lint/format, ADR checks, normal commit hooks and independent merge-preservation review passed.

The earlier full suite at 2024c3ba94 passed 13,736 tests with 40 existing skips. That result remains attributed to its recorded head; it was not rerun on the final main merge. The intervening test-only corrections use valid workflow fixtures and isolate mocked UI conversion/preflight from live catalog reads while retaining validation and assertions. The current affected composition and feature checks cover the final merge.

The changelog-only follow-up at c782f9f92c documents saved_file_id as the actual userdata identity, separate from workflow_id, and its nullable saved_file_identity_unavailable warning. All runtime and test bytes are identical to the source-validation head above; normal hooks and whitespace checks pass.

November 2 review follow-up verification

Fixed reactive OAuth peer adoption so recovery accepts only a different access token with known, unexpired expiry; otherwise it refreshes the current stored refresh token. Watch classification rereads credentials nonblocking after refresh-lock contention, retaining watch_auth_lost/75. Workflow association refusal guidance now asks users to verify name, content, and ownership before manual cleanup.

Validation: 3,616 affected tests passed (6 existing warnings), plus whole-tree Ruff lint/format and ADR checks. The shared auth/test bytes match the independently reviewed #1044 fix; its old-source controls fail six cases while five preservation controls pass. Account binding, default refresh/coalescing, the 90-second refresh budget, deletion policy, saved-file/skill contracts and CI policy are preserved. Normal commit hooks ran; this is scoped local validation, not a new whole-project or hosted result.

Add a default-installed comfy-run-on-cloud skill that takes one local
workflow onto Comfy Cloud: stock Cloud first, an existing workspace Build
next, and a workflow-scoped custom build only for what is left. It gates
every upload from disk on a per-file yes, and asks before freeing a
release, Build or deployment slot. A reference skill,
comfy-run-on-cloud-local-install, covers finding the install behind a
workflow, Comfy Desktop's split macOS layout included.

Add a hidden `comfy build inventory <workflow>` that reports what one
workflow loads (classes, recorded versions, models with subfolders,
embeddings, input files, muted nodes, implicit loaders), finds each model
across local model roots, joins a running ComfyUI's classes, and with
--cloud says whether stock Comfy Cloud runs it as-is, with dropdown
remaps, or needs a build. `comfy skills` ships only SKILL.md, so the
skill's inventory step has to be a command rather than a bundled script.
@coderabbitai

coderabbitai Bot commented Oct 14, 2026 •

Copy link
Copy Markdown

Review in Change Stack →

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review
Walkthrough

This PR adds Cloud model upload and workflow operations, workflow dependency inventory, and Comfy Desktop discovery. It also updates credential refresh and build/deployment watch handling, adds canvas validation, and adjusts several CLI behaviors.

Changes: Cloud model and workflow operations

Layer / File(s) Summary
Model upload and validation
comfy_cli/command/models/upload.py, comfy_cli/cloud_model_validation.py, comfy_cli/command/run/preflight.py, comfy_cli/command/workflow.py, comfy_cli/schemas/model_upload.json, tests/comfy_cli/command/test_model_upload.py, tests/comfy_cli/test_cloud_model_validation.py
Adds approved snapshot-based model uploads with digest, collision, ownership, and response checks. Cloud validation can verify exact private model assets missing from static enum data.
Saved workflows and UI links
comfy_cli/command/workflow.py, comfy_cli/command/workflow_ui.py, comfy_cli/command/deploy_ui.py, comfy_cli/comfy_client.py, comfy_cli/schemas/*ui.json, tests/comfy_cli/command/test_workflow_saved.py, tests/comfy_cli/command/test_workflow_ui.py, tests/comfy_cli/command/test_deploy_ui.py
Cloud saves write sidebar files and look up mirrored records. The new UI commands verify workflow or deployment data before returning editor links.
Canvas validation and Run-on-Cloud guidance
comfy_cli/cloud_workflow_schema.py, comfy_cli/schemas/cloud_workflow_*.json, comfy_cli/skills/comfy-run-on-cloud/*, comfy_cli/skills/comfy/SKILL.md, docs/adr/CLOUD-HANDOFF-0004-verify-upload-bytes-and-editor-identity.md, docs/cloud-model-import.md, docs/deployment-editor.md
Adds schema-based canvas validation and a frontend acceptance corpus. Adds Run-on-Cloud skills and documentation for model imports and editor links.

Workflow inventory and Desktop discovery

Layer / File(s) Summary
Workflow inventory and enrichment
comfy_cli/workflow_inventory.py, comfy_cli/command/build.py, comfy_cli/schemas/build_inventory.json, tests/comfy_cli/test_workflow_inventory*.py, tests/comfy_cli/command/test_build_inventory.py
Adds dependency reports for workflow classes, models, embeddings, inputs, and implicit dependencies. The command can join local files, server metadata, Cloud catalog data, Desktop roots, and deployment assets.
Desktop and workspace discovery
comfy_cli/desktop_install.py, comfy_cli/workspace_manager.py, comfy_cli/cmdline.py, comfy_cli/output/panels.py, comfy_cli/schemas/which.json, comfy_cli/schemas/env.json, tests/comfy_cli/test_desktop_install.py, tests/comfy_cli/test_which_desktop.py, docs/adr/DESKTOP-DISCOVERY-0005-preserve-runtime-path-identity.md
Adds read-only Desktop install detection and reports workspace existence, Desktop paths, model roots, and discovery warnings.

Authentication and build/deploy operations

Layer / File(s) Summary
Shared credential refresh and watch recovery
comfy_cli/cloud/oauth.py, comfy_cli/credentials.py, comfy_cli/builder_api.py, comfy_cli/command/build.py, comfy_cli/command/deploy_runtime.py, comfy_cli/error_codes.py, tests/comfy_cli/test_session_refresh.py, tests/comfy_cli/command/test_deploy_status.py, docs/json-output.md
Refresh requests can adopt a newer persisted token after a late 401. Build and deployment watches report watch_auth_lost when recovery fails while a refreshable sign-in remains stored.
Registry pins in build pushes
comfy_cli/command/build.py, comfy_cli/error_codes.py, tests/comfy_cli/command/test_build_push.py, tests/comfy_cli/command/test_build_auth_matrix.py, comfy_cli/skills/comfy-build/SKILL.md
Dry runs resolve public custom-node pins through the builder without uploading or saving. Real pushes use the same pin check.

CLI refinements

Layer / File(s) Summary
Workspace and command refinements
comfy_cli/agent/command.py, comfy_cli/command/assets_library.py, comfy_cli/command/build_validation.py, comfy_cli/command/preview.py, comfy_cli/error_codes.py, tests/comfy_cli/agent/test_command.py, tests/comfy_cli/command/test_assets_library.py, tests/comfy_cli/command/test_preview_bundled_regression.py
Updates CLI invocation detection, asset tag query encoding, local-path error text, and bundled FFmpeg handling. Supporting test updates cover these behaviors.

Estimated code review effort: 4 (Complex) | ~60 minutes

Change: Feature

Possibly related issues

  • Comfy-Org/comfy-cli#1070: Run-on-Cloud uses workflow conversion, and this issue reports that conversion can drop legacy proxyWidgets host values.
  • Comfy-Org/comfy-cli#1077: The PR uses the saved-workflow conversion contract for Cloud handoffs, which is also the conversion path tracked by this issue.
  • Comfy-Org/comfy-cli#873: The PR includes Cloud validation and handoff of converted workflows; this issue reports conversion failures for frontend-only nodes and positional widget values.
  • Comfy-Org/comfy-cli#893: The PR’s workflow conversion path is related to this issue’s reported slot and widget-value drift for newer frontend widget types.

Suggested reviewers: guill, vqt123

Merge Risk: Low · previous review 40d64

Inventory for a remote server can report unrelated local paths. Avoid relying on those paths until filesystem identity is verified.

Pre-merge checks: Passed 4 · Failed 1

Failed Failed checks: 1 warning

Check name Status Explanation Resolution
Architecture Decision Compliance Warning The prior architecture finding remains unresolved. Both new ADRs are still Proposed: CLOUD-HANDOFF-0004 and [DESKTOP-DI… Add and accept ADR coverage for the watch-auth recovery protocol, Builder reads during dry runs, and the inventory compatibility/readiness contract. Accept or explicitly supersede the Desktop discovery decision if it governs the new path-id…
Passed Passed checks: 4 passed
Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title clearly summarizes the primary change: verification of Run on Cloud workflow handoffs. It is concise, specific, and directly related to the pull request objectives.
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Architecture Decision Compliance

Explanation

The prior architecture finding remains unresolved. Both new ADRs are still Proposed: CLOUD-HANDOFF-0004 and DESKTOP-DISCOVERY-0005. The diff introduces durable contracts without accepted coverage: deploy_runtime.py:134-183,212-229 and cloud/oauth.py:761-875 define watch_auth_lost, shared-token adoption, one-retry recovery, and preserved sign-in behavior; command/build.py:1882-1910,2047-2054 makes push --dry-run perform an authenticated Builder snapshot read; and workflow_inventory.py:565-680 plus schemas/build_inventory.json:240-335 define compatibility, readiness, model-identity, and lossless-removal contracts. In addition, cloud_model_validation.py:94-150 removes selected unknown_enum_value errors and emits cloud_model_asset_verified, while Proposed CLOUD-HANDOFF-0004 rejects weakening unrelated CQL validation at lines 111-117 without defining an accepted scoped exception.

Resolution

Add and accept ADR coverage for the watch-auth recovery protocol, Builder reads during dry runs, and the inventory compatibility/readiness contract. Accept or explicitly supersede the Desktop discovery decision if it governs the new path-identity boundary. Amend CLOUD-HANDOFF-0004 to define and accept the scoped Cloud model-validation exception, or preserve the original unknown_enum_value diagnostic. Proposed ADRs do not replace accepted decisions.

Finishing Touches
Generate docstrings
  • Commit to this branch
  • Create a new PR
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

CodeRabbit Verify

  • Run CodeRabbit Verify to test the changes in this pull request.

The skill now converts a workflow for stock Cloud on its own only when the
conversion cannot change the output: the same file in another folder,
removing memory- or speed-only nodes, an exact core equivalent, or a
setting that reproduces the saved behavior. Any other change (a different
model, LoRA, upscaler or implementation, or Cloud's file under the user's
filename but with different weights) needs the user's yes, offered next to
a custom build as the exact alternative with its costs and the workspace
limits. A custom build asks whether to cover just the workflow or the whole
instance. Every converted copy is pre-flighted on the server, a deployment
counts as working only with a clean import log and a smoke run, and inputs
already on Cloud are not re-uploaded.

`comfy build inventory` reports the pieces this needs: memory-only nodes
Cloud lacks as `lossless_removable`, a size check of each local model
against Cloud's same-named file (`weights`), and with `--input-root` the
blake3-based name each input would have on Cloud and whether it is there.
Verdicts are now `covered`, `covered_after_lossless_fixes`,
`covered_needs_check` and `needs_build_or_lossy_conversion`.
…d-skill

# Conflicts:
#	CHANGELOG.md
#	comfy_cli/skills/__init__.py
… esun/feat/run-on-cloud-skill

# Conflicts:
#	CHANGELOG.md
…into esun/feat/run-on-cloud-skill

# Conflicts:
#	CHANGELOG.md
…into esun/feat/run-on-cloud-skill

# Conflicts:
#	CHANGELOG.md
#	comfy_cli/desktop_install.py
#	comfy_cli/schemas/env.json
#	comfy_cli/schemas/which.json
#	tests/comfy_cli/command/test_manager_gui.py
#	tests/comfy_cli/test_desktop_install.py
@github-actions

Copy link
Copy Markdown

🎉 Thank you for your contribution, we really appreciate it! 🎉

Like many open source projects, we require contributors to sign our Contributor License Agreement (CLA). A CLA makes the ownership of contributions explicit, so contributors and the project share a clear understanding of how the code can be used. By signing, you:

  • Confirm that you own your contribution.
  • Keep the right to reuse your own code.
  • Grant us a copyright license to include and share it within our projects.

CLAs are standard practice across major open source projects including those under the Apache Software Foundation and the Linux Foundation. Ours is based on the Apache Software Foundation's CLA. Most importantly, it would enable us to relicense the project under a more permissive license in the future, giving the project and its community greater flexibility.

✍ To sign, please post a new comment on this PR with exactly the following text: ✍


I have read and agree to the Contributor License Agreement


You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.

@skishore23 skishore23 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

KishoreBot (AI), reviewing at Kishore's request.

Reviewed commit 958ac1f49c0f00dacd785146e506b9f7ab1d8478 against base bb1b6a6f43be24e673d2211be1aa89820e450de3.

[P1] Integrated workflow deletion can remove a concurrent replacement.

comfy_cli/command/workflow.py:1642-1667 verifies a sidebar file/mirrored record and owner, then deletes the path without a server-enforced content/version condition. A concurrent same-name save after verification is deleted even though its bytes were never verified. The exact-head in-memory transport reproduction replaces the graph during the intervening user lookup; deletion exits 0 and removes the replacement. This is also reported on component PR #1046.

Please use conditional deletion bound to the verified identity/version, refuse without destructive cleanup on mismatch, and add the interleaving regression. If the API cannot provide this condition, do not automatically remove the sidebar file. A second GET only narrows the race.

The previous malformed-modelsDirs and bool/number identity findings are fixed. The integrated auth/watch and authenticated dry-run contracts also need ADR coverage under AGENTS.md/.agents/checks/adr-compliance.md: token-family ownership/adoption/retry/watch-state semantics and the public-only authenticated Builder read/no-upload/no-save boundary. Please record the decisions, or explain why they are local implementation details; the proposed handoff/Desktop ADRs do not document those contracts.

Validation: the review covered all 113 changed files, affected callers/tests and prior discussions. The review runner reports 2,238 focused tests passed (including installed-skill and schema-consumer coverage) plus ADR/Ruff checks, and reproduced the delete race at this head. I independently inspected the current delete sequence. No live Cloud/Desktop/upload acceptance is claimed. Current CI: 17 success, CodeRabbit skipped, cla-assistant failed. The contributor CLA remains a separate landing blocker.

vqt123 added a commit that referenced this pull request Nov 5, 2026
…y Cloud and hands back its link

Builds on #1008. The agent reads the workflow from the running local
server, checks it with `comfy workflow check --where cloud --models-dir`,
then runs it on Comfy Cloud, an existing build, a swapped copy or a
custom build. A model the check cannot prove the same runs on Cloud's
copy and is named in the report. It asks by name before every upload
and lossy swap: a model goes through `comfy model upload` after a dry
run, and a deployment run goes first with `--no-upload`, asks about the
files in details.missing[], then reruns with one `--allow-upload <hash>`
per approved file. It runs one real job and saves with
`comfy workflow save --where cloud`, ending with the folder link, or
says there is none for a record-only save.

comfy-build points a single-workflow request at the new skill,
comfy-build-failures says a missing import needs a way to install it
before another cut, and comfy-deploy and comfy-deploy-failures read a
deployment with `deploy show` outside a Build folder, since
`deploy status` needs one.
vqt123 added a commit that referenced this pull request Nov 5, 2026
…y Cloud and hands back its link

Builds on #1008. The agent reads the workflow from the running local
server, checks it with `comfy workflow check --where cloud --models-dir`,
then runs it on Comfy Cloud, an existing build, a swapped copy or a
custom build. A model the check cannot prove the same runs on Cloud's
copy and is named in the report. It asks by name before every upload
and lossy swap: a model goes through `comfy model upload` after a dry
run, and a deployment run goes first with `--no-upload`, asks about the
files in details.missing[], then reruns with one `--allow-upload <hash>`
per approved file. It runs one real job and saves with
`comfy workflow save --where cloud`, ending with the folder link, or
says there is none for a record-only save.

comfy-build points a single-workflow request at the new skill,
comfy-build-failures says a missing import needs a way to install it
before another cut, and comfy-deploy and comfy-deploy-failures read a
deployment with `deploy show` outside a Build folder, since
`deploy status` needs one.
vqt123 added a commit that referenced this pull request Nov 5, 2026
…y Cloud and hands back its link

Builds on #1008. The agent reads the workflow from the running local
server, checks it with `comfy workflow check --where cloud --models-dir`,
then runs it on Comfy Cloud, an existing build, a swapped copy or a
custom build. A model the check cannot prove the same runs on Cloud's
copy and is named in the report. It asks by name before every upload
and lossy swap: a model goes through `comfy model upload` after a dry
run, and a deployment run goes first with `--no-upload`, asks about the
files in details.missing[], then reruns with one `--allow-upload <hash>`
per approved file. It runs one real job and saves with
`comfy workflow save --where cloud`, ending with the folder link, or
says there is none for a record-only save.

comfy-build points a single-workflow request at the new skill,
comfy-build-failures says a missing import needs a way to install it
before another cut, and comfy-deploy and comfy-deploy-failures read a
deployment with `deploy show` outside a Build folder, since
`deploy status` needs one.
vqt123 added a commit that referenced this pull request Nov 5, 2026
…y Cloud and hands back its link

Builds on #1008. The agent reads the workflow from the running local
server, checks it with `comfy workflow check --where cloud --models-dir`,
then runs it on Comfy Cloud, an existing build, a swapped copy or a
custom build. A model the check cannot prove the same runs on Cloud's
copy and is named in the report. It asks by name before every upload
and lossy swap: a model goes through `comfy model upload` after a dry
run, and a deployment run goes first with `--no-upload`, asks about the
files in details.missing[], then reruns with one `--allow-upload <hash>`
per approved file. It runs one real job and saves with
`comfy workflow save --where cloud`, ending with the folder link, or
says there is none for a record-only save.

comfy-build points a single-workflow request at the new skill,
comfy-build-failures says a missing import needs a way to install it
before another cut, and comfy-deploy and comfy-deploy-failures read a
deployment with `deploy show` outside a Build folder, since
`deploy status` needs one.
vqt123 added a commit that referenced this pull request Nov 5, 2026
…y Cloud and hands back its link

Builds on #1008. The agent reads the workflow from the running local
server, checks it with `comfy workflow check --where cloud --models-dir`,
then runs it on Comfy Cloud, an existing build, a swapped copy or a
custom build. A model the check cannot prove the same runs on Cloud's
copy and is named in the report. It asks by name before every upload
and lossy swap: a model goes through `comfy model upload` after a dry
run, and a deployment run goes first with `--no-upload`, asks about the
files in details.missing[], then reruns with one `--allow-upload <hash>`
per approved file. It runs one real job and saves with
`comfy workflow save --where cloud`, ending with the folder link, or
says there is none for a record-only save.

comfy-build points a single-workflow request at the new skill,
comfy-build-failures says a missing import needs a way to install it
before another cut, and comfy-deploy and comfy-deploy-failures read a
deployment with `deploy show` outside a Build folder, since
`deploy status` needs one.
vqt123 added a commit that referenced this pull request Nov 5, 2026
…y Cloud and hands back its link

Builds on #1008. The agent reads the workflow from the running local
server, checks it with `comfy workflow check --where cloud --models-dir`,
then runs it on Comfy Cloud, an existing build, a swapped copy or a
custom build. A model the check cannot prove the same runs on Cloud's
copy and is named in the report. It asks by name before every upload
and lossy swap: a model goes through `comfy model upload` after a dry
run, and a deployment run goes first with `--no-upload`, asks about the
files in details.missing[], then reruns with one `--allow-upload <hash>`
per approved file. It runs one real job and saves with
`comfy workflow save --where cloud`, ending with the folder link, or
says there is none for a record-only save.

comfy-build points a single-workflow request at the new skill,
comfy-build-failures says a missing import needs a way to install it
before another cut, and comfy-deploy and comfy-deploy-failures read a
deployment with `deploy show` outside a Build folder, since
`deploy status` needs one.
@vqt123

vqt123 commented Nov 11, 2026

Copy link
Copy Markdown
Contributor

Closing: this was carried over in #1114, #1116, #1117 and #1118, merged 2026-11-05. The branch stays.

@vqt123 vqt123 closed this Nov 11, 2026
@github-actions github-actions Bot locked and limited conversation to collaborators Nov 11, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants