docs: add Ollama FAQ entry to Desktop FAQ page#1277
Conversation
|
Warning Review limit reached
Next review available in: 24 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughChangesOllama FAQ
🚥 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: 1
🤖 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 `@installation/desktop/faq.mdx`:
- Line 88: Update the ComfyUI Account API Key Integration link in the FAQ entry
to use the existing /development/comfyui-server/api-key-integration destination,
preserving the link text and surrounding content.
🪄 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: 851636fc-3982-4d62-bf8f-5ecf07608faf
📒 Files selected for processing (1)
installation/desktop/faq.mdx
| <Accordion title="Can I use Ollama with ComfyUI?"> | ||
| ComfyUI does not natively integrate with [Ollama](https://ollama.ai) for diffusion model backends. However, you can use Ollama-served LLMs for prompt generation and text processing through **partner nodes** or **custom nodes** available in the ComfyUI Manager registry. | ||
|
|
||
| For connecting ComfyUI to LLM services, see [ComfyUI Account API Key Integration](/development/comfyui-server/comfyui-account-api-key-integration). |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Locate the referenced docs page and any routing/redirect configuration.
git ls-files | rg -n "installation/desktop/faq\.mdx|development/comfyui-server|redirect|rewrites|routes|sidebars|nav|menu|comfyui-account-api-key-integration|api-key-integration" -NRepository: Comfy-Org/docs
Length of output: 3833
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Read the likely relevant files if they exist.
for f in \
installation/desktop/faq.mdx \
development/comfyui-server/api-key-integration.mdx \
development/comfyui-server/comfyui-account-api-key-integration.mdx \
docusaurus.config.* \
sidebars.* \
src/pages/**/[[...slug]]* \
src/pages/**/_redirects* \
static/_redirects \
vercel.json \
_redirects
do
[ -e "$f" ] && echo "### $f" && wc -l "$f" && sed -n '1,220p' "$f"
doneRepository: Comfy-Org/docs
Length of output: 10613
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Search for any explicit redirect from the old path to the new page.
rg -n --hidden --glob '!node_modules' --glob '!dist' --glob '!build' \
"comfyui-account-api-key-integration|api-key-integration|redirects?|rewrites?" .Repository: Comfy-Org/docs
Length of output: 13628
🏁 Script executed:
#!/bin/bash
set -euo pipefail
printf 'ROOT=%s\n' "$PWD"
for f in installation/desktop/faq.mdx development/comfyui-server/api-key-integration.mdx development/comfyui-server/comfyui-account-api-key-integration.mdx; do
if [ -f "$f" ]; then
echo "### $f"
wc -l "$f"
sed -n '1,160p' "$f"
else
echo "### MISSING $f"
fi
done
echo "### redirects/rewrite clues"
rg -n --hidden --glob '!node_modules' --glob '!dist' --glob '!build' \
"comfyui-account-api-key-integration|api-key-integration|redirect|rewrites|trailingSlash|cleanUrl|route" \
docusaurus.config.* src static . 2>/dev/null | sed -n '1,240p'Repository: Comfy-Org/docs
Length of output: 37678
🏁 Script executed:
#!/bin/bash
set -euo pipefail
# Check the generated route and any explicit redirect entry for the old URL.
rg -n '"(redirects|source|destination)"|comfyui-account-api-key-integration|development/comfyui-server/api-key-integration' docs.jsonRepository: Comfy-Org/docs
Length of output: 10881
Fix the FAQ link. installation/desktop/faq.mdx:88 points to /development/comfyui-server/comfyui-account-api-key-integration, but the page lives at /development/comfyui-server/api-key-integration. Update the link so readers don’t hit a 404.
Proposed fix
-For connecting ComfyUI to LLM services, see [ComfyUI Account API Key Integration](/development/comfyui-server/comfyui-account-api-key-integration).
+For connecting ComfyUI to LLM services, see [ComfyUI Account API Key Integration](/development/comfyui-server/api-key-integration).📝 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.
| For connecting ComfyUI to LLM services, see [ComfyUI Account API Key Integration](/development/comfyui-server/comfyui-account-api-key-integration). | |
| For connecting ComfyUI to LLM services, see [ComfyUI Account API Key Integration](/development/comfyui-server/api-key-integration). |
🤖 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 `@installation/desktop/faq.mdx` at line 88, Update the ComfyUI Account API Key
Integration link in the FAQ entry to use the existing
/development/comfyui-server/api-key-integration destination, preserving the link
text and surrounding content.
1 participant
Summary
Multiple users have asked whether ComfyUI supports Ollama. This adds a clear FAQ entry explaining that while ComfyUI doesn't natively integrate with Ollama for diffusion backends, users can leverage Ollama-served LLMs through partner nodes or custom nodes.
Changes
installation/desktop/faq.mdx: Added 'Can I use Ollama with ComfyUI?' FAQ entrySource
Mintlify AI Assistant analytics data (2026-07-16)
Checklist