nodes/DemonGatanjieu-Anomalous_Model_Browser

Files

T

DemonGatanjieuandClaude Opus 5.5 bc9f18a838 Let the user pick which tools an AI app is offered: every tool, a short drawing set, or their own

The tool list sits in the AI's context every round and is at its budget (issue #27). The address
may now name a shorter one: ?tools=core (drawing in the AI app's own chat: no workbench, no file
moves, scans or downloads, no voice; the ways, skills, zoom_image and stop_run stay) or
?tools=mine (the user's checklist by stage, kept in user/anomalous/ai_tool_sets.json). Only the
list shrinks: tools/call takes every tool, an unknown or empty set offers all, and the address as
it is answers exactly as before. The instructions are split into parts and a part naming a tool
outside the set is dropped; without the workbench the AI is told to ask in its own chat.

Connect an AI picks the set above the address (not under a waiting task, which needs the
workbench); the address, the sentence and each app's line follow. Users pick from Anomalous's
tools and never add their own (AD-027).

The structure check passed absolute paths for every web file on one command line, which grew
past what Windows takes; it now passes them relative to the plugin.

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

2026-11-12 18:57:29 +08:00

backend.md

Let the user pick which tools an AI app is offered: every tool, a short drawing set, or their own

2026-11-12 18:57:29 +08:00

frontend.md

Show a model's guessed words, its author's settings and the files it needs in its details

2026-11-08 22:52:33 +08:00

lessons.md

Keep the Saves list still during a press

2026-11-05 21:21:41 +08:00

material-library.md

Lay a workflow's details out as flow, preset tabs and the preset shown

2026-11-02 20:05:38 +08:00

model-resolution.md

Say what Model Check can do without fingerprints, link its rules

2026-11-07 16:05:40 +08:00

README.md

A UI map: from a word on screen to its code, styles, route and backend function

2026-10-25 13:29:04 +08:00

recipe-model-lifecycle.md

Read the LoRAs of popular third-party nodes wherever AMB reads a workflow's models

2026-10-13 21:57:36 +08:00

recipes.md

Lay a workflow's details out as flow, preset tabs and the preset shown

2026-11-02 20:05:38 +08:00

tool-exam.md

Offer only the bases to pick from, stop an AI's run with no prompt, ask before swapping a named model

2026-11-10 21:13:34 +08:00

ui-flows.md

Let the user pick which tools an AI app is offered: every tool, a short drawing set, or their own

2026-11-12 18:57:29 +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.

ui-flows.md: the UI map's hand-written part, in Chinese: what each part of a page is for, what a click does and why, and one name per thing (a glossary the structure check enforces). Where a word on screen is drawn and what it calls comes from the code: node tools/ui_map.mjs find <words> (tools/ui_map.mjs, its index tools/ui_map_scan.mjs; build writes the whole map to the untracked docs/ui-map.md).
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.