20:"$Sreact.view_transition" 21:I[9754,["/_next/static/chunks/2t36f5p4pjzlb.js","/_next/static/chunks/1gyqeidjm5eoa.js","/_next/static/chunks/0_fjnxc4tt_l_.js","/_next/static/chunks/1ymt1shyhmu-4.js","/_next/static/chunks/3kv2zf0i7s2wc.js","/_next/static/chunks/1vs_3g_g75zmk.js","/_next/static/chunks/2g4dh802s8oz3.js","/_next/static/chunks/1bc3f0shukf1j.js","/_next/static/chunks/192kgs9v_t14j.js","/_next/static/chunks/0z6pw0v5c_lx5.js","/_next/static/chunks/08r60e6icmtkc.js","/_next/static/chunks/3trx6c0i7_x-3.js","/_next/static/chunks/40sro5bzp9bi_.js","/_next/static/chunks/1wgf3tk38y6cf.js"],"ProjectDetail"] 22:T4216, VibeComfy — 让代理成为 ComfyUI 的一等公民

VibeComfy

一份工作流，同时活在两种语言里。

将 ComfyUI 工作流转为可编辑 Python 的库。

graph · ComfyUI JSON

LoadImage

CLIPTextEncode

KSampler

VAEDecode

SaveImage

source · editable Python

image = load_image(IMAGE) conditioning = clip_text(…) latent = ksampler(…) result = vae_decode(…) image.save()

同一节点标识，在两侧以相同强调呼应两侧是同一对象的两份并行表达，而非

01the two languages

同一个工作流的两种表达

一个 ComfyUI 工作流同时存在于两种语言里：右侧是你直接读写的图 JSON，左侧是可以编辑的 Python 源码。哪一边都不是唯一的“真相”，它们只是同一个对象的并行翻译。

VibeComfy 做的，就是把这两份表达保持同步——图里改了，代码跟着改；代码里改了，验证通过后再按原样编回队列所用的 API JSON。

# 一份工作流，两种语言，同一对象
graph         ↔   source

load          ↔   load_image(…)
encode        ↔   clip_text(…)
sample        ↔   ksampler(…)
decode        ↔   vae_decode(…)

02from graph to code

graph side

workflow fragment

"LoadImage": {
  "inputs": {
    "image": "photo.png"
  }
}

code side

def build():
    img = load_image(
        "photo.png"
    )

导入时，工作流被折叠为可编辑的 Python；你在这里改动，而图 JSON 保持为同源的对照。

03round-trip validation

验证通过，才走完一圈

编辑只是旅程的前半段。VibeComfy 验证你的 Python，再把代码编译回 ComfyUI 队列实际使用的 API JSON——只有验证通过，折返才是完整的。

一遍是从图到代码的折叠，一遍是从代码回到图的展开；验证是那道让折痕真正合上的门。

导入

把工作流读成可编辑的 Python，不再是不可直接操作的图 JSON。

编辑

在代码里改动节点与参数，保持与图一侧的对应关系。

验证

确认这份 Python 成立，再没有任何一边脱节。

编译回队列

导出成 ComfyUI 队列所使用的 API JSON，闭环完成。

04ready templates & CLI

现成模板，加上命令行

VibeComfy 在 ready_templates/ 里带上可直接使用的现成模板，例如 image/z_image。把它们复制到你自己本地的 recipes/ 工作区，就能开始编辑。

并且提供一套 CLI 命令，覆盖转换、验证与导出的完整流程。

port convert · 将工作流转为可编辑 Python validate · 验证你的 Python 成立 port export · 导出回队列所用的 API JSON

05agent in ComfyUI

让代理真正走进 ComfyUI

VibeComfy 提供 ComfyUI 扩展节点和编辑器内的代理面板，让轻量代理能直接读取、编辑并验证工作流，而不必直接操作图 JSON。

对代理开发者而言，这意味着工作流处理从“手工改一串嵌套的数据”变成了可以托管、验证和追踪的代码。

# 代理在编辑器内工作
# 轻量代理 → 读取 → 编辑 → 验证
ext.read(workflow)
ext.edit(patch)
ext.validate()  # 通过后编回队列

06license & start

从这里开始

适合想用代码方式管理 ComfyUI 工作流的开发者和代理集成场景。

—
ComfyUI 用户
需要先装好 ComfyUI 环境，模型文件也需自行下载。
—
代理开发者
在编辑器内用代码读取、编辑并验证工作流。
—
工作流自动化
文档可能仍不完整——当作探索的一部分。

github.com/peteromallet/VibeComfy → MIT · Python · agent first-class

本项目为嵌入式详情页，不搭建站内导航或个人信条；一切文字对应冻结事实。

23:T3e1c, VibeComfy — Making agents first-class in ComfyUI

VibeComfy

One workflow, living in two languages at once.

A library to turn ComfyUI workflows into editable Python.

graph · ComfyUI JSON

LoadImage

CLIPTextEncode

KSampler

VAEDecode

SaveImage

source · editable Python

image = load_image(IMAGE) conditioning = clip_text(…) latent = ksampler(…) result = vae_decode(…) image.save()

same node names, echoed in the same accent two parallel expressions of one object

01the two languages

The same workflow, expressed twice

A ComfyUI workflow exists in two languages at once: on the one hand the graph JSON you read and write, on the other an editable Python source. Neither side is the one true version — they are parallel translations of a single object.

VibeComfy keeps those two expressions in agreement. Change the graph and the code follows; change the code, and — once validated — it is compiled back into the API JSON that ComfyUI actually queues.

# one workflow, two languages, one object
graph         ↔   source

load          ↔   load_image(…)
encode        ↔   clip_text(…)
sample        ↔   ksampler(…)
decode        ↔   vae_decode(…)

02from graph to code

graph side

workflow fragment

"LoadImage": {
  "inputs": {
    "image": "photo.png"
  }
}

code side

def build():
    img = load_image(
        "photo.png"
    )

On import the workflow folds into editable Python; you change it there, while the graph JSON stays as the same-source counterpart.

03round-trip validation

The loop only closes when it validates

Editing is only the first half of the journey. VibeComfy validates your Python, then compiles it back into the API JSON that ComfyUI queues — only a passing validation completes the round trip.

One fold takes the graph to code; the other takes the code back to the graph. Validation is the seam where the fold truly snaps shut.

Import

Read a workflow as editable Python instead of an opaque graph JSON.

Edit

Change nodes and parameters in code, keeping the graph side in correspondence.

Validate

Confirm the Python holds, so neither side ever drifts.

Export to the queue

Compile back to the API JSON ComfyUI uses to run, closing the loop.

04ready templates & CLI

Ready templates, plus the command line

VibeComfy ships ready-to-use templates in ready_templates/, such as image/z_image. Copy them into your own local recipes/ workspace and start editing.

A set of CLI commands covers the whole route of converting, validating, and exporting.

port convert · turn a workflow into editable Python validate · check your Python holds port export · export back to the API JSON the queue runs

05agent in ComfyUI

Bring agents inside ComfyUI

VibeComfy ships ComfyUI extension nodes and an in-editor agent panel, so lightweight agents can read, edit, and validate workflows directly — without reaching into the graph JSON themselves.

For agent developers, this moves workflow work from hand-editing nested data into code that can be hosted, validated, and traced.

# an agent working inside the editor
# lightweight agent → read → edit → validate
ext.read(workflow)
ext.edit(patch)
ext.validate()  # then back to the queue

06license & start

Start here

For developers and agent integrations who want to manage their ComfyUI workflows in code.

—
ComfyUI users
You'll need a ComfyUI environment installed, and model files downloaded yourself.
—
Agent developers
Read, edit, and validate workflows in code from inside the editor.
—
Workflow automation
The docs may still be incomplete — treat that as part of the journey.

github.com/peteromallet/VibeComfy → MIT · Python · agent first-class

This is an embedded detail page — no site navigation or personal credo; every word maps to a frozen fact.

24:T4bd,The selected direction, 'The Bilingual Page', is the one that most directly expresses the project's verified mechanism: VibeComfy's defining act is representing one ComfyUI workflow simultaneously as graph JSON and as editable Python, then keeping the two in agreement through validation. A side-by-side correspondence of a graph fragment and its code, linked by matching tokens, is a derived relationship — not a marketing cliché and not a fake product screenshot. It best matches the primary evidence claims (import to editable Python; validate; compile back to API JSON), stays fully within the frozen facts (no fabricated metrics or media), degrades cleanly to 390px by collapsing the gutter into a horizontal correspondence bridge, and poses the lowest similarity risk to any generic landing page. The other two directions were strong but secondary: 'The Closing Loop' leads with a journey/timeline that is more expository than the object's core duality, and 'The Recipe Ledger' emphasizes the templates catalog, which is only one claim among several. Neither antiTemplateContext nor historicalSeed supplied competing fingerprints, so the bilingual-correspondence composition is unique and safe to freeze.a:[["$","$20",null,{"enter":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-enter","default":"none"},"exit":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-exit","default":"none"},"update":{"secondary-forward":"secondary-forward","secondary-back":"secondary-back-update","default":"none"},"default":"none","children":["$","$L21","cmt2zh28s01c86271cxojas0g:zh-CN:beautified",{"project":{"id":"cmt2zh28s01c86271cxojas0g","slug":"peteromallet-vibecomfy","name":"vibecomfy","description":"将 ComfyUI 工作流转为可编辑 Python 的库","authorName":"peteromallet","authorVerification":{"verified":false,"verifiedAt":null},"category":"development_tools","subcategory":"data_ai_tools","experienceUrl":null,"qualityScore":52,"featured":false,"officialSite":null,"views":{"original":{"available":true},"official":{"available":false,"reason":"disabled_by_policy"},"beautified":{"available":true,"reason":null},"defaultView":"beautified"},"beautifiedView":{"revisionId":"cmt2zh29f01ck62714ypg8ykh","kind":"artifact","artifact":{"schemaVersion":"localized-static-html-v4","kind":"static_html","locales":["zh-CN","en"],"defaultLocale":"zh-CN","documents":{"zh-CN":"$22","en":"$23"},"designDirections":{"schemaVersion":"dodot-design-directions-v1","directions":[{"id":"dir-bilingual-pane","name":"The Bilingual Page","projectMetaphor":"The same workflow exists in two languages at once: the ComfyUI graph JSON and the editable Python source. Neither side is the 'real' truth — they are parallel translations of one object, and VibeComfy keeps them in agreement.","signatureVisual":"A vertical dual-pane where the graph side and the code side face each other with a shared central gutter; matching node identifiers glow identically in both panes, so the reader's eye walks across the gutter and sees the one-to-one correspondence of a workflow fragment and its Python expression.","heroGeometry":"A strict 50/50 dialectic split; on the left a compact node network, on the right an aligned block of code, both locked to a common invisible baseline and linked by matching highlighted tokens and a thin connective gutter.","sectionSequence":["the-two-languages","from-graph-to-code","round-trip-validation","ready-templates-and-cli","agent-in-comfyui","license-and-start"],"surfaceModel":"Plane surfaces in pale paper tones with hairline rule dividers; each pane is a flat sheet, and authority moves from one sheet to the other by the matching-token emphasis. Depth only appears at the gutter, where the two sheets lean toward each other.","palette":"Warm paper off-white base, deep ink graphite text, one accent for graph-node identities (cobalt) and one for Python tokens (green), the two chromatic accents used only on the correspondence highlights.","typography":"A legible grotesque for body and a compact monospaced face for the code side and for all identifiers; heading treatment uses large mono-indexed labels to echo 'source' and 'graph' fields.","desktopComposition":"The hero is a true two-column translation view holding the full width; later sections alternate between full-bleed single sheets and narrow single-column proof passages. The gutter is a persistent vertical axis that recurs only in sections about translation.","mobileTransformation":"The two panes can no longer sit side by side; they stack, and the shared gutter becomes a horizontal bridge. The graph pane renders in a condensed single track above, the code pane below, and matching tokens are linked by the same accent so the correspondence survives the collapse.","mediaStrategy":"No media region: assetManifest is empty and no local image qualifies. The signature visual is itself the dual-pane translation diagram built from verified relationships (workflowFragment ↔ pythonExpression), not a screenshot.","forbiddenPatterns":["generic slogan above three metric cards","reusable feature-card wall","browser, terminal, or editor chrome shell","decorative gradient or glow used as skin","fake controls, tabs, or inputs"],"compositionFingerprint":"hero = two facing panes sharing a central matching-token gutter; persistent vertical axis; mono-indexed section labels."},{"id":"dir-roundtrip-loop","name":"The Closing Loop","projectMetaphor":"VibeComfy is a folding cycle: a workflow is folded into editable Python, held and edited, then folded back toward the graph — but the fold only closes and returns if it passes validation. The loop is the product.","signatureVisual":"A large bent arc that descends from graph iconography into code and curves back up toward the graph, left visually open; a validation gate sits at the join, and the open arc 'snaps shut' to signal a valid round trip.","heroGeometry":"A full-width bent-torque curve laid near the base of the hero, with the entry point (graph), the descent (import), the trough (editable Python), the rise (export), and the gate (validate) marked along its length — the motion of one object, not a static banner.","sectionSequence":["import-as-a-fold","edit-in-the-open","the-validation-gate","export-back-to-the-queue","ready-templates-workspace","cli-and-agents"],"surfaceModel":"A continuous flowing ribbon surface with a single seam at the validation gate; surfaces shade subtly along the fold direction to suggest physical bending. The gate is the only place with crisp edges.","palette":"Near-dark ink base so the ribbon reads as lit, a warm amber for the descending side and a cool teal for the rising side, meeting at a single white gate seam; foreground type in light paper tone.","typography":"Monospaced for all identifiers and command-oriented copy to reinforce the pipeline, with a rounded geometric face for short declarative headers that sit on the bends.","desktopComposition":"The hero curve occupies the lower third and reads left-to-right as a journey; sections follow the parabola locally — copy placed along the trough, the gate getting a full-width stop, then the rise to the CTA. Chronology IS the layout.","mobileTransformation":"The horizontal curve collapses into a vertical descending staircase of steps, each step one stage of the loop (import → edit → gate → export); the descending/rising color follows the staircase down and back up, and the gate becomes a full-width seam that requires intentional scrolling to cross.","mediaStrategy":"No media region: assetManifest is empty. The loop/staircase is a derived path diagram expressing the verified import-validate-export relationship; it does not impersonate a product screenshot.","forbiddenPatterns":["decorative motion or glow substituting for the fold idea","browser, terminal, or editor shell","three-parallel-card metric layout","feature-card wall","fake status, progress, or switch controls"],"compositionFingerprint":"hero = bent open arc with a gate seam marking a one-directional journey; chronology drives layout; the gate is the compositional hinge."},{"id":"dir-recipe-ledger","name":"The Recipe Ledger","projectMetaphor":"VibeComfy ships a catalog of ready templates you file into your own local recipes/ workspace and then make yours. The product is a filing system: copy a template out of the catalog, port it, and send it on its way.","signatureVisual":"An index ledger of typed rows, each row a filed template entry (its identifier, its source location like ready_templates/image/z_image, and its destination recipes/). Rows are aligned on a strict ruled grid, resembling a bibliographic index of workflows.","heroGeometry":"A ruled ledger grid occupying the hero center: several horizontal index rows of differing widths anchored to a strong left spine, the top row being the selected template, with provenance and destination stamped into the right cells.","sectionSequence":["a-catalog-of-templates","porting-a-template","import-to-editable-python","cli-commands","agents-inside-comfyui","make-it-your-own"],"surfaceModel":"A ruled ledger on a flat table surface — fine horizontal rules, generous leading, letterpress-style stamped emphasis; no floating shadows, no glass. Authority lives in alignment and ruled structure.","palette":"Structured cream paper with dark permanent-ink type; a single red-correction accent reserved for the destination/diff marking; neutral stone for secondary rules.","typography":"A highly legible text serif for the catalog rows and a slab/mono for filenames, paths, and template identifiers, creating an archive/bibliography register rather than marketing copy.","desktopComposition":"The ledger rules extend the full rendered width and persist across all sections; sections read as additional ledger folios (listings, an index of CLI usage, template entries). A continuous left spine with vertical ruling holds the page together as one register.","mobileTransformation":"The horizontal ledger rows narrow to their essential two cells — identifier and destination — and flow as a single justified ruled column; the left spine becomes a thin sticky vertical rule, preserving the register feel as rows stack edge to edge.","mediaStrategy":"No media region: assetManifest is empty. The ledger of template entries is a derived data-structured index of verified template/paths, not a screenshot or fake table of measurements.","forbiddenPatterns":["slogan-plus-three-metric-cards","card wall of identical features","browser or editor shell","glowing grid or particle backdrop","fake tabs, switches, or search"],"compositionFingerprint":"hero = ruled ledger grid with a strong left spine and stamped provenance/destination cells; continuous ruled register across every section; archive rather than landing page."}],"selectedDirectionId":"dir-bilingual-pane","selectionRationale":"$24"},"designBrief":{"schemaVersion":"dodot-design-brief-v1","selectedDirectionId":"dir-bilingual-pane","projectMetaphor":"The same workflow exists in two languages at once: the ComfyUI graph JSON and the editable Python source. Neither side is the 'real' truth — they are parallel translations of one object, and VibeComfy keeps them in agreement.","signatureVisual":"A vertical dual-pane where the graph side and the code side face each other with a shared central gutter; matching node identifiers glow identically in both panes, so the reader's eye walks across the gutter and sees the one-to-one correspondence of a workflow fragment and its Python expression.","compositionFingerprint":"hero = two facing panes sharing a central matching-token gutter; persistent vertical axis; mono-indexed section labels.","heroGeometry":"A strict 50/50 dialectic split; on the left a compact node network, on the right an aligned block of code, both locked to a common invisible baseline and linked by matching highlighted tokens and a thin connective gutter.","sectionSequence":["the-two-languages","from-graph-to-code","round-trip-validation","ready-templates-and-cli","agent-in-comfyui","license-and-start"],"surfaceModel":"Plane surfaces in pale paper tones with hairline rule dividers; each pane is a flat sheet, and authority moves from one sheet to the other by the matching-token emphasis. Depth only appears at the gutter, where the two sheets lean toward each other.","palette":"Warm paper off-white base, deep ink graphite text, one accent for graph-node identities (cobalt) and one for Python tokens (green), the two chromatic accents used only on the correspondence highlights.","typography":"A legible grotesque for body and a compact monospaced face for the code side and for all identifiers; heading treatment uses large mono-indexed labels to echo 'source' and 'graph' fields.","desktopComposition":"The hero is a true two-column translation view holding the full width; later sections alternate between full-bleed single sheets and narrow single-column proof passages. The gutter is a persistent vertical axis that recurs only in sections about translation.","mobileTransformation":"The two panes can no longer sit side by side; they stack, and the shared gutter becomes a horizontal bridge. The graph pane renders in a condensed single track above, the code pane below, and matching tokens are linked by the same accent so the correspondence survives the collapse.","mediaStrategy":"No media region: assetManifest is empty and no local image qualifies. The signature visual is itself the dual-pane translation diagram built from verified relationships (workflowFragment ↔ pythonExpression), not a screenshot.","evidencePlan":["Front-load the verified core claim: import ComfyUI workflows as editable Python, validate, and compile back to the API JSON ComfyUI queues — shown as the graph side and code side meeting at the gutter.","Ground 'ready-templates-and-cli' with only the frozen facts: ready_templates/ contains copying-ready templates such as image/z_image; CLI commands port convert, validate, and port export exist for converting, validating, and exporting workflows.","Ground 'agent-in-comfyui' with only the frozen fact that VibeComfy includes ComfyUI extension nodes and an in-editor agent panel letting agents edit workflows directly inside ComfyUI; never invent extra features, metrics, or testimonials.","Keep the bilingual correspondence strictly derived from verified relationships; do not fabricate a product screenshot, measurements, or third-party quotes anywhere."],"localeContract":{"zh-CN":"复制内容直接来自 material.json 的 localizations.zh-CN（slogan、oneLine、overview、highlights、bestFor、caveats）。slogan：让代理成为 ComfyUI 的一等公民；oneLine：将 ComfyUI 工作流转为可编辑 Python 的库。正文叙述保持自然中文密度，术语（ComfyUI、Python、CLI、ready_template、workflow）保留英文原词。证据型文字严格对应冻结事实，不补充规格、数字或评价。","en":"Copy follows material.json localizations.en directly (slogan, oneLine, overview, highlights, bestFor, caveats). slogan: Making agents first-class in ComfyUI; oneLine: A library to turn ComfyUI workflows into editable Python. Body copy keeps natural English; evidence-based text maps only to the frozen facts and adds no specifications, numbers, or testimonials."},"forbiddenPatterns":["generic slogan above exactly three metric cards","reusable feature-card wall that could accept any project's copy","browser, terminal, or editor chrome shell without direct project evidence","decorative gradient or glow skin used instead of a project-specific visual idea","fake controls, tabs, inputs, switches, charts, logos, or testimonials"]},"visualReview":{"schemaVersion":"dodot-automated-design-review-v1","status":"approved","summary":"Selects dir-bilingual-pane ('The Bilingual Page'): the hero is a true 50/50 dual-pane showing a ComfyUI graph fragment (left) and its editable Python expression (right) joined by a matching-token gutter with cobalt/green accents on flat paper sheets, directly embodying the project's graph-JSON-to-editable-Python duality. Six sections follow the brief's sequence exactly (the-two-languages, from-graph-to-code, round-trip-validation, ready-templates-and-cli, agent-in-comfyui, license-and-start). All copy maps to frozen facts in material.json with no fabricated metrics, testimonials, screenshots, or device shells; the signature visual is a derived diagram, not an asset. Mobile collapses the panes into a stacked column with a condensed graph track, preserving correspondence via shared accents. Locale parity is strong; two minor warnings flagged (the vertical gutter does not literalize the brief's 'horizontal bridge', and one zh-CN hero caption string ends on an incomplete fragment '而非').","checks":{"projectFit":{"passed":true,"evidence":"Hero implements a true 50/50 dialectic split: .pane.graph ('graph · ComfyUI JSON') on left faces .pane.code ('source · editable Python') on right inside a flat .pane-shell, with a thin connective .gutter (vertical color-fade line) and matching node/token identifiers (LoadImage/CLIPTextEncode/KSampler/VAEDecode/SaveImage vs image/conditioning/latent/result) highlighted in the two brief-specified accents -- --graph-accent cobalt --2456d0 and --python-accent green --1f7a4d. Section order (01-06) exactly matches design-brief sectionSequence. Persistent mono-indexed section labels and paper/hairline surface model follow the surfaceModel and typography specs."},"evidenceBound":{"passed":true,"evidence":"Every claim traces to material.json facts/claims and readme: import workflows as editable Python / validate / compile back to API JSON (claims 1, overview); ready_templates/ with image/z_image copyable to local recipes/ (claim 2); CLI commands 'port convert', 'validate', 'port export' (claim 4, sections 04 and round-trip steps); ComfyUI extension nodes + in-editor agent panel (claim 3, section 05); MIT license, Python language, and github.com/peteromallet/VibeComfy link (projection facts). slogan used in both (让代理成为 ComfyUI 的一等公民 / Making agents first-class in ComfyUI) and oneLine in hero. No fabricated specs, numbers, testimonials, or metrics are introduced."},"signatureVisual":{"passed":true,"evidence":"The dual-pane translation diagram is present and real in the hero source (no image asset): .pane-shell with .pane.graph + .gutter + .pane.code, matching tokens marked .tok.g/.tok.p. This is exactly the brief's mediaStrategy -- a derived diagram from verified relationships (workflowFragment -> pythonExpression), not a screenshot or fake product mock. assetManifest is empty and no local image is referenced, consistent with direction mediaStrategy."},"mobileTransformation":{"passed":true,"evidence":"@media (max-width:760px) re-composes the layout: .pane-shell{grid-template-columns:1fr} stacks graph pane above code pane, .pane.graph{border-right:none;border-bottom} and .pane.graph .pane-body{display:flex;flex-wrap:wrap} renders nodes as a condensed single track; .grid/.row-sheet/.proof collapse to 1fr, .proof .arrow is hidden, and hero min-height is released. Correspondence survives the collapse because the two accents and node/code pairing persist. Minor deviation from brief: the central .gutter remains a vertical line at left:50% instead of literalizing the specified 'horizontal bridge'."},"localeParity":{"passed":true,"evidence":"zh-CN.html and en.html are structurally parallel across all six sections with equivalent copy: hero h1/h2/one-line, the two prose paragraphs, the code proof blocks, CLI entries (port convert / validate / port export), agent code block, and BestFor/Caveats lists map 1:1. ComfyUI/Python/CLI terms retained in both. Caveats mirror material.json localizations.caveats. Minor copy blemish in zh-CN hero caption second string ends mid-clause ('一份并行表达，而非') trailing off, unlike the complete English 'two parallel expressions of one object'."},"antiTemplate":{"passed":true,"evidence":"No generic slogan-above-three-metric-cards layout; no reusable feature-card wall; no browser/terminal/editor chrome shell (distinct from the sanctioned dual-pane diagram); no decorative gradient/grid used as a skin -- the only gradients are the central gutter correspondence line and a subtle vertical hero wash, both serving the translation metaphor. No media region and no device shells are present."},"noFakeUi":{"passed":true,"evidence":"qa-report.json reports fakeControlCount:0, brokenImageCount:0, emptyLinkCount:0 for zh-CN and en at both desktop and mobile. Source review confirms no fake tabs, switches, inputs, search, charts, logs, or progress/status controls; the workflow fragment and code blocks are inert rendered text, and the repo link is a real href (https://github.com/peteromallet/VibeComfy)."}},"issues":[{"code":"mobile-gutter-not-horizontal-bridge","severity":"warning","locale":"all","description":"design-brief mobileTransformation specifies that the two panes stack and the shared central gutter becomes a horizontal bridge linking graph track and code track. The implemented mobile CSS collapses .pane-shell to a single column and reflows the graph body, but the .gutter div remains a vertical 1px fade line centered at left:50%, so the connective gutter does not literally transform into the horizontal correspondence bridge the brief describes.","repairInstruction":"In the max-width:760px block, restyle .gutter to a horizontal seam: set height:1px, width:100%, left:0, top:auto, and a horizontal left-to-right color fade, or replace it with a short horizontal connector between the stacked graph track and the code pane so the correspondence survives the collapse as a horizontal bridge."},{"code":"zh-hero-caption-incomplete-fragment","severity":"warning","locale":"zh-CN","description":"The hero .cap second string in zh-CN.html reads '两侧是同一对象的两份并行表达，而非' and ends on the coordinating particle '而非' (rather than ...) with nothing following, leaving an incomplete sentence. The English counterpart 'two parallel expressions of one object' is a complete, natural phrase, so the zh-CN caption should be a full sentence of equal completeness.","repairInstruction":"Complete the zh-CN cap sentence, e.g. replace '两侧是同一对象的两份并行表达，而非' with a self-contained clause such as '两侧是同一对象的两份并行表达，互为翻译' (or similarly natural full wording) so the caption reads as a complete sentence equivalent in meaning to the en caption."}]},"repairEvidence":[],"provenance":{"executor":"opencode","model":"deepseek/deepseek-v4-flash","opencodeVersion":"1.1.58","promptVersion":"dodot-showcase-deepseek-v4","inputHash":"c1277244e8393203d84390f7c3d5723decfec3a2e6e168c056d5c85d9fead6fb","artifactHash":"1572186333bdc330cdd6b5a34562bd745ec09d62046c88217c49a16640bab97e","designSkill":"dodot-showcase-design"},"qaEvidence":{"zh-CN":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":5,"sectionCount":6,"textLength":2037,"cjkCount":718,"latinLetterCount":766,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":4288,"h1Top":270.84375,"bottomInset":79.71875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"2a1ef023c4d9114492acbf1348b4d939a1bfe454b68dddc96b9d8247032beccb","middle":"2064862b61e21dce11652e69f9f484ad2e8755cd28536ef1c97b6dfb350b5a22","bottom":"806e5678940d1b629d61dc58b498d10508186744c447e08e3b83e0863a88bd92"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"zh-CN","h1Count":1,"h2Count":5,"sectionCount":6,"textLength":2037,"cjkCount":718,"latinLetterCount":766,"scrollWidth":390,"clientWidth":390,"scrollHeight":5344,"h1Top":147.09375,"bottomInset":80.03125,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"da79199e2cf559987b74d85155a986520052eaf509174e8074a32795b98774ed","middle":"dd37ec0af41f44a44f3769e638709af9aa0d77b1f7115bbe0bec3739fa54671a","bottom":"e9a2b07530826a2a5389a3fe088163b754d8adef9bf71ba2d8d473ff6bf6ecf6"},"consoleErrors":[],"networkRequests":[]}],"en":[{"viewport":"desktop","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":5,"sectionCount":6,"textLength":3724,"cjkCount":0,"latinLetterCount":2808,"scrollWidth":1280,"clientWidth":1280,"scrollHeight":4636,"h1Top":235.859375,"bottomInset":79.796875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"14828348ec43b1634c0d89b16334d86253c25dfa2a2b776a72e8d051486b3ec0","middle":"c2568551969ee33cb0c2e791fc4eb2fbac6206d06b0c84f853cd6bd5ba24031e","bottom":"c3c1680454c55789541fccfb70940dbf5851affb921285f02e6af7e3dcea9d29"},"consoleErrors":[],"networkRequests":[]},{"viewport":"mobile","passed":true,"localePassed":true,"metrics":{"language":"en","h1Count":1,"h2Count":5,"sectionCount":6,"textLength":3724,"cjkCount":0,"latinLetterCount":2808,"scrollWidth":390,"clientWidth":390,"scrollHeight":5857,"h1Top":147.09375,"bottomInset":79.796875,"brokenImageCount":0,"missingAltCount":0,"fakeControlCount":0,"emptyLinkCount":0},"screenshotHashes":{"top":"44ff05c3daad02149e855d32896cb6d0672bd94b80b2b787383d6e97fe96e837","middle":"8f976868912a3e682101746ef0c6afec8f05bf028ca9e51f7462a01b05b0e9fc","bottom":"3d9fa65bb78a61159b45d935c5829b1da72e108721e381ca375a0161131d292b"},"consoleErrors":[],"networkRequests":[]}]}},"generatorVersion":"opencode-1.1.58:deepseek/deepseek-v4-flash:dodot-showcase-deepseek-v4","publishedAt":"2026-08-20T08:29:45.622Z"},"rawExtraction":{"projectRevisionId":"cmt2zh29801ce6271b95qykja","projectVersion":1,"sources":[{"canonicalKey":"github:peteromallet/vibecomfy","role":"primary","revisionVersion":1,"url":"https://github.com/peteromallet/VibeComfy"}],"facts":[{"key":"repository_owner","value":"peteromallet","evidence":[{"path":"repository.owner","excerpt":"peteromallet"}]},{"key":"repository_name","value":"vibecomfy","evidence":[{"path":"repository.name","excerpt":"vibecomfy"}]},{"key":"description","value":"(empty)","evidence":[{"path":"repository.description","excerpt":"(empty)"}]},{"key":"primary_language","value":"Python","evidence":[{"path":"repository.language","excerpt":"Python"}]},{"key":"license","value":"MIT","evidence":[{"path":"repository.license","excerpt":"MIT"}]},{"key":"source_count","value":"1","evidence":[{"path":"projectRevision.sources","excerpt":"github:peteromallet/vibecomfy"}]}],"taxonomy":{"category":"development_tools","subcategory":"data_ai_tools","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"(empty)"}]},"lifecycle":{"stage":"active","confidence":0.75,"evidence":[{"path":"repository.pushedAt","excerpt":"2026-08-14T12:06:04.000Z"}]},"userIntents":[{"slug":"build_software","label":"构建或改进软件","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"(empty)"}]},{"slug":"automate_work","label":"自动化工作流程","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"(empty)"}]},{"slug":"create_content","label":"创作内容或设计","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"(empty)"}]},{"slug":"analyze_data","label":"分析与理解数据","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"(empty)"}]},{"slug":"learn_explore","label":"学习与探索","confidence":0.65,"evidence":[{"path":"repository.description","excerpt":"(empty)"}]}],"readme":{"headings":["VibeComfy: Making agents first-class citizens in the ComfyUI ecosystem","Abridged from ready_templates/image/z_image.py.","Getting Started","Use VibeComfy Inside ComfyUI","Practically this is how this looks","Advanced: nodes-only install (no agent panel)","macOS: expected console noise","`vibecomfy[comfy]` venv conflict","Use VibeComfy Directly","Architecture In One Pass","Templates And Porting","Deeper Docs","Repository Layout","Thanks","License"],"commands":["pip resolver conflict: `comfyui 0.26.0` wants `comfyui-frontend-package<1.46`"]},"changeSet":[{"field":"repository","beforeHash":"7ce1c75acdcb8b60b982844135dd3b6721285dad365fea06e55b63d0e83a3ae9","afterHash":"013627ea36ab934885a59a965503ebd0370ac28621eb79a68cf4bd97c45c2cb1"}]},"publishedAt":"2026-08-16T12:43:41.797Z","updatedAt":"2026-08-21T13:26:52.859Z","summary":{"id":"cmt2zh29b01cg6271mt8ddskx","projectType":"library","oneLine":"将 ComfyUI 工作流转为可编辑 Python 的库","overview":"VibeComfy 是一个 Python 库，将 ComfyUI 工作流导入为可编辑的 Python 代码，验证后编译回 API JSON。它提供现成模板、CLI 工具和 ComfyUI 扩展节点，让轻量级代理能直接读取、编辑和验证工作流，而无需直接操作图 JSON。适合希望用代码方式管理 ComfyUI 工作流的开发者和代理集成场景。","highlights":["工作流转 Python","现成模板","CLI 工具","ComfyUI 扩展"],"bestFor":["ComfyUI 用户","代理开发者","工作流自动化"],"caveats":["需要安装 ComfyUI 环境","模型文件需自行下载","文档可能不完整"],"categorySuggestion":"development_tools","subcategorySuggestion":"libraries_sdks","lifecycleStages":["frontend","backend_data"],"audienceIntents":["build","integrate","evaluate"],"confidence":0.7,"evidence":[{"claim":"VibeComfy 将 ComfyUI 工作流导入为可编辑的 Python，验证后编译回 ComfyUI 队列所需的 API JSON。","sourceType":"readme","locator":"https://github.com/peteromallet/VibeComfy"},{"claim":"提供 ready_templates/ 中的现成模板，例如 image/z_image，可复制到本地 recipes/ 工作区进行编辑。","sourceType":"readme","locator":"https://github.com/peteromallet/VibeComfy"},{"claim":"包含 ComfyUI 扩展节点和编辑器内代理面板，代理可直接在 ComfyUI 中编辑工作流。","sourceType":"readme","locator":"https://github.com/peteromallet/VibeComfy"},{"claim":"提供 CLI 命令，如 port convert、validate 和 port export，用于转换、验证和导出工作流。","sourceType":"readme","locator":"https://github.com/peteromallet/VibeComfy"}],"publishedAt":"2026-08-17T13:40:16.226Z"},"github":{"url":"https://github.com/peteromallet/VibeComfy","ownerAvatarUrl":"https://avatars.githubusercontent.com/u/4647941?v=4","starsCount":140,"forksCount":16,"language":"Python","syncedAt":"2026-08-17T13:37:02.562Z","license":"MIT","defaultBranch":"main","archived":false,"disabled":false,"lastChangedAt":"2026-08-14T12:06:04.000Z","missing":false},"tags":[],"updates":[]},"entryPoint":"discovery","claim":{"state":"unclaimed","verified":false},"initialView":"beautified","community":{"viewer":null,"state":{"likesCount":0,"creativeCount":0,"followersCount":0,"commentsCount":0,"liked":false,"creative":false,"followed":false},"comments":{"comments":[],"nextCursor":null}}}]}],"$L25"] </article></body></html>