Add one capability without losing a working Forge

Open Extensions → Install from URL, paste the Git repository URL, add a branch only when the publisher specifies one, install it, inspect the console, then use Installed → Apply and restart UI. Install one extension at a time and prove its exact action.

By default, user extensions live under the active data path in extensions/. If --data-dir changes the data path, the extension root moves with it. Use the paths reference to resolve the active location.

No. Original Forge changed backend behavior and uses Gradio 4 at the inspected commit. An A1111 directory entry or an old tutorial is not a current compatibility guarantee.

No. At the inspected commit, its default index URL points to the AUTOMATIC1111 extension directory. On 2 September 2026 that JSON exposed 353 entries, but the count and entries are volatile and neither proves Forge compatibility nor safety.

Built-ins ship inside the inspected Original Forge repository under extensions-builtin/. Third-party extensions are separate repositories installed under extensions/. Both can execute Python and add interface behavior, but only the built-in files belong to the inspected Forge commit.

Spaces are bundled wrapper directories, but their optional mini-app lifecycle and downloads are distinct from a normal user extension. Use the Spaces guide for install, launch, stop, remove, and network boundaries.

Yes. The Install from URL flow can run install.py immediately after cloning, and active third-party installers are also considered during launch setup. Review repository code and requirements before installation.

Yes. A reliable test requires Apply and restart UI or a full process restart. Refreshing the browser alone does not repeat installer, preload, import, callback, and UI construction stages.

Leave it empty to use the repository default. Enter a branch only when the extension publisher or a dated compatibility record names that exact branch; record it because a different branch is a different test subject.

It overrides the folder name under extensions/. Use it only when you need an explicit non-colliding local name. It does not change the repository identity or make incompatible code compatible.

The installer rejects duplicate repository URLs and existing target directories. Inspect Installed and the extensions/ directory before choosing another name; a second copy can create duplicate callbacks or canonical-name conflicts.

Record exact Forge and extension commits, prove a clean baseline, install the extension alone, restart, verify its control, run its exact promised action, and rerun the core control. Compatibility is that recorded result—not the presence of a folder or tab.

Do not treat a bulk copy as migration. It removes the one-change boundary and can introduce obsolete Gradio calls, shared dependency changes, duplicate identities, and overlapping built-ins. Start clean and evaluate one repository at a time.

Search the official temporary discussion by user job, then recheck the candidate repository’s current code, commits, issues, branch and supported Forge build. The discussion is discovery evidence, not certification.

It is an ongoing discussion opened on 9 September 2024, with community submissions over time. Each entry keeps its own date and confidence. Treat every candidate as needing a fresh repository review and local test.

Save a named state, update one extension, restart, repeat the clean core control and target action, then record old and new commits. Avoid updating the whole set at once because it erases the first-bad boundary.

No. It fetches update information and exposes the update state. Apply selected changes deliberately, one extension at a time, after saving a receipt and return point.

It can restore recorded Git-managed Forge and extension commits and enabled states when those repositories remain reachable and resettable. It is not a full installation, model, dependency, or arbitrary-file backup.

Use Extensions → Installed, clear or disable the extension, then Apply and restart UI. For a broken startup, launch temporarily with --disable-extra-extensions and follow the troubleshooting guide.

Current code restricts extension access when share, listen, ngrok, or a server name makes the instance non-local, unless an explicitly insecure override is used. Do not weaken that boundary as a generic fix.

Not as a normal install step. The flag is explicitly named insecure. Evaluate it only if you control and understand the complete network boundary; never expose extension administration casually.

Installation proves discovery only. The installer, preload, import, callback, visibility setting, browser script, or target action can still fail. Preserve the first console error and use the extension troubleshooting guide.

Include both repository URLs and full commits, branch, local directory, install route, launch arguments, OS, GPU, Python, Torch, Gradio, enabled extensions, exact action, first Python error, browser error, clean baseline, and disabled-extension results.

The inspected commit contains 38 directories under extensions-builtin/: 14 generation and guidance integrations, 8 preprocessors, 10 Space wrappers, and 6 utility or upscaler integrations. Directory presence does not guarantee a top-level tab.