Shima Setup Hub
The pack's front desk — a settings anchor, not a processing node
- STATUS
Shima Setup Hub is where you'd expect a config dashboard to live, and it sort of is - but let's be blunt about what it's not. It processes no data. It takes nothing from your graph and hands nothing back that a sampler cares about. Its single output is a STATUS string telling you which asset pack is active and whether auto-update is on. If you placed it expecting it to load a model or set a seed, you're going to be disappointed.
Its real job is as a UI anchor for Shima's "bootstrap" system and its companion marketplace at shima.wf. The pack is built around composable "islands" - workflow fragments that auto-connect via Use Everywhere - and the Hub is the control panel for that ecosystem's local settings. The author's own node reference describes it as "a UI anchor for the Shima Bootstrap system," which is the most honest one-line summary you'll get.
What you actually set
- active_style_thumbnails - which style-thumbnail pack the Styler nodes use. Defaults to "Walking Woman", with "Still Life" and "YourStyleImages" (yours, after you add them). This is the one field with any real effect: it picks which preview images show up across the pack's styler nodes.
- auto_update - whether Shima checks for updates to those asset packs. Defaults to on.
- custom_download_url - an override URL for pack downloads, useful if you're mirroring assets or the marketplace endpoint is having a day. Leave it blank.
How it works
Under the hood it reads ShimaSettings from the pack's config (config/shima_settings.json, site_default_settings.json), merges the node's selection with whatever global pack is configured, and reports back. If you're connected to the shima.wf marketplace, purchased islands sync into a local SQLite DB and work offline - the Hub is the visible tip of that sync system. The good news for privacy-minded people: generation stays local, the marketplace is optional, and nothing about running these nodes requires an account. The pack's own docs push this "offline-first" angle hard, and the code backs it up.
Install
Nothing special:
cd ComfyUI/custom_nodes
git clone https://github.com/KDB-USJP/shima_wf
then restart. Or use ComfyUI Manager and search "Shima". The Hub itself needs no models, though the pack's official-dependencies bundle lists checkpoints like AbsoluteReality and JuggernautXL - those are for the official "Finals" workflows, not for the Hub, so don't let the dependency checker scare you into downloading a gig of models you don't need.
Should you even add it?
If you're only using a couple of Shima nodes, skip it - nothing breaks without it. If you're building island-style workflows, the pack's own getting-started guide tells you to place it first, mostly so the Styler thumbnails and asset packs behave. Two honest caveats: first, on first boot the pack auto-installs dependencies (Impact Pack, cg-use-everywhere, plus pip packages) and reaches out to its marketplace endpoint, which is exactly the kind of behavior to be aware of - this is a young pack with essentially no community footprint yet, so install from the official repo URL and keep an eye on what it downloads. Second, STATUS is a string you'll rarely wire anywhere. Treat the Hub as the pack's settings page and you'll be happy with it; treat it as a workflow node and you'll be confused.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| active_style_thumbnails | COMBO | Walking Woman | 3 options: Walking Woman, Still Life, YourStyleImages |
| auto_update | BOOLEAN | true | — |
| custom_download_urlopt | STRING | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| STATUS | STRING | — |