{"id":25208062,"url":"https://github.com/comfy-org/rfcs","last_synced_at":"2026-02-03T06:03:29.243Z","repository":{"id":270750045,"uuid":"911346688","full_name":"Comfy-Org/rfcs","owner":"Comfy-Org","description":"RFCs for substantial changes to ComfyUI core, APIs, or standards.","archived":false,"fork":false,"pushed_at":"2025-06-17T17:04:34.000Z","size":113,"stargazers_count":30,"open_issues_count":4,"forks_count":6,"subscribers_count":8,"default_branch":"main","last_synced_at":"2025-07-03T21:47:34.858Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"","language":"Python","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Comfy-Org.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2025-01-02T19:56:44.000Z","updated_at":"2025-06-30T18:50:47.000Z","dependencies_parsed_at":"2025-02-04T04:19:04.114Z","dependency_job_id":"f5975574-5f9d-420e-88a2-651b70882eba","html_url":"https://github.com/Comfy-Org/rfcs","commit_stats":null,"previous_names":["comfy-org/rfcs"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/Comfy-Org/rfcs","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Comfy-Org%2Frfcs","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Comfy-Org%2Frfcs/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Comfy-Org%2Frfcs/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Comfy-Org%2Frfcs/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Comfy-Org","download_url":"https://codeload.github.com/Comfy-Org/rfcs/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Comfy-Org%2Frfcs/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":286080680,"owners_count":29035273,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-02-03T02:28:16.591Z","status":"ssl_error","status_checked_at":"2026-02-03T02:27:48.904Z","response_time":96,"last_error":"SSL_connect returned=1 errno=0 peeraddr=140.82.121.5:443 state=error: unexpected eof while reading","robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":false,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-02-10T12:18:35.663Z","updated_at":"2026-02-03T06:03:29.229Z","avatar_url":"https://github.com/Comfy-Org.png","language":"Python","funding_links":[],"categories":[],"sub_categories":[],"readme":"# rfcs\nRFCs for substantial changes to ComfyUI core, APIs, and standards.\n\n## What is an RFC?\n\nThe \"RFC\" (request for comments) process is intended to provide a\nconsistent and controlled path for new features to enter the framework.\n\nMany changes, including bug fixes and documentation improvements can be\nimplemented and reviewed via the normal GitHub pull request workflow.\n\nSome changes though are \"substantial\", and we ask that these be put\nthrough a bit of a design process and produce a consensus among the ComfyUI\n[core team] and the community.\n\n## The RFC life-cycle\n\nAn RFC goes through the following stages:\n\n- **Pending:** when the RFC is submitted as a PR (with associated discussion thread). We use Discussions instead of Pull Request comments as the former provides better discussion threading.\n- **Active:** when an RFC is acknowledged and undergoing implementation. The feature may be shipped as experimental during this phase.\n- **Landed:** when an RFC's proposed changes are shipped as stable in a release.\n- **Rejected:** when an RFC is officially rejected or dropped.\n\n## When to follow this process\n\nYou need to follow this process if you intend to make \"substantial\"\nchanges to standards / APIs in the ComfyUI ecosystem.\n\nWhat constitutes a \"substantial\" change is evolving based on community norms, but may include the following:\n\n- A new addition to or modification of existing ComfyUI core libraries or backend APIs eg. [Model Patcher](https://github.com/comfyanonymous/ComfyUI/commit/0ee322ec5f338791c5836b79830e2f419d6fcc79). If you are writing a custom node and want something exposed by core in an API, please open an issue.\n- A major change to ComfyUI functionality, such as the execution engine eg. [Execution Model Inversion](https://github.com/comfyanonymous/ComfyUI/commit/5cfe38f41c7091b0fd954877d9d7427a8b438b1a)\n- Changes to workflow.json schema\n- Changes to custom node standards\n- Request for frontend widgets and APIs\n- Nodes that should be provided by core\n- Anything that will be relied on by developers using ComfyUI (eg. `/prompt` API)\n\nIf you submit a pull request to implement a new feature without going\nthrough the RFC process, it may be closed with a polite request to\nsubmit an RFC first.\n\n## Why do you need to do this\n\nIt is great that you are considering suggesting new features or changes to ComfyUI - we appreciate your willingness to contribute! However, as ComfyUI becomes more widely used, we need to take stability more seriously, and thus have to carefully consider the impact of every change we make that may affect end users.\n\nThese constraints and tradeoffs may not be immediately obvious to users who are proposing a change just to solve a specific problem they just ran into. The RFC process serves as a way to guide you through our thought process when making changes to ComfyUI, so that we can be on the same page when discussing why or why not these changes should be made.\n\n## Gathering feedback before submitting\n\nIt's often helpful to get feedback on your concept before diving into the\nlevel of API design detail required for an RFC. **You may open an\nissue on this repo to start a high-level discussion**, with the goal of\neventually formulating an RFC pull request with the specific implementation\ndesign.\n\nOur [Discord](https://discord.com/invite/comfyorg) is also a good place to start a discussion.\n\n## What the process is\n\nIn short, to get a major feature added to ComfyUI, one must first get the\nRFC merged into the RFC repo as a markdown file. At that point the RFC\nis 'active' and may be implemented with the goal of eventual inclusion\ninto ComfyUI.\n\n1.  Work on your proposal in a Markdown file based on the template (`0000-template.md`) found in this repo.\n\n    - Put care into the details: **RFCs that do not present convincing motivation, demonstrate understanding of the impact of the design, or are disingenuous about the drawbacks or alternatives tend to be poorly-received**.\n\n2.  Submit the Markdown file as a pull request.\n\n    - Fork this repo.\n\n    - Create your proposal as `rfcs/0000-my-feature.md` (where \"my-feature\" is descriptive). Don't assign an RFC number yet, that will be done when the PR is merged. Make sure to place the file in the `rfcs` directory.\n\n    - Submit a pull request. A new thread in [Discussions](https://github.com/comfy-org/rfcs/discussions) will be made automatically.\n\n    - Build consensus and integrate feedback in the discussion thread. RFCs that have broad support are much more likely to make progress than those that don't receive any comments.\n\n3.  Eventually, the [core team] will decide whether the RFC is a candidate\n    for inclusion in ComfyUI.\n\n    - An RFC can be modified based upon feedback from the [core team] and community. Significant modifications may trigger a new final comment period.\n\n    - An RFC may be rejected after public discussion has settled and comments have been made summarizing the rationale for rejection. A member of the [core team] should then close the RFC's associated pull request.\n\n    - An RFC may be accepted at the close of its final comment period. A [core team] member will merge the RFC's associated pull request, at which point the RFC will become 'active'.\n\n## Details on Active RFCs\n\nOnce an RFC becomes active then authors may implement it and submit the\nfeature as a pull request to the relevant repo. Becoming 'active' is not a rubber stamp, and in particular still does not mean the feature will ultimately\nbe merged; it does mean that the [core team] has agreed to it in principle\nand are amenable to merging it.\n\nFurthermore, the fact that a given RFC has been accepted and is\n'active' implies nothing about what priority is assigned to its\nimplementation, nor whether anybody is currently working on it.\n\nModifications to active RFC's can be done in followup PR's. We strive\nto write each RFC in a manner that it will reflect the final design of\nthe feature; but the nature of the process means that we cannot expect\nevery merged RFC to actually reflect what the end result will be at\nthe time of the next major release; therefore we try to keep each RFC\ndocument somewhat in sync with the language feature as planned,\ntracking such changes via followup pull requests to the document.\n\n## Implementing an RFC\n\nThe author of an RFC is not obligated to implement it. Of course, the\nRFC author (like any other developer) is welcome to post an\nimplementation for review after the RFC has been accepted.\n\nAn active RFC should have the link to the implementation PR listed if there is one. Feedback to the actual implementation should be conducted in the implementation PR instead of the original RFC PR.\n\nIf you are interested in working on the implementation for an 'active'\nRFC, but cannot determine if someone else is already working on it,\nfeel free to ask (e.g. by leaving a comment on the associated issue).\n\n## Reviewing RFC's\n\nMembers of the [core team] will attempt to review some set of open RFC\npull requests on a regular basis. If a [core team] member believes an RFC PR is ready to be accepted into active status, they can approve the PR using GitHub's review feature to signal their approval of the RFC.\n\n**ComfyUI's RFC process owes its inspiration to the [Vue RFC process]**\n\n[vue rfc process]: https://github.com/vuejs/rfcs\n[core team]: https://www.comfy.org/about\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcomfy-org%2Frfcs","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fcomfy-org%2Frfcs","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fcomfy-org%2Frfcs/lists"}