nodes/DemonGatanjieu-Anomalous_Model_Browser

Files

T

DemonGatanjieuandClaude Opus 5.5 7b363bdac8 Light theme: follow ComfyUI, dark, light or Abyssal Scarlet

Settings -> Appearance -> Theme (and the ComfyUI setting
Anomalous.ModelBrowser.Theme, which replaces the Abyssal Scarlet switch)
picks Follow ComfyUI (default), Dark, Light or Abyssal Scarlet. Following
ComfyUI watches the dark-theme class ComfyUI sets on <html> for a dark
palette and repaints at once; an older Abyssal switch reads as Abyssal.

The light theme is html.amb-theme-light with its own --amb-* values. Hard
coded colors were turned into tokens whose dark values are the colors they
replace (checked: every stylesheet resolves to the same dark values):
rgba(var(--amb-ink-rgb), a) for tints, status shades, tooltip, float,
dialog, sunken, scrim and note tokens. Older rules and inline styles that
wrote a dark color now write var(--amb-lt-<role>, <that color>); the
--amb-lt-* tokens exist only in the light theme. Inside the plugin's
windows ComfyUI's palette variables (--bg-color, --fg-color ...) follow the
plugin's theme when the two differ. Surfaces over images stay dark, and the
image viewer gets the dark tokens back. The ready banner on a recipe reads
green instead of pink. Stylesheet cache versions are bumped.

Checked on a test ComfyUI in light and dark: home, models, gallery and its
viewer, workflows and a recipe's tabs, combos and a combo, prompts and the
docked drawer, voices, audio library, settings, scan, Model Check, current
node and its model picker, a model's detail with notes, share, save
recipe, update guide, versions, GPT-SoVITS settings and the prompt dialog;
light with a dark ComfyUI, and Abyssal Scarlet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-07 17:27:02 +08:00

backend.md

feat(backup): models' scan results, and Civitai covers on request

2026-10-06 23:11:51 +08:00

frontend.md

Light theme: follow ComfyUI, dark, light or Abyssal Scarlet

2026-10-07 17:27:02 +08:00

lessons.md

docs: lessons move from the private .agents notes into the repository

2026-10-06 17:54:20 +08:00

material-library.md

Drag combo cards onto the canvas; un-keep from the gallery star

2026-10-05 00:31:45 +08:00

model-resolution.md

feat(model-check): download missing models, to the folder you choose

2026-10-06 01:28:51 +08:00

README.md

docs: lessons move from the private .agents notes into the repository

2026-10-06 17:54:20 +08:00

recipe-model-lifecycle.md

Rename Model Doctor to Model Check

2026-10-02 16:32:33 +08:00

recipes.md

feat(recipes): reopen recipe packages, imported through share and import

2026-10-07 00:32:05 +08:00

update-guide.md

test: publish the plugin's tests, one command to run them

2026-10-06 17:47:35 +08:00

README.md

Architecture Topic Guide

Start with the repository-root ARCHITECTURE.md, then open only the topic needed for the current task.

backend.md: Python routes, filesystem safety, persistence, scan state, model sidecars, and backend performance.
frontend.md: extension bootstrap, UI ownership, localization, media lifecycle, panel state, and graph mutations.
recipes.md: Workflow Recipes, packages, galleries, Parameter Notebooks, prompt roles, and recipe-to-model transitions.
material-library.md: saved prompts and node values (material files), keeping an output image, and dragging prompts onto the canvas.
recipe-model-lifecycle.md: authoritative model fields, Hash synchronization, local matching, partial append, and note privacy.
model-resolution.md: model provenance, Model Check, hash injection, model scanning, and recovery policy.
../decisions/README.md: concise records of product and architectural decisions that still explain current behavior.

These documents describe current contracts rather than implementation history. For exact changes, use Git history. For user-visible releases, use CHANGELOG.md. For recurring implementation traps, use lessons.md.