docs: standardize model and service connection steps in use cases - #3807
Open
Meow33 wants to merge 2 commits into
Open
docs: standardize model and service connection steps in use cases#3807Meow33 wants to merge 2 commits into
Meow33 wants to merge 2 commits into
Conversation
|
@Meow33 is attempting to deploy a commit to the Lucky's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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.
Background
Standardize connection workflows across the following use-case guides: ComfyUI, Context7, Firecrawl, FlareSolverr, Jellyfin, Karakeep, LiteLLM, Navidrome, NemoClaw, OpenClaw, OpenCode, Paperclip, PDFMathTranslate, Pool CLI, Speaches and TensorZero.
Target Version for Merge
Related Issues
PRs Involving Sub-Systems
Other information:
Note
Low Risk
Documentation-only changes with no runtime or auth logic; risk is limited to outdated screenshots or links if product UI diverges from the new standard paths.
Overview
Standardizes how Olares use-case docs explain connecting apps to services and local models, mainly by
@include-ingdocs/reusables/ai-service-connections.mdfor app Endpoint setup and Model Console (Model name + OpenAI-compatible Base URL).Across guides (ComfyUI/Krita, Context7, Firecrawl, FlareSolverr, Jellyfin, Karakeep, LiteLLM, Navidrome, NemoClaw, OpenClaw, OpenCode/OMO, Paperclip, PDFMathTranslate, Pool CLI, Speaches, TensorZero, plus matching
zh/pages), the diff replaces bespoke “shared entrance” copy, hard-coded example URLs, and ComfyUI Shared / heavy Ollama-only walkthroughs with the same Settings > Applications > … > Entrances flow and placeholder endpoints like<your-firecrawl-endpoint>.Example-model refresh: many tutorials now default to Qwen3.6-27B (llama.cpp) (and related models such as Gemma 4 / EmbeddingGemma where noted) with Custom Provider / OpenAI-compatible wiring; OpenClaw is notably shortened (interactive onboarding only,
curl …/modelsand/chat/completions). NemoClaw drops the optional KEEP_ALIVE section. Doc metadata (doc_version,doc_updated) is bumped on touched pages.Reviewed by Cursor Bugbot for commit dd83931. Bugbot is set up for automated code reviews on this repo. Configure here.