docs: add FAQ entry for embedding import on Comfy Cloud#1256
Open
lin-bot23 wants to merge 1 commit into
Open
Conversation
📝 WalkthroughWalkthroughThe model import FAQ now explains how to import embedding and textual inversion files, lists supported formats, and shows the ChangesEmbedding Import Documentation
🚥 Pre-merge checks | ✅ 2✅ Passed checks (2 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@cloud/import-models.mdx`:
- Around line 149-150: Reconcile the supported file formats between the upload
restriction near line 122 and the FAQ accordion titled “Can I import embedding
or textual inversion files?”. Clarify that the restriction applies only to
standard model uploads if embeddings and textual inversion files may use .pt and
.bin, or remove those formats from the FAQ so both sections state the same
supported behavior.
- Line 150: Update the inline code spans in the import guidance to use unescaped
backticks for the supported file extensions, CLIPTextEncode, and embedding
syntax; preserve the existing wording and examples.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro Plus
Run ID: 856c7ee7-7d4d-48b0-a7be-4a0b8aef7ef3
📒 Files selected for processing (1)
cloud/import-models.mdx
Comment on lines
+149
to
+150
| <Accordion title="Can I import embedding or textual inversion files?"> | ||
| Yes. Embedding and textual inversion files (supported formats: \`.safetensors\`, \`.pt\`, \`.bin\`) can be imported the same way as other models. Import them from Civitai or Hugging Face using the standard import flow, then reference them in your \`CLIPTextEncode\` node prompt with the embedding syntax (e.g., \`embedding:my-embedding-name\`). |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Reconcile this FAQ with the upload restriction above.
Line 122 says only safetensor files are supported, while this FAQ claims .pt and .bin imports work. Clarify whether the restriction applies only to standard model uploads, or update one of the conflicting claims.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@cloud/import-models.mdx` around lines 149 - 150, Reconcile the supported file
formats between the upload restriction near line 122 and the FAQ accordion
titled “Can I import embedding or textual inversion files?”. Clarify that the
restriction applies only to standard model uploads if embeddings and textual
inversion files may use .pt and .bin, or remove those formats from the FAQ so
both sections state the same supported behavior.
| </Accordion> | ||
|
|
||
| <Accordion title="Can I import embedding or textual inversion files?"> | ||
| Yes. Embedding and textual inversion files (supported formats: \`.safetensors\`, \`.pt\`, \`.bin\`) can be imported the same way as other models. Import them from Civitai or Hugging Face using the standard import flow, then reference them in your \`CLIPTextEncode\` node prompt with the embedding syntax (e.g., \`embedding:my-embedding-name\`). |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Remove the backslashes from inline code spans.
The ``` sequences escape the backticks, so these values may render as literal backticks instead of code-styled tokens. Keep the syntax crisp, not cryptic.
Proposed fix
- Yes. Embedding and textual inversion files (supported formats: \`.safetensors\`, \`.pt\`, \`.bin\`) can be imported the same way as other models. Import them from Civitai or Hugging Face using the standard import flow, then reference them in your \`CLIPTextEncode\` node prompt with the embedding syntax (e.g., \`embedding:my-embedding-name\`).
+ Yes. Embedding and textual inversion files (supported formats: `.safetensors`, `.pt`, `.bin`) can be imported the same way as other models. Import them from Civitai or Hugging Face using the standard import flow, then reference them in your `CLIPTextEncode` node prompt with the embedding syntax (for example, `embedding:my-embedding-name`).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| Yes. Embedding and textual inversion files (supported formats: \`.safetensors\`, \`.pt\`, \`.bin\`) can be imported the same way as other models. Import them from Civitai or Hugging Face using the standard import flow, then reference them in your \`CLIPTextEncode\` node prompt with the embedding syntax (e.g., \`embedding:my-embedding-name\`). | |
| Yes. Embedding and textual inversion files (supported formats: `.safetensors`, `.pt`, `.bin`) can be imported the same way as other models. Import them from Civitai or Hugging Face using the standard import flow, then reference them in your `CLIPTextEncode` node prompt with the embedding syntax (for example, `embedding:my-embedding-name`). |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@cloud/import-models.mdx` at line 150, Update the inline code spans in the
import guidance to use unescaped backticks for the supported file extensions,
CLIPTextEncode, and embedding syntax; preserve the existing wording and
examples.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Multiple users asked about how to use embedding and textual inversion files on Comfy Cloud, but the documentation didn't address this. Mintlify AI analytics shows these questions as unanswered.
Changes
cloud/import-models.mdx: Added FAQ entry clarifying that embedding/textual inversion files (.safetensors, .pt, .bin) can be imported via the same Civitai/Hugging Face flow and referenced with embedding syntax in prompts.Source
Mintlify AI Assistant analytics data (2026-07-05)
Checklist