feat(addons): add-ons UI direction B: one name, Turn on and Turn off, preview pane (#12858)

* refactor(addons): one name and one verb pair in the add-ons UI

The sidebar, the page and the tabs now say Add-ons. The tabs are My
add-ons, Find add-ons and Sources. Turn on and Turn off replace Enable,
Start, Disable and Stop wherever they label a button, and the state words
read On and Off. The subtitle no longer names the owner.

Other locales get the new keys; the main labels are translated and the
rest carry the English text until a translator refines them. A unit test
checks that every locale has the keys of English.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

* feat(addons): show what an add-on does on its card and move actions to a menu

A card now shows the add-on description, an "Adds a page" line and the
number of chat tools when they apply. The pin button and the bare arrows
are replaced by one overflow menu with Show in sidebar, Details and
Remove. Reordering a pinned add-on stays in the same menu. Remove asks
first and runs the typed uninstall action; only administrators see it.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

* feat(addons): add a preview pane for the selected add-on

Selecting a card, or choosing Details in its menu, opens a pane beside
the list. It shows the name and state, the description, what the add-on
adds, Turn on or Turn off and Remove, and its version and source. The pane
replaces the modal sheet and uses the data the list already has. The
source comes from the installed list that the host already serves to
administrators. Screenshot slots show only when the host lists images for
the add-on; today it lists none, so no slot is drawn.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

* feat(addons): clear first-run and empty states for My add-ons

With nothing installed, an administrator now sees three add-ons from the
sources, each with Install and turn on, and a link to Find add-ons. A
search that finds nothing says that no add-on matches and offers to clear
the search, instead of saying that nothing is installed. Install and turn
on is one action of the user: it installs, then turns the add-on on, with
a separate operation identity for each step and the progress or the reason
for a failure shown on the card.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

* feat(addons): one button and folded details on Find add-ons entries

Each entry shows its description, an "Adds a page" label when the library
entry declares a main page, and one button: Install and turn on. An
add-on that is installed but off offers Turn on. Details is folded into
the entry and shows the trust and build facts the entry already carries,
so the separate details sheet is gone. A backend keeps a plain Install,
because a backend has no on or off.

The library entry carries no tool count, so the entry cannot say how many
chat tools an add-on adds. That label appears on My add-ons, where the
list knows it.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

* feat(addons): install and turn on in one dialog with inline progress

Install and turn on now asks once. The dialog then stays open and shows
two steps, the install and the turn on, and ends on the result or on the
reason a step failed with a way to try again. A failed turn on keeps the
install and the retry only turns the add-on on. Each step is its own
action with its own operation identity, so an unknown outcome still
blocks further actions on the add-on until it is read or dismissed. The
first-run cards use the same dialog. The two-step flow is a plain function
with unit tests.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

* refactor(addons): fold the Installed tab into My add-ons

The page now has three tabs: My add-ons, Find add-ons and Sources. What
the Installed tab showed is in the preview pane of each add-on, under
More details for administrators: health, trust, compatibility, storage,
data recovery and updates, with Check for updates and Upgrade. Remove
and Turn on or Turn off are on the card and in the pane. An old
?tab=installed address opens My add-ons, and the management link
?manage=ID opens the details of that add-on. A card shows an update mark
when the host reports one. Closing the pane returns focus to its card.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

* docs(addons): describe the new add-ons page labels

Update the add-ons feature page and the pages that point at it: the
sidebar item and the page are called Add-ons, the tabs are My add-ons,
Find add-ons and Sources, Turn on and Turn off replace Start and Stop,
the card menu replaces the pin control, and the preview pane holds what
the Installed tab showed.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

* feat(addons): say what is wrong on the page of an add-on that cannot open

The page of an add-on that cannot open now depends on the add-on. One
that is installed but off says "<name> is off" and offers Turn on to an
administrator. One that is not installed says so and sends an
administrator to Find add-ons. One that failed shows the reason and a link
to its details. A reader gets a line that says who can fix it, and no
button. The page title is the name of the add-on, with a capital first
letter when the host lists no title, and no longer the bare identifier.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

* feat(chat): put the add-on tools control next to MCP and say what off means

The add-on tools control moves from the chat header to the composer, right
after the MCP control, because both decide what the model may call in this
chat. Its menu starts with one line: an add-on that is off here does
nothing in this chat. Only add-ons that ship tools appear in it, as
before.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

* chore(addons): clear lint warnings of the new components

Add the lint header the add-on components use for JSX-only imports, drop
an unneeded directive, stop exporting a helper from a component file and
extract the dependencies of an effect.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

* test(addons): update the backend library specs for the folded entry details

A backend says its kind on the entry, an add-on says it under Details,
Details is a fold of the entry and an installed backend has no Install
button.

Assisted-by: Claude:claude-sonnet-5-5 [Claude Code]
Signed-off-by: Ettore Di Giacinto <mudler@localai.io>

---------

Signed-off-by: Ettore Di Giacinto <mudler@localai.io>
Co-authored-by: Ettore Di Giacinto <mudler@localai.io>

docs/content/features/addons.md

@@ -124,7 +124,7 @@ A library source is a place LocalAI reads entries from. There are three kinds:
 
 All sources of all kinds are in one store, `addons/sources.json` under the data path.
 `local-ai library` (see the [CLI reference](/reference/cli-reference/#library-sources)), the
-HTTP routes below and the Libraries tab work on the same store with the same code, so
+HTTP routes below and the Sources tab work on the same store with the same code, so
 a change made in one place shows in the others.
 
 A source can be a default: one that LocalAI ships (the official add-on library, the
@@ -135,9 +135,9 @@ you remove a default, LocalAI keeps a record of the removal (a tombstone, `remov
 true`), so the default does not come back at the next start. Turn the source on again
 to bring it back. A source you added is deleted when you remove it.
 
-### The Libraries tab
+### The Sources tab
 
-The Libraries tab of the Add-ons page lists the sources of all three kinds. Use the kind
+The Sources tab of the Add-ons page lists the sources of all three kinds. Use the kind
 filter to show only add-ons, backends or models. Each source shows its kind, a Default
 badge for a shipped default, and its state: enabled, disabled, removed or, while the
 official libraries are off, off. Administrators can add a source (kind, format, name and
@@ -166,7 +166,7 @@ in the group Backends and galleries. On the command line it is
 
 When it is off, LocalAI does not read the default sources. The default add-on library,
 model gallery index and backend gallery index are not used for search, install or
-update checks. They stay in the store, still marked `default`, and the Libraries tab shows
+update checks. They stay in the store, still marked `default`, and the Sources tab shows
 them as off (`suspended: true` in the routes). Each source keeps its own enabled state, so turning the
 setting back on restores exactly what was there. Sources you added are not affected. The
 change applies at once, with no restart.
@@ -208,7 +208,7 @@ backends, the way the model library is for the models. The backend gallery
 (`backend/index.yaml`) is a generated copy of it. A tagged build before the cutover reads
 the gallery by default; a build from master reads the library. See
 [The backend library](#the-backend-library). A library entry of kind `backend` can also be
-installed by digest from the Browse tab, as described below.
+installed by digest from the Find add-ons tab, as described below.
 
 ### How a reader treats an unknown kind
 
@@ -217,7 +217,7 @@ not read the fields of a skipped entry, so a newer kind can carry fields this ve
 never seen. The index is not refused. A skipped entry is reported in two places:
 
 - the refresh result and the state of the library have `skipped` (a count) and
-  `skippedKinds`. The Libraries tab shows them;
+  `skippedKinds`. The Sources tab shows them;
 - the refresh writes a warning to the log.
 
 A kind that is not a plain lowercase name, or that is not text, is a malformed entry
@@ -304,10 +304,11 @@ signer exactly.
 
 ### Install a backend from a library
 
-An administrator installs a backend from the Browse tab of the Add-ons page. The entry
+An administrator installs a backend from the Find add-ons tab of the Add-ons page. The entry
 shows its kind. The page sends the install to the backend route, not to the add-on
-lifecycle: an add-on stays disabled until you enable it, a backend is ready to use when
-the install ends.
+lifecycle. The page installs an add-on and turns it on in one action (Install and turn
+on); the install itself leaves an add-on disabled. A backend has no on or off: it is
+ready to use when the install ends, and its button says Install.
 
 The route is `POST /backends/library/install`. It is for administrators and exists only
 when the add-on owner runs on this instance:
@@ -335,7 +336,7 @@ follow it. The `phase` of the job is the step it is in, in this order: `resolvin
 `verifying` (only when the library requires a signature), `size`, `fetching` (with
 `progress` and the sizes of the fetch) and `writing`. A job that ends has `processed` set.
 It ends with the phase `done` and `message` `completed`, or with `error` set and the
-`phase` of the step that failed. The Browse tab shows these steps. Refusals that depend on
+`phase` of the step that failed. The Find add-ons tab shows these steps. Refusals that depend on
 the entry arrive this way: an unknown entry, a name installed from another origin (a
 gallery, another library or a manual install; nothing changes), an image over the size
 limit, a library that strict mode refuses. The request itself answers `400` when it does
@@ -377,7 +378,7 @@ backend gallery: 1088 backends (934 concrete backends and 154 meta backends) in
 entries, because a backend built for several platforms has one entry for each. LocalAI
 registers it on the first start as the source `official-backends`, next to the backend
 gallery `localai-backends`, and a source you remove stays removed. To add it again later,
-use the Libraries tab with this URL and the policy above:
+use the Sources tab with this URL and the policy above:
 
 ```
 https://raw.githubusercontent.com/mudler/LocalAI/master/gallery/backends/index.yaml
@@ -1940,7 +1941,7 @@ are a later task and will have their own review.
 ### Built-in add-ons
 
 `GET /api/addons/builtin` lists the page add-ons that ship inside the web bundle, so the
-Add-ons drawer can show them next to the installed apps. The answer is
+My add-ons page can show them next to the installed add-ons. The answer is
 `{"builtin": [...]}`, and each entry has an `id`, a `kind` (always `page`), a `titleKey`,
 an `icon` and a `mainPath`, plus a `feature` or `adminOnly` when the entry has a gate.
 Today the list is empty: Studio and Talk, which used to be built in, are packaged
@@ -1953,7 +1954,7 @@ sent with `Cache-Control: private, no-store`.
 
 ### Pins
 
-Pinned apps are listed in the sidebar under Apps, in pin order. A pinned tile in the add-ons drawer has buttons to move it earlier or later.
+Pinned add-ons are listed in the sidebar under Add-ons, in pin order. The menu of a pinned card in My add-ons has **Move earlier** and **Move later**.
 
 `GET /api/addons/pins` returns the caller's pinned add-on IDs as a JSON array, in order.
 `PUT /api/addons/pins` takes a JSON array of add-on IDs, replaces the caller's pins with it
@@ -1994,26 +1995,28 @@ serves `/api/addons/builtin` and `/api/addons/pins`.
 
 ## Add-ons page and management
 
-The web UI serves one page for add-ons at `/app/addons`, the **Add-ons drawer**. It is
+The web UI serves one page for add-ons at `/app/addons`, called **Add-ons**. It is
 shown to a caller who holds the `addons` feature, and to anyone who can open a built-in
-tile (none today). Studio and Talk are add-ons: they are in the drawer only while they
-are installed. Administrators also
-reach **Browse**, **Installed** and **Libraries** from the drawer. The tabs are a
+tile (none today). Studio and Talk are add-ons: they are listed only while they
+are installed. The first tab is **My add-ons**. Administrators also
+reach **Find add-ons** and **Sources**. The tabs are a
 convenience: the owner checks administration again on every call, so a request that skips
 the page is denied the same way (403).
 
-The sidebar has the items **Chat**, **Models** and **Apps**. **Apps** opens the add-ons drawer at
-`/app/addons`. The pinned apps are listed under it, in pin order, as indented links with the app icon and title; nothing is listed when no app is
-pinned, and the list is hidden when the sidebar is collapsed. The user pins add-ons and changes
-their order with the buttons on a pinned tile in the drawer. Pins belong to the user, follow the user across browsers, and are
+The sidebar has the items **Chat**, **Models** and **Add-ons**. **Add-ons** opens the page at
+`/app/addons`. The add-ons a user shows in the sidebar are listed under it, in order, as indented links with the add-on icon and title; nothing is listed when none is
+shown, and the list is hidden when the sidebar is collapsed. The user adds an add-on to the sidebar with **Show in sidebar** in the menu of its card, and
+changes the order with **Move earlier** and **Move later** in the same menu. Pins belong to the user, follow the user across browsers, and are
 capped at eight. A pin whose add-on is stopped opens the detail view; a pin whose add-on
 was removed or is hidden is not drawn. Operators who
 need the previous sidebar can set `LOCALAI_LEGACY_NAVIGATION=true` (flag
 `--legacy-navigation`); it also brings back the Add-ons tab of the Build hub, which then opens `/app/addons`. The switch is a rollback aid and is removed one release after the
 new navigation ships; the UI reads it from the `addon_navigation` key of `/api/features`.
 
-A tab is addressed as `/app/addons?tab=browse|installed|libraries`. The management link of
-an app (`/app/addons?manage=ID`) opens the Installed tab with that addon's details open.
+A tab is addressed as `/app/addons?tab=browse|libraries`; My add-ons has no `tab`. What the
+former Installed tab showed is the **More details** section of an add-on in My add-ons, so
+`?tab=installed` opens My add-ons. The management link of an app
+(`/app/addons?manage=ID`) opens My add-ons with the details of that add-on open.
 
 ### Old links
 
@@ -2054,13 +2057,13 @@ A link with a model (`/app/image/<model>`) opens `/app/addons/studio/studio/imag
 The legacy switch (`LOCALAI_LEGACY_NAVIGATION`) restores the old sidebar and the Add-ons
 tab of the Build hub only. These redirects do not depend on it: with the switch on, the
 old generator links also open the Studio add-on. The legacy sidebar lists Home, Models, Chat and
-the hubs; Studio and Talk are in the drawer, as add-ons.
+the hubs; Studio and Talk are in My add-ons, as add-ons.
 
 ### The Studio add-on
 
 The Studio add-on (`studio`) is a packaged add-on. It is not shipped with LocalAI: install
-it from **Browse add-ons** in the drawer and start it. Once it is usable, it appears in
-the drawer and can be pinned. Until then the sidebar, the drawer and the Home `/studio`
+it from **Find add-ons** with **Install and turn on**. Once it is usable, it appears in
+My add-ons and can be shown in the sidebar. Until then the sidebar, My add-ons and the Home `/studio`
 command do not list it, and the old Studio links open the add-on page, which says the
 add-on is not available.
 
@@ -2086,7 +2089,7 @@ the `media` locale files of the web UI, in every language the web UI has.
 ### The Talk add-on
 
 The Talk add-on (`talk`) is a packaged add-on, separate from Studio. Install it from
-**Browse add-ons** and start it. It adds the page `/app/addons/talk/talk` (main page) for
+**Find add-ons** with **Install and turn on**. It adds the page `/app/addons/talk/talk` (main page) for
 users with the `addons` feature. The page opens a WebRTC session to a realtime pipeline
 through `/v1/realtime/calls` and reads the pipeline list from `/api/pipeline-models`, with
 the signed-in user's own session; the core keeps both routes. The page uses the MCP servers
@@ -2096,10 +2099,10 @@ file of the web UI; other languages read the English text.
 ### The Voice add-on
 
 The Voice add-on (`voice`) is a packaged add-on. It is not shipped with LocalAI: install it
-from **Browse add-ons** in the drawer and start it. Once it is usable, it appears in the
-drawer and can be pinned. The Build hub has no Voices tab.
+from **Find add-ons** with **Install and turn on**. Once it is usable, it appears in
+My add-ons and can be shown in the sidebar. The Build hub has no Voices tab.
 
-The add-on has one page, `/app/addons/voice/voice`, and one entry in the drawer. Its
+The add-on has one page, `/app/addons/voice/voice`, and one entry in My add-ons. Its
 sections are tabs of that page, and the tab is the next segment of the address:
 
 | Tab | Path | Who sees it |
@@ -2130,8 +2133,8 @@ views, built from one source directory into each add-on.
 ### The Face add-on
 
 The Face add-on (`face`) is a packaged add-on, separate from the Voice add-on. It is not
-shipped with LocalAI: install it from **Browse add-ons** in the drawer and start it. Once it
-is usable, it appears in the drawer and can be pinned. The Build hub has no Faces tab.
+shipped with LocalAI: install it from **Find add-ons** with **Install and turn on**. Once it
+is usable, it appears in My add-ons and can be shown in the sidebar. The Build hub has no Faces tab.
 
 | Page | Path | Who sees it |
 |---|---|---|
@@ -2151,8 +2154,8 @@ same views, built from one source directory into each add-on.
 ### The Fine-tuning and Quantization add-ons
 
 The Fine-tuning add-on (`fine-tuning`) and the Quantization add-on (`quantization`) are
-packaged add-ons. They are not shipped with LocalAI: install them from **Browse add-ons**
-in the drawer and start them. Once usable, they appear in the drawer and can be pinned.
+packaged add-ons. They are not shipped with LocalAI: install them from **Find add-ons**
+with **Install and turn on**. Once usable, they appear in My add-ons and can be shown in the sidebar.
 The Build hub has no Fine-Tune or Quantize tab.
 
 | Add-on | Page | Path | Who sees it |
@@ -2169,31 +2172,43 @@ reach the engine through [Host operations](#host-operations), and a tool can con
 a job that a tool started. See [Fine-tuning](../fine-tuning/#fine-tuning-is-an-add-on) and
 [Quantization](../quantization/#quantization-is-an-add-on).
 
-### The drawer
+### My add-ons
 
-The drawer is a grid of tiles with a search box. The built-in tiles (none today) come
-first, then the installed add-ons by identifier. Each tile has a pin control, a real
-button with a name and a pressed state, so it works from the keyboard; a pinned tile also
-has buttons to move it earlier or later. Pinning a ninth add-on opens a dialog that asks
-the user to unpin one first. A running tile opens the add-on; every other tile opens a
-detail view (`/app/addons?detail=ID`) and never the main page, because the main page
-needs a live process. Administrators also see **Browse add-ons** and **Add a new add-on**.
-A caller without the `addons` feature sees only the built-in tiles (none today), and the page does not
+My add-ons is a grid of cards with a search box. The built-in cards (none today) come
+first, then the installed add-ons by identifier. A card shows the icon, the name, the state
+(**On**, **Off**, or the state the host observed, such as **Starting** or **Failed**), the
+description, **Adds a page** when the add-on has a page and the number of **chat tools** when
+it has tools. A running add-on with a page also has an **Open** link. Each card has one
+overflow menu with **Show in sidebar** (or **Remove from sidebar**), **Details**, and, for an
+administrator, **Remove**. A pinned add-on also has **Move earlier** and **Move later** in the
+menu. Showing a ninth add-on in the sidebar opens a dialog that asks the user to remove one
+first. Selecting a card, or **Details**, opens the preview pane beside the list
+(`/app/addons?detail=ID`) and never the main page, because the main page needs a live
+process. The pane shows the name and state, the description, screenshots only when the host
+lists images for the add-on (it lists none today, so no slot is drawn), what the add-on adds
+(its page and its chat tools), **Turn on** or **Turn off**, **Remove** and the version and
+source. For an administrator it also has **More details**: health, trust, compatibility,
+storage, data recovery and updates. Administrators also see **Find add-ons**.
+A caller without the `addons` feature sees only the built-in cards (none today), and the page does not
 call `GET /api/addons/apps` for that caller.
 
-The detail view shows the entry as described next, and the pages the add-on names in
-`ui.navigation`. The drawer draws `GET /api/addons/apps`: the icon from the host's icon route, the
+With nothing installed, an administrator sees three add-ons from the sources, each with
+**Install and turn on**, and a link to **Find add-ons**. A search that matches nothing says
+that no add-on matches it.
+
+The pane also lists the pages the add-on names in
+`ui.navigation`. The page draws `GET /api/addons/apps`: the icon from the host's icon route, the
 title in the interface language (falling back to the default text and then to the
 identifier), the description, a state chip (`running`, `starting`, `failed`, `stopped`),
 an **update pending** chip when the owner's cached check reports one, an **Open** link only when the entry
-has a `mainPage`, and for an add-on without pages a short tool summary. Icons always
+has a `mainPage`, and a tool summary. Icons always
 come from the same origin; the page never loads an image from a manifest or a library.
 
 The list is read again every 5 seconds (30 seconds in a hidden tab). A failed read
 doubles the wait up to 60 seconds, keeps the last list on screen and says it may be
-out of date. Leaving the page cancels the pending read. Administrators see **Start**,
-**Stop** and **Manage** on an entry that carries the `admin` object. A start or stop
-sends a fresh operation ID with the generation that was listed and keeps that ID for
+out of date. Leaving the page cancels the pending read. Administrators see **Turn on** and
+**Turn off** on an entry that carries the `admin` object. They send
+a fresh operation ID with the generation that was listed and keep that ID for
 retries of that one action: once the operation is final (completed, failed or refused)
 the ID is dropped, so the next click is a new operation and is never answered from an
 old one. After `outcome_unknown` the page reads the original
@@ -2925,7 +2940,7 @@ Voice, Face, fine-tuning, quantization, Studio and Talk enable all four. A test
 platform is enabled without a recorded check.
 
 Each package also has a catalog template in `gallery/addons/<id>.yaml.tmpl`, so it can be
-listed in Browse add-ons once a maintainer renders and publishes its entries. See
+listed in Find add-ons once a maintainer renders and publishes its entries. See
 `gallery/addons/README.md` for the commands.
 
 Every add-on has its own repository. Tables publishes to `ADDON_OCI_REPOSITORY`. Each

docs/content/features/fine-tuning.md

@@ -216,7 +216,7 @@ A user needs the fine-tuning permission. Without it, the page says the account c
 
 ### Fine-tuning is an add-on
 
-The Fine-Tune page is the `fine-tuning` add-on. It does not ship with LocalAI. An administrator installs it from **Browse add-ons** in the drawer and starts it. Once it runs, it opens from the drawer at `/app/addons/fine-tuning/jobs` and can be pinned. The Build hub no longer has a Fine-Tune tab.
+The Fine-Tune page is the `fine-tuning` add-on. It does not ship with LocalAI. An administrator installs it from **Find add-ons** with **Install and turn on**. Once it is on, it opens from My add-ons at `/app/addons/fine-tuning/jobs` and can be shown in the sidebar. The Build hub no longer has a Fine-Tune tab.
 
 The old link `/app/fine-tune` keeps working. It opens the add-on page while the add-on is installed and usable, and it opens the same page in the core web UI otherwise.
 

docs/content/features/quantization.md

@@ -155,7 +155,7 @@ A user needs the quantization permission. Without it, the page says the account
 
 ### Quantization is an add-on
 
-The Quantize page is the `quantization` add-on. It does not ship with LocalAI. An administrator installs it from **Browse add-ons** in the drawer and starts it. Once it runs, it opens from the drawer at `/app/addons/quantization/jobs` and can be pinned. The Build hub no longer has a Quantize tab.
+The Quantize page is the `quantization` add-on. It does not ship with LocalAI. An administrator installs it from **Find add-ons** with **Install and turn on**. Once it is on, it opens from My add-ons at `/app/addons/quantization/jobs` and can be shown in the sidebar. The Build hub no longer has a Quantize tab.
 
 The old link `/app/quantize` keeps working. It opens the add-on page while the add-on is installed and usable, and it opens the same page in the core web UI otherwise.
 

docs/content/features/studio.md

@@ -6,7 +6,7 @@ url = "/features/studio/"
 +++
 
 {{% notice note %}}
-Studio is an add-on. It is not part of the web bundle: install it from **Browse add-ons** in the [Add-ons](../addons/#the-studio-add-on) drawer and start it. Once it is usable, it is in the drawer and can be pinned, and it opens at `/app/addons/studio/studio`. The old links (`/app/studio`, `/app/image` and the other generator links) open it there.
+Studio is an add-on. It is not part of the web bundle: install it from **Find add-ons** in the [Add-ons](../addons/#the-studio-add-on) page with **Install and turn on**. Once it is usable, it is in My add-ons and can be shown in the sidebar, and it opens at `/app/addons/studio/studio`. The old links (`/app/studio`, `/app/image` and the other generator links) open it there.
 {{% /notice %}}
 
 Studio is the part of the web UI where you make images, video, 3D objects, speech, sound and transformed audio, and find what you made before. It opens on a front page with a prompt box and your own work. Each type still has its own workspace page (Images, Video, 3D, TTS, Sound, Transform, Diarization) where a run happens.

docs/content/features/tables.md

@@ -331,7 +331,7 @@ deleted is refused like an unknown one. With none selected the tool answers a
 
 Tables ships its own UI as a standalone ES module in the package. It is loaded by
 the host after the host was built, so installing or updating Tables changes the
-pages without a rebuild of LocalAI. The Add-ons drawer shows a **Tables** tile.
+pages without a rebuild of LocalAI. The My add-ons page shows a **Tables** card.
 
 | Where | What |
 |---|---|