Comfy dates the first commit to 16 January 2023 in its second-anniversary retrospective. Earlier experiments in October 2022 are described in the September 2025 funding post; they are not a January 2023 company-incorporation date. Company retrospective, 16 January 2025; company origin account, 16 September 2025. Project origins, company formation and financing announcements are distinct events.
This calendar represents all 45 months from January 2023 through September 2026. The first 30 entries use up to five end-of-month core-repository commits each, retrieved on 1 October 2026. They are selected evidence, not exhaustive release histories or monthly activity counts. The later 15 retain their published methods chapters and company-source commentary. Their different evidence types are deliberately labelled.
Repository record / 2023-01
January 2023: Graph primitives
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Save a small graph using the latent transform or advanced sampler you actually need. Retain its input dimensions and seed; node availability alone does not establish interchangeable outputs.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2023-02
February 2023: Memory and backend handling
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Distinguish CUDA and ROCm environments before investigating a memory failure. Record the installed backend and a failing workload instead of interpreting cache cleanup as extra physical VRAM.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2023-03
March 2023: Model patching and output history
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Compare a patched model with an unchanged baseline. Keep output-history records together with the graph and model revision so a saved image can be traced to its settings.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2023-04
April 2023: Conditioning and checkpoint defaults
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Make checkpoint fallback and conditioning weights explicit in a shared graph. A successful load through a default checkpoint is not evidence that the intended checkpoint was selected.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2023-05
May 2023: Custom-node registration
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Record node-pack revisions before changing registration code. Check how a missing extension is reported and retain a recoverable environment; this is a proposed check, not a security certification.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2023-06
June 2023: Model merging and loader caching
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Distinguish a cached model from a newly loaded revision when comparing outputs. Preserve merge settings and source-model terms; a merge feature does not grant permission to redistribute weights.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2023-07
July 2023: Latent output and execution resources
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Keep latent outputs and ordinary image files separately labelled. A downstream collaborator needs the correct decoder and graph context; a file saved successfully is not automatically a portable result.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2023-08
August 2023: Tiled decoding and controls
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Record tile settings, decoder revision and output dimensions when diagnosing memory pressure. Compare the complete delivered image rather than treating a lower-memory decode as an equivalent quality result.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2023-09
September 2023: Sampler and scheduler choices
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Freeze the sampler, scheduler, seed and step count as one condition. A newly available scheduler is a distinct experimental choice, not evidence of universal improvement over existing settings.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2023-10
October 2023: Attention and image quantisation
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Separate attention-memory handling from image-processing changes. Retain unsuccessful runs as well as outputs so a patch intended to recover a workload is not silently presented as a speed benchmark.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2023-11
November 2023: Grouped graphs and model recipes
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Check that grouped nodes retain understandable inputs and outputs when reopened. Use a documented model-specific recipe instead of assuming an SDXL Turbo workflow accepts ordinary sampling settings unchanged.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2023-12
December 2023: Validation and CPU decoding
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Exercise invalid node inputs before distributing a graph. If decoding runs on CPU, record that execution path alongside elapsed time; do not compare it with a GPU-only result without qualification.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-01
January 2024: Interface and group management
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Test an edited mask and grouped graph after saving and reopening. Pin the framework environment separately from interface preferences, because a frontend improvement does not establish backend compatibility.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-02
February 2024: Model-specific sampling
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Document the model and sampling configuration together. Support for a model family or continuous sampling path does not prove that a previously saved graph has the correct conditioning and settings.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-03
March 2024: Platform defaults and import diagnostics
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Keep platform-specific precision and extension-import logs with the workflow record. A changed default on one operating system must not be advertised as a universal accelerator improvement.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-04
April 2024: Upscale sampling and mask handling
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Keep mask batches, upscale settings and scheduler configuration in the same test record. Validate delivered dimensions and alignment; a sampler feature is not a substitute for checking the final composition.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-05
May 2024: Preview and upscaler dependencies
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Separate a preview from the exported deliverable and record the upscaler dependency. Inspect deterministic settings for the actual backend before treating visually similar previews as reproducible output.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-06
June 2024: Audio workflow records
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Retain an audio file's embedded workflow and inspect the exported file as well as its preview. Confirm the model licence and output format independently; an import feature does not establish commercial rights.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-07
July 2024: Text-encoder precision and memory
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Pin text-encoder precision and model identity alongside the GPU environment. Compare a fixed prompt and model revision before attributing a changed result to memory management alone.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-08
August 2024: Frontend transition and Flux
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Company announcement, 2024-08-06: The team announced Flux support, stable releases and a TypeScript frontend transition planned for 15 August. Its stated priorities were development speed and extension compatibility. The announcement's planned execution-inversion work is not treated as already released. Read the dated primary source.
Operator check, proposed: Keep interface and core revisions separately identifiable during the transition. Reopen a small extension-dependent graph before updating a production collection, and retain a rollback route.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-09
September 2024: Compilation and low-memory adapters
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Compare eager and compiled execution under the same environment and workload. Record adapter format and memory mode; compile-path fixes are not evidence that every custom extension is compatible.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-10
October 2024: Desktop and node compatibility
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Company announcement, 2024-10-21: The V1 announcement described a packaged Desktop experience and registry-based extension management. The desktop invitation was a closed beta, not proof of general availability or an independently verified security guarantee. Read the dated primary source.
Operator check, proposed: Treat desktop packaging, accelerator settings and individual node behaviour as separate acceptance checks. Preserve an exported workflow so a convenient installation route does not become the only recovery path.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-11
November 2024: Inpainting and video previews
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Inspect the actual inpaint or video deliverable, not only its preview. Experimental accelerator instructions remain conditional; retain device and framework versions when deciding whether they apply.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2024-12
December 2024: Sampler errors and extension contracts
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Keep a minimal failing graph when a sampler or custom node fails. Distinguish error handling and type-hint changes from a feature launch; a clearer failure is useful without implying a successful run.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2025-01
January 2025: Frontend and hardware guidance
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Company announcement, 2025-01-16: The second-anniversary post set out an operating-system-for-generative-AI ambition, with interface, team workflow and dependency-management priorities. This is a company strategy statement, not evidence that those priorities had all shipped. Read the dated primary source.
Operator check, proposed: Check new hardware instructions against the installed framework build before upgrading. Preview and batching changes need a saved acceptance example rather than an assumed speed or capacity increase.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2025-02
February 2025: Wan integration and precision modes
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Pin model revision, permitted inputs and precision when trying a video graph. An integration commit establishes repository work, not measured video quality, broad device support or a complete release census.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2025-03
March 2025: Video preprocessing and latent channels
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Preserve preprocessing settings and expected latent shape with the workflow. Compare the final sequence, including frame count and dimensions, before interpreting a successful graph execution as an equivalent result.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2025-04
April 2025: Offloading and update tests
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Keep an untouched environment before testing updater or offloading changes. Record model-loading and generation observations separately; an automated-test change does not certify every user's installation.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2025-05
May 2025: Templates and API paths
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Retain the template version and inspect API route handling in the actual deployment. Check a known input and failure response rather than assuming a template update is a backwards-compatible production interface.
Retrospective written 1 October 2026. Source-calendar entry.
Repository record / 2025-06
June 2025: Sampling optimisation and release process
Selected dated commits in the core repository document the following work. These are change records, not a claim that every change shipped in a stable release, passed a benchmark or reached all users.
Operator check, proposed: Compare an unchanged graph before and after an optimisation. Release-workflow edits and dependency updates are repository changes, not evidence of product adoption, revenue or a completed security review.
Retrospective written 1 October 2026. Source-calendar entry.