Skip to content

fix(api): harden core ASGI routes against custom-node mutation #10211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JPPhoto merged 8 commits into from
Nov 11, 2026
Merged

fix(api): harden core ASGI routes against custom-node mutation #10211

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
f7d4827
fix(api): harden ASGI route registration
JPPhoto Nov 9, 2026
7905306
docs(nodes): clarify ASGI route support
JPPhoto Nov 9, 2026
95d70f8
Merge branch 'invoke-ai:main' into asgi-hardening
JPPhoto Nov 9, 2026
7c9d4e8
fix(api): harden core ASGI routes against custom-node mutation
JPPhoto Nov 9, 2026
abc8da0
fix(api): snapshot Socket.IO ASGI dispatch
JPPhoto Nov 9, 2026
64dbc18
fix(api): preserve included WebSocket dependency overrides
JPPhoto Nov 10, 2026
807243e
fix(api): prevent clone cache ID reuse
JPPhoto Nov 10, 2026
909b682
Merge branch 'main' into asgi-hardening
JPPhoto Nov 11, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/src/content/docs/development/Guides/creating-node-pack.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -73,6 +73,14 @@ from invokeai.app.invocations.vae.flux_vae_encode import FluxVaeEncodeInvocation
Legacy root-level import paths remain available through forwarding shims until
a separately approved cleanup. Use canonical paths for new node packs.

Node packs extend InvokeAI through registered invocation classes. Before importing
custom nodes, InvokeAI captures its core routes and frontend/static serving
configuration. HTTP and other ASGI routes added by a pack are not served, while
registered invocation classes remain available and appear in the OpenAPI schema.
Requests to unregistered API paths return `404 Not Found`. This route boundary is
not a Python sandbox: node-pack code runs in-process and can access Python objects
and resources available to InvokeAI.

## Dependencies (`requirements.txt` or `pyproject.toml`)

If your nodes require additional Python packages, list them in a `requirements.txt` (or `pyproject.toml`) at the repository root:
Expand Down
Loading
Loading