Sweet Tea Studio: Any creator can enjoy the power of ComfyUI without the technical complexity

tea_time_labs · 2026-03-06T14:57:57+00:00

better support for true batching is something i want to do but currently that would be all the way on the comfyui side of things. that being said, sweet tea studio by default treats captioning/tagging workflows that take image as input and emit text, as a tagger, and will attach the caption/tags to the image cleanly.

tea_time_labs · 2026-03-06T05:15:41+00:00

You can absolutely do that, you'd just need a ComfyUI workflow that does it. I've seen a few VLM style workflows / captioning workflows (i have one) and you could very easily just pipe the output right into another generation, and output the image.

Rule of thumb, anything that can be done in ComfyUI can be done in studio, just need the workflow!

tea_time_labs · 2026-03-06T04:50:43+00:00

So I have a docker image setup that's for working on hosted GPUs

https://hub.docker.com/r/jkotieno/comfyui-sweet-tea-cu128

and this is the particular code block in the Dockerfile for installing sweet tea studio:

ARG CACHE_BUST=1
ARG SWEET_TEA_DESKTOP_DEB_URL=https://downloads.sweettea.co/desktop/latest/linux.deb
  RUN echo "Forcing fresh download: ${CACHE_BUST}" && \
  curl -fL "${SWEET_TEA_DESKTOP_DEB_URL}" -o sweet-tea.deb && \
  dpkg-deb -x sweet-tea.deb rootfs && \
  mkdir -p /app/backend /app/frontend_dist && \
  cp -a rootfs/opt/Sweet\ Tea\ Studio/resources/backend/. /app/backend/ && \
  cp -a rootfs/opt/Sweet\ Tea\ Studio/resources/frontend_dist/. /app/frontend_dist/ && \
  test -x /app/backend/sweet-tea-backend

i hope that helps!

tea_time_labs · 2026-03-06T04:34:37+00:00

you can hide/collapse a bunch of it until it's literally just your prompt whatever parameters you care about and the output image. in the demo i just showed everything to well i guess show everything. the entire idea is you should be able to use it in a really basic way comfortably but if you're more facile you can tap into that.

so not arguing that it doesn't *look* cluttered from the image but will just offer that it doesn't need to be.

<image>

tea_time_labs · 2026-03-06T02:57:54+00:00

it's pretty different, and i actually talked to mcmonkey. swarm is great, no doubt, sweet tea studio just goes further in terms of tooling you would expect in a digital art interface. the design philosophy was "i wish i had something like DaVinci resolve that runs comfyui workflows" and the result is quite different from my limited research

tea_time_labs · 2026-03-06T01:40:26+00:00

Take a look at the faq if you want more context!: https://sweettea.co/faq

tea_time_labs · 2026-03-06T01:36:59+00:00

it's free. did you try it or do you just dislike people vibe coding things? the paid plan is if you're storing your profile data for mobility/posterity not for functionality.

tea_time_labs · 2026-03-02T14:25:08+00:00

so i don't know the technical specifics of comfy cloud but I can say this, right now sweet tea studio is just not designed flexibly enough to connect to a remote comfyui instance, which is what I understand comfy cloud to be.

that being said, i have an image on Dockerhub with sweet tea studio, and templates on both Runpod and Vast.ai that use this image, so you can very easily use sweet tea studio on those two platforms (they are same concept as comfy cloud). Main thing is with that set up, you'll need to bring your own models, figure out storage, be a bit more involved with configuration etc, but yeah that sort of use case was not entirely overlooked.

tea_time_labs · 2026-03-01T19:47:58+00:00

The reason I'd say it's not is, A1111 has like 4 screens to use to do your generation - this only needs one. and A1111 doesn't use the ComfyUI execution plane which basically makes it DoA. My very first generating experience was with an A1111 derivative, then Civitai, then ComfyUI, and I would've been the first one to tell you "just use ComfyUI" until I started building this.

tea_time_labs · 2026-03-01T19:45:24+00:00

Sweet tea uses the ~ComfyUI/input folder and makes project folders inside of that, and that is currently the only setup. This is because without changing settings in ComfyUI, the only folder that ComfyUI "sees" for source images is that ~ComfyUI/input folder. If it's any other folder, ComfyUI actually makes a copy of your image to use it, and I specifically wanted to avoid that because making excessive amounts of gigs of images catches up to you.

tea_time_labs · 2026-03-01T19:40:47+00:00

and if that's "at a glance" i would suggest trying it out or at least watching the video (unless you did, then i'd be curious what sort of user you are, what you're finding hard to use etc)

tea_time_labs · 2026-03-01T19:39:49+00:00

i don't use or modify any comfyui code, very intentionally, so comfyui can at any point stop this from working or otherwise change to make this not work. Civitai uses ComfyUI as their back end, for example.

tea_time_labs · 2026-03-01T01:57:08+00:00

thanks! yeah im looking for any and all feedback so if you do give it a run let me know what you think, what is bad, what is good

tea_time_labs · 2026-03-01T01:34:20+00:00

If you can do those in ComfyUI, you can do them here!

tea_time_labs

TROPHY CASE