Resources is Sweet Tea's main public discovery surface. It brings Sweet Tea Pipes and supporting ComfyUI ecosystem information into one place so you can search by the job you want to do, compare the available paths, and inspect what each path may require before opening it.
Browsing public Resources does not require an account. Actions that create account-owned state, such as syncing a Pipe to My Desk, still require sign-in. A specific download or external service can also retain its own safety, ownership, or provider-access requirements.
Start from a Goal
The default Resources page is useful before you enter a search. When the current catalog contains them, it shows:
- a maintained Sweet Tea Pipe under Start here;
- outcome-oriented resource collections;
- a distinction between hosted Sweet Tea Pipes and external ecosystem resources; and
- a route to Workflow Doc when you already have a workflow file to inspect.
Use ordinary language in search, such as portrait setup for character variations or image to video workflow for short anime clips. Results can include several resource types because a runnable workflow may need a Pipe or workflow plus models, node packs, and setup guidance.
What the Catalog Contains
| Type | What it represents |
|---|---|
| Pipe | A Sweet Tea workflow tool with a Studio-facing interface and Pipe-specific actions |
| Workflow | A source-linked ComfyUI workflow that may still need review, dependencies, or conversion before Studio use |
| Model | A checkpoint, adapter, encoder, VAE, upscaler, or other model resource |
| Node pack | A custom-node package or registry-backed node collection |
| Guide | Sweet Tea or source-linked documentation relevant to a task or dependency |
A Resource entry is information about an item; it is not automatically an installed or runnable item. In particular, an external workflow does not become a Sweet Tea Pipe merely because it appears in Resources.
Search and Filters
Use the left-side search controls to narrow the catalog by:
- Type — Pipes, workflows, models, node packs, or guides;
- Task — such as text to image, image to image, video, audio, captioning, or upscaling;
- Model family and Model type;
- Source — Sweet Tea or external;
- Disposition — Verified, Approved, or Unvetted; and
- Sort — Recommended, Sweet Tea readiness, Freshness, or Newest.
Enable Hosted by Sweet Tea when you specifically want first-party hosted results. When a hosted Pipe is a strong fit for a search, Resources can show it ahead of the wider ecosystem results without hiding those other results.
Broaden one dimension at a time when nothing matches. First remove an overly specific model or task filter, then shorten the search phrase. A true zero-result state is different from an unavailable catalog: Resources says when the catalog request itself could not be completed and preserves the search for a retry.
Reading Trust and Readiness Signals
Treat every badge as a bounded signal rather than a blanket guarantee:
- Hosted identifies a Sweet Tea delivery path; it does not prove that your local runtime already has every dependency.
- Verified, Approved, and Unvetted describe the record's current review or evidence lane. They are not interchangeable with creator verification and do not guarantee that a workflow is safe or compatible with your machine.
- A readiness value helps compare results within the catalog. Actual execution readiness still depends on the Pipe or workflow, its exact dependencies, and the ComfyUI runtime where you intend to use it.
Use the source, requirements, version, and provenance fields in the opened detail rather than inferring compatibility from one badge or score.
Inspecting a Resource
Select Inspect to open the detail without losing the current result list, or open the full detail page when you want a shareable route and more room. Depending on the resource and the evidence currently available, the detail can include:
- a plain-language overview or clearly labeled source excerpt;
- task, family, version, publisher, license, and update facts;
- explicit model or node-pack requirements;
- helpful guides and related Pipes or workflows;
- workflow lineage, including direct or ancestor relationships when supported;
- representative source links and verification dates;
- source evidence, selected media, and field-level provenance;
- model artifacts and exact download links when those artifacts are available and verified; and
- unresolved requirements or canonical links that still need review.
Not every source supplies every field. An absent requirement or media panel means no explicit item is attached to the current public record; it does not prove that the upstream workflow has no dependency or that no preview exists anywhere. Follow the canonical source when you need facts the current Resources entry does not yet contain.
For an external resource, Open source leaves Sweet Tea for the upstream page. Review that destination's license, file, version, and instructions before downloading anything. For a Sweet Tea Pipe, the detail can expose Pipe-specific Download and Sync actions. Download retrieves the available .tea package; Sync signs in when needed and adds the Pipe to account-owned Desk state.
Resource Collections
Collections are goal-first stacks rather than personal image collections. A collection combines one primary path with supporting resources most likely to help with the same outcome. Items can be labeled as:
- Primary — the main starting point;
- Companion — a supporting dependency or resource;
- Guide — setup or usage documentation; or
- Alternative — another path to the same or a related goal.
Open a collection to inspect its included items and any available workflow lineage, or choose Search this goal to return to the full Resources catalog with the collection's goal query. A collection does not install its contents or assert that every item is required on every runtime.
Resources and Pipes
Use Resources for broad discovery across the ecosystem. Use a Pipe's direct detail page for its package, versions, creator information, and publishing-specific actions. The direct Pipes surfaces also remain the place to upload or publish your own .tea package; see Web Pipes Discovery and Publishing.
This division keeps discovery and execution evidence separate: Resources helps you understand the available path, while the Pipe and Studio surfaces own package use, import, runtime validation, and generation.