6 Commits

Include renames

Author	SHA1	Message	Date
mudler-agentandEttore Di Giacinto	b39d37f559	feat(agents): limit saved agents to one folder (#13009) ... * Store the folder and its mode on a saved agent A saved agent gets FolderID, the workspace node of its folder, and FolderMode, read or write. The folder is kept by node so that a rename or a move is followed. A mode without a node is an agent whose folder is not chosen yet; Validate accepts it, and refuses a node without a mode. The GORM store adds two columns with defaults, so AutoMigrate fills the rows of existing agents as agents without a folder. The JSON store reads a file without the keys the same way. Both stores pass the new contract case. Assisted-by: Claude:claude-opus-5-5 * Keep on a chat whether its saved agent had a folder A chat whose agent is deleted runs today without the agent's grants. When that agent had a folder, nothing is left to say which folder the chat may read, so the chat must be refused instead of getting the whole home. ChatRecord.ScopedAgent records that the agent had a folder. CreateChat writes the flag and SetScopedAgent changes it. UpdateChat leaves it alone, like the tool switches, so the loop's stale copy of the record cannot clear it. Both chat stores read chats stored before the flag as not scoped; the GORM column has a default, so AutoMigrate is the migration. Assisted-by: Claude:claude-opus-5-5 * Add the design and plan for agent folder scope A saved agent works on the whole home folder of its user. The spec lets the user give an agent one folder and a mode, read only or read and write, and confines every chat that runs it to that folder. The workspace store enforces the folder through a fence on the actor, so a caller that forgets it gets less access, not more. The spec maps every caller that builds a user actor today, including the host bash, the sandbox runner and the add-on workspace operations, and how each is moved to the chat's access. The plan splits the work into ten lanes; the store fence and the agent record come first. Assisted-by: Claude:claude-opus-5-5 * Resolve the folder of a saved agent by node A person chooses an agent's folder by its path in their home; the agent keeps the node, so a rename or a move is followed. The new FolderResolver turns the path into the node and back, always as the user. A path is refused when it is not a live folder, when it is LocalAI/ or Chats/ or inside them, or when it names a parent. The home itself ("/") is allowed. The workspace stores cannot find a node by its ID yet. PathOf reads the newest change sets of the home first, checks the path it finds with Stat, and else lists the folders the user can read. A store that implements NodeByID is used instead. Nothing is cached, so every frontend answers the same. SaveAgent keeps the stored folder when it replaces an agent, so a caller that knows nothing of folders cannot widen one. SaveAgentWithFolder sets or clears it. ImportAgent looks the folder of a file up in the importer's home, and saves a folder that is not there as unset: the mode without a node, which does not start. Assisted-by: Claude:claude-opus-5-5 * Add a fence to the workspace actor A chat whose saved agent has a folder must reach only that folder and the chat's own folders. The store needs to know which folders those are on every call, so the actor carries them. Actor.Fenced returns a copy that reaches only the given folders, by node ID, each at most at its mode. The fence is an unexported field: a copy of the actor keeps it, and only Fenced can set it. Fencing a fenced actor adds a layer, and a node is reached only when every layer allows it, so a fence never grows. The helpers in export.go let both store implementations apply the same rules: the mode a fence allows on a node, its roots, and the limit of MaxFenceRoots roots per call. Assisted-by: Claude:claude-opus-5-5 * Show and choose the folder of an agent in the API The agent routes carry folder. A write takes {path, mode}: the server turns the path into the folder's node, and refuses with 400 a path that is not a folder of the user's home, or is LocalAI or Chats. A write without folder keeps the agent's folder, so a client that does not know the field cannot widen the agent; {path: ""} clears it. A read answers the folder's path now, its name, the mode and a state: ok, missing or unset. The node never leaves the server. An agent with a folder exports as version 2, with the folder's path and mode. A server that reads only version 1 refuses that file, so a scoped agent is never imported elsewhere as one with all the files. An agent without a folder still exports as version 1. The import reads both versions and looks the folder up in the importer's home; a folder that is not there saves the agent as unset, with a warning. The Swagger spec, the API instructions and the agents docs page show the field and the new file version. Assisted-by: Claude:claude-opus-5-5 * Enforce the actor fence in both workspace stores The store is the one place every file call of a chat goes through, so it applies the fence: a caller that forgets the agent's folder gets "not found", never the whole workspace. - The mode of a fenced actor on a node is the lower of its grants and the fence. A root in the Trash counts for nothing, and is back after Undo, because the fence holds the node ID. - A fenced actor never takes the administrator shortcut, so it cannot grant, revoke or list grants, and ReadablePrefixes gives only fence roots or folders inside them. - A root cannot be deleted, moved or renamed by the fenced actor, by any path: Move, Delete, Undo, an upper layer, or a delete of a folder above a nested root. - A fence with too many roots or a bad root is ErrInvalid. The shared suite in wstest runs the new specs against the JSON store and the GORM store (SQLite and PostgreSQL). Assisted-by: Claude:claude-opus-5-5 * Map the model's paths through the chat's place A chat's file tools spelled every path as a path in the user's home. A chat whose agent has a folder sees that folder at /workspace/home and its own chat folder at /workspace/chat, so the mapping must come from the mounts of the chat's view, not from the principal. session.Place maps a path the model writes to a workspace path: "/x", "x", "home/x" and "/workspace/home/x" are x in the primary mount, "/workspace/<name>/x" is x in the mount of that exact name, and the skill layers keep their names. It refuses "..", NUL, control characters and invalid UTF-8 wherever they point, and a /workspace path that is no mount. Encoded and look-alike separators stay part of a name. Place is only a mapping: the store's fence enforces the access. session.Access holds a turn's actor, view and place. It has no exported fields and one constructor, so a tool cannot be built from a principal string. Owner gives the user's own actor without the fence. Assisted-by: Claude:claude-opus-5-5 * Build a chat's view from its folders and describe it BuildView took the home of the principal as the folder at /workspace/home. A chat whose agent has a folder needs that folder there, at the agent's mode, and its own chat folder beside it. BuildView now takes the primary folder and the chat folder. The chat folder is mounted at /workspace/chat, read and write; the name chat is reserved like the skill layer names. The store caps each mount at the actor's mode, and a fenced actor gets the shared folders read only. Every caller passes the home and no chat folder, so an unscoped chat keeps today's view. LayoutPrompt takes a ScopedPrompt. A scoped chat hears only of its folders: the agent's folder by its name and mode, with a line that it cannot see the user's other files, the chat folder and where its working files go, and the shared folders. It gets no hint to build a page, because pages live outside its folder. An unscoped chat keeps today's text. Assisted-by: Claude:claude-opus-5-5 * Find a workspace node by its ID A caller that keeps a node ID, such as the folder of a saved agent, had no way to ask the store where that node is now. It had to search the journal and then list folders, which costs one query per folder in a large home. Store.NodeByID returns a live node at its current path, so a rename or a move of the node or of a folder above it is followed. It answers ErrNotFound when the node or a folder above it is deleted, and when the actor cannot read it; a fenced actor finds only nodes inside its fence. Both stores implement it and the shared suite checks it. The remote store of the Sandbox add-on refuses it, like its other calls. Assisted-by: Claude:claude-opus-5-5 * Name the work folder of a scoped chat at /workspace/chat A chat whose agent has a folder keeps its chat folder in the home, but sees it as a mount of its own at /workspace/chat. Its work folder is then /workspace/chat/work, not a path under /workspace/home. workfiles reads /workspace/chat as the chat folder: a helper file under its work folder is working, a script beside the attachments is a stray helper, and a folder named chat in the agent's folder is an ordinary folder. ScopedPrompt steers the model to that work folder and sends the deliverables to the agent's folder, or to the chat folder when the agent may only read. It says nothing of pages or of the settings folder, which are outside the agent's folder. The chat picks the text by its view. Assisted-by: Claude:claude-opus-5-5 * Look up the folder of an agent by node The folder resolver searched the journal of the home and then listed folders to find where an agent's folder is now. The stores can now find a node by its ID, so the resolver asks them directly and the search is gone. Assisted-by: Claude:claude-opus-5-5 * Resolve the file and media tools through the chat's access The file tools mapped paths to the user's home and acted as the chat's actor, and the media tools did the same through files.HomePath. A chat whose agent has a folder must reach only its folders, and search must start in the agent's folder, so the count of documents still being indexed cannot count files elsewhere in the home. files.Service.Tools and media.Service.Tools take a session.Access. Every path goes through its place and every call acts as its actor. A write to a read-only folder is refused before the store sees it. A search with no path starts at the primary folder, and in a scoped chat also looks in the chat folder; the pending count is taken below that root. files.HomePath is removed. UnscopedAccess builds today's access of a chat (the home and the shared folders), and the studio service takes the turn's access from one function, turnAccess, which gives that access until the chat access resolver replaces it. The new specs run the paths that try to leave the folder (parents, absolute and doubled paths, encoded and look-alike separators, NUL, other cases) through every file tool and the media tools, and check that nothing outside the folder is read, named or changed, and that search counts no pending file outside it. Assisted-by: Claude:claude-opus-5-5 * Resolve the access of a chat at every turn A chat whose saved agent has a folder must reach only that folder. Up to now every chat got the user's actor, which reaches the whole home. The chat's access is now resolved from the stores at every turn start. With no agent folder it is the actor and the view of today. With a folder the actor is fenced to the agent's folder at its mode, the chat's own folder read and write, and the shared folders and the skill layers read only; the chat's folder is made before the fence, because a fenced actor cannot make it. A sub-agent takes the folder of its parent's agent, and its own agent's folder inside it. A folder that is deleted, unreadable or not chosen refuses the chat with ErrAgentFolderMissing; it never falls back to the whole home. A chat records whether its agent had a folder, so a chat whose agent was deleted is refused too. CreateAs refuses such an agent at once. session.Access carries the actor and the view, has no exported fields and one constructor. Open takes it, the turn tools are built from it, and an open chat compares the fence as well, so an edit of the agent restarts the harness at the next turn on any frontend. The person's uploads and renames use the owner's actor, without the fence. The files a command changed are read as the chat can read them. Nothing is kept between turns, so frontends cannot disagree. Assisted-by: Claude:claude-opus-5-5 * List a scoped chat's files by its place in the prompt The turn prompt lists the chat's files with the paths the model uses. For a chat whose agent has a folder those paths come from its mounts, and a file the chat touched outside its folders, for example before the agent got a folder, must not be named. Manager.FilesIn is Files with a place. For a scoped place, each file is named by its mount (/workspace/home for the agent's folder, /workspace/chat for the chat folder) and a file outside every mount is left out. Other places give what Files gives. The prompt's file list uses the turn's place; the chats API keeps the user-wide list. Assisted-by: Claude:claude-opus-5-5 * Answer 409 when an agent's folder is missing A chat with a saved agent whose folder is missing or not chosen does not start. The chat endpoints now say so with 409 and the type agent_folder_missing, both when the chat is created and when a message is sent to an open chat, instead of a server error. The agent docs say what a chat with a folder reaches, when a change of the folder applies, and that nothing is kept between turns. Assisted-by: Claude:claude-opus-5-5 * Point a scoped chat at rules and work folders in its own folders The rules nudge walked from the chat folder up to the home root and named AGENTS.md files there, and the stray-helper note named the work folder under /workspace/home. A chat whose agent has a folder must hear only of its own folders. The nudge takes the turn's access: it reads paths through the place, starts at the primary folder (the agent's folder) and stops there, so it never points above the folder or into the chat folder mount. The helper note names /workspace/chat/work/ in a scoped chat, and a sub-agent of a scoped parent gets the scoped work folder text. Assisted-by: Claude:claude-opus-5-5 * Find workspace actors built outside the chat access An actor built from a principal has no fence and reaches the whole home. A spec now parses the studio service, the command runners, the add-on host operations and the application wiring, and fails on a workspace.Actor literal, a files.UserActor call or an Actor(principal) call in a function that is not on the allowlist. Each allowed entry says why: a host read of the user's settings, a user surface, or a caller that a later change moves to the chat's access. An entry that builds no actor any more fails the spec too, so the list stays exact. Assisted-by: Claude:claude-opus-5-5 * Build the expected view of a chat with the view's folders The spec of a chat without an agent folder compared its view with BuildView called with the old arguments, so the test package did not compile after the merge of the view builder. It now passes the home as the primary folder and no chat folder, which is the view of an unscoped chat. Assisted-by: Claude:claude-opus-5-5 * Give every file tool of a turn the chat's resolved access The resolver of a chat's access built the view of a scoped chat itself, with no shared folders, while every other chat got its view from the session manager. And the file tools, the media tools, the chat's file list in the prompt, the rules nudge and the work folder lines each asked for an access of their own, the view of the whole home. A chat whose agent has a folder therefore had a fenced actor but home-relative paths: it reached its folder only through paths such as /Projects/Acme/a.txt, and its prompt named the home. The session manager now builds every chat's view: UserAccess mounts the home, and the new ScopedAccess mounts the agent's folder at home, capped at the fence's mode, the chat folder at chat and the shared folders read only. It refuses an actor without a fence, and a folder outside the fence is an error, never a view of the home. The resolver calls it with the innermost folder, so a sub-agent of a saved agent still works in its own folder. The access that the resolver builds once at the start of the turn now goes down to every consumer. A sub-agent of a saved agent acts for its parent chat with the same access (Access.ForChat), and a generic sub-agent gets its tools from the parent's access. The seam that gave the unscoped access, and the files service's own view builder, are removed, so a new consumer cannot build a view by mistake. A turn whose access has no folder gets no tools rather than the home. A scoped chat now sees its folder at /workspace/home and its chat folder at /workspace/chat in its tools, its search, its prompt and its work folder lines. A chat whose agent has no folder is unchanged. Assisted-by: Claude:claude-opus-5-5 * Find chat views built outside the chat access The turn's access is resolved once and handed down, but nothing stopped new code from building a view of its own, which shows a scoped chat the whole home. A second scan now parses the same sources as the actor scan and fails on a call of BuildView, SkillLayerMounts, NewAccess, UserAccess or ScopedAccess, or on a store's View, in a function that is not on its allowlist. The resolver is the one allowed caller; the host bash, the sandbox runner and the add-on host operations are listed until they take the chat's access. A stale entry fails the scan too. Assisted-by: Claude:claude-opus-5-5 * Keep a sub-agent inside its parent's folder A saved agent started from a scoped chat could name a folder outside the chat's own, and the child was made before its first turn failed with a message about a missing folder. spawn_agent now checks the agent against the chat's agent from the stores before it makes the child: no folder is fine, the same folder or one inside it is fine, anything else fails with "this agent works in another folder than this chat". The child never has more reach than its parent, in folder or in mode. The ScopedAgent flag of a sub-agent was reset to what its own agent had at each turn. A child of a scoped chat with an agent without a folder lost the mark, so deleting the parent's agent would have given that child the whole home. The flag now follows both folders. New specs cover a generic child, a saved-agent child outside, inside and at the parent's folder with the lower mode, a child without a folder, and the work folder wording of a child of a read-only or read-write parent. Assisted-by: Claude:claude-sonnet-5-5 * Show agent folders in list_agents and limit them by scope list_agents gave a scoped chat every saved agent, including ones that spawn_agent would refuse, and told the model nothing about where an agent works. Each entry now carries the name of the agent's folder and its mode, or folder_missing when the folder is deleted or not chosen. The path is left out, since it would show the folders above the chat's own. A chat whose agent has a folder lists only the agents that fit under that folder, by the same check spawn_agent makes. The docs for saved agents as sub-agents and for the agent folder describe both. Assisted-by: Claude:claude-sonnet-5-5 * Keep the triggers of a scoped agent to its folder A chat of an agent with a folder reaches only that folder, but its triggers still worked on the whole home. A file trigger could watch any folder, the rules of a run were read from the home root down with the user's actor, the first message named home paths, and a run whose agent's folder was gone fell through to a failed chat start after the host had already read the home's rules. The trigger tools of a scoped chat could also list, change or propose triggers that reach the whole home. The agent's folder now bounds every step: - Saving a file trigger (create, update, edit, confirm) refuses a folder outside the agent's folder, and a trigger of an agent whose folder is missing or not chosen. - Each run checks the agent's folder before it reads anything. A missing or unset folder skips the run with "the agent's folder is missing" and switches the trigger off; a watched folder that is not inside the agent's folder does the same with its own reason. No chat is made and the owner is told. - The folder check and the rules are read with an actor fenced to the agent's folder, read only, so no AGENTS.md above it is read. The rules of a schedule run start at the agent's folder. The first message names folders and the file as the chat sees them, under /workspace/home, and the rules nudge of the run's chat counts those rules as given. - In a scoped chat the trigger tools read folders as paths of the chat's place, refuse one outside the agent's folder, and see only the triggers of that agent. The trigger watcher takes the service's administrator actor, made once next to the change feed's, and the trigger functions leave the actor scan's allowlist. Assisted-by: Claude:claude-opus-5-5 * Send connector replies through the chat's access The files a connector reply sends were listed from every change made in the chat's name and read with the user's actor, so a reply of an agent limited to one folder could send a file from anywhere in the home that some host-side write had attributed to the chat. A message to an agent whose folder was missing made or reopened a chat, failed to start it, and answered with a generic error. A reply now resolves the chat's access once, lists the turn's files through its place (a file outside the chat's folders is left out) and reads each one with its fenced actor. A file the access cannot reach is skipped without being named. Before it makes a chat, a message checks the bound agent's folder; when it is missing or not chosen, the sender gets one reply, "This agent cannot work right now: its folder is missing.", the refusal is logged and the binding stays on. The same reply covers a folder that goes away between the check and the turn. readChatFile leaves the actor scan's allowlist. Assisted-by: Claude:claude-opus-5-5 * Name a read-only refusal of a commit by its guest path The store names an upper entry that a read-only mount refused by its path in the view (/home/x), not by its store path. The note that a command's output ends with took every path but an outside-view one for a store path, so it told the model that "/home/x was not saved", a path the guest does not have. A path that no mount holds but that starts with a mount name is now taken as a path of the view and gets the /workspace prefix. Assisted-by: Claude:claude-opus-5-5 * Take the actor and view of command runners from the chat's access The host bash and the sandbox runner made their own actor and view: the host bash a user actor from the principal and the view of the whole home, the sandbox runner a plain actor by default and the view from its own mount requests. Neither knew the chat's agent folder, so a command of a scoped chat could reach the whole home. The runner now has no default actor or view. Options.Actor takes a context and returns an error, and Options.View returns the view itself; both are asked at every call. A view of another actor than the chat's is refused, and a sandbox whose actor or mounts changed is made again, so an agent's new folder or mode applies from the next command. A failing resolver fails the call, also with a sandbox running. The server wires both hooks to the chat's resolved access: the new Service.CommandActor and Service.CommandView, the latter refusing an actor that is no longer the chat's. Access.SandboxView adds the skill layers to the turn's view, at the names the file tools use. The host bash refuses a fenced actor, at the tool and again at each call, as a command on this machine reads what the server can read. The Sandbox add-on passes a label actor and its home view: the host binds each workspace operation to the call's chat. The lane 5 entries leave the actor and view scan allowlists. Assisted-by: Claude:claude-opus-5-5 * Offer no host bash to a chat whose agent works in one folder A command of the built-in bash runs on this machine and reads every file LocalAI can read. No workspace rule confines it, so a chat whose agent works in one folder cannot have it, whatever chats_host_exec says. The tool's build now refuses a fenced actor, so the chat gets no bash, its prompt says nothing runs commands, and the shell group of the Tools menu gives the reason: the agent works in one folder and runs commands only in the Sandbox add-on. Sub-agents of such a chat have the fenced actor too. The docs of saved agents and of the commands on this machine state the rule and the Sandbox layout of a scoped chat. Assisted-by: Claude:claude-opus-5-5 * Tell a scoped chat where its Sandbox commands start and what they keep The commands block of the prompt told every chat with the Sandbox that a command starts in /workspace/home, the user's home, and that what it saves there or in a writable shared folder is kept. In a chat whose agent works in one folder, /workspace/home is that folder, the chat folder is /workspace/chat and the shared folders are read only. The block now says so, and with a read-only folder it names only /workspace/chat as kept. Assisted-by: Claude:claude-opus-5-5 * Name a scoped chat's attachments where its commands see them The model learns of an attached file by its guest path, which was always /workspace/home/Chats/<chat>/<file>. In a chat whose agent works in one folder, /workspace/home is that folder: the file and media tools still found the file through the place's chat alias, but a command sees the chat folder only at /workspace/chat, so the path named nothing for it. The text the model gets now names a file of the chat folder at /workspace/chat/<file> in a scoped chat, through the chat's place: when a message is sent, queued or injected, in the summary of the chat, and in the model state rebuilt after an edit, a regenerate, a fork or an import. What is stored keeps the home spelling, which SplitMessage reads back, and an unscoped chat is unchanged. Assisted-by: Claude:claude-opus-5-5 * Remove the duplicated allowlist entries of the actor scan Assisted-by: Claude:claude-opus-5-5 * Read and write the folder of an agent in the agent helpers The agent API now answers an agent's folder with its path, mode and state, and a write keeps the stored folder unless it names one. The page helpers learn that shape: the folder field of a save is sent only when the person changed it, an empty path clears it, a missing or unset folder that the person did not replace is kept, and the mode is read unless write was chosen. Small helpers say whether a listing entry can be chosen (not a folder LocalAI manages, not a shared folder), which folders agents use for the Files page marker, and whether a chat error is the missing-folder conflict. Assisted-by: Claude:claude-opus-5-5 * Move the folder walk of the Move dialog into a folder picker The agent editor needs the same walk through the person's folders as the Move dialog, so the breadcrumb and the folder list move into FolderPicker, with their styles, and the Move dialog draws it. The picker can show a folder as one that cannot be chosen, with the reason next to it, and a folder that cannot be read now offers to try again; a folder still loading says so instead of an empty list. Assisted-by: Claude:claude-opus-5-5 * Choose the folder of an agent in the agent form The agent form gets a Files section after the instructions: All my files, or One folder chosen in the folder picker, and whether the agent's chats can read the folder or read and change it. The picker shows the folders LocalAI manages as ones that cannot be chosen, and Home itself can be chosen. A folder that was deleted, or an imported agent whose folder was not found, is said in place with an offer to choose another; the rest of the form still saves and keeps it. A save sends the folder only when the person changed it, so editing another field never touches it. Picking One folder and choosing nothing stops the save, as it would otherwise save an agent on all the files. The Export section now downloads the file the server writes, which names the folder, and says so. Assisted-by: Claude:claude-opus-5-5 * Show the folder of an agent on the agents list and its page An agent with a folder shows it in the list's line and on its page, with its access in words and a lock when its chats can only read it. A folder that is gone, or an agent with no folder chosen yet, shows a warning that opens the form; the agent's page also says so above its facts and offers to choose another folder. Assisted-by: Claude:claude-opus-5-5 * Mark the folders that agents work in on the Files page A folder that a saved agent works in gets a small marker with the agent's name, or the number of agents, and a tooltip that names each one with its access. Inside such a folder, a line over the list says the same. The page reads the agent list it can already fetch, so the files API is unchanged, and the page still shows all the files. Assisted-by: Claude:claude-opus-5-5 * Show a chat's folder and say when its agent's folder is missing A chat with an agent that has a folder shows the folder next to the agent in the message box, with a lock for read only, and the Tools menu says which files the chat's tools reach. When the folder is gone, the chip says so and opens the agent's form. A chat whose agent's folder is missing does not start, and the server answers with a conflict. The message box now says that in plain words, keeps the message, and offers Edit agent, instead of the server's text. Assisted-by: Claude:claude-opus-5-5 * Test the folder of an agent across the web interface The agent stubs now list folders by path, read a written folder back as the server does, export a version 2 file for an agent with a folder, import one whose folder is not found as unset, and refuse to start a chat whose agent's folder is missing. The specs choose a folder and see it on the list, switch the access, leave an unchanged folder out of the save, clear it, keep and replace a missing folder, keep Chats and LocalAI out of the picker, retry a folder that cannot be read, see the Files marker, the chat's chip and Tools line, the missing-folder chat error with Edit agent, and the import warning. A render smoke opens the picker on the real server, and one spec checks that the copy names no internal path. Assisted-by: Claude:claude-opus-5-5 * Describe the agent's folder in the web interface The agent docs said what the folder field does in the API. They now also say where the web interface sets it, how the agents pages, the Files page and a chat show it, and what a chat whose folder is missing offers. Assisted-by: Claude:claude-opus-5-5 * Record the chat an add-on call was made for An add-on's workspace operations run as the user of the live request, with no idea which chat made it. Only an action carries a chat, and only as a key in its resource ID; a read tool such as the Office add-on's read-docx carries none. So a chat that should reach only one folder could reach the whole home through an add-on. The in-flight record of a request now keeps, next to the envelope, a binding to the chat the request was made for: the user's principal and the chat ID. It is host-side only and never a field of the envelope, which installed add-ons decode with unknown fields refused. A context carries the binding from the chat turn to the place that records the request. The broker gives each host operation the chat and the scope of its live request. An operation ID that requests of two chats share is not live, so neither chat is trusted. Assisted-by: Claude:claude-opus-5-5 * Keep the chat binding of a runtime call on the host The runtime client records each call's envelope for the host operation channel. It now records the chat binding too when the call's context carries one, so the add-on's host operations know which chat made the request. The envelope sent to the add-on is the same bytes with or without a binding: a spec checks that the body of a bound call equals the body of an unbound one and still decodes with unknown fields refused. Assisted-by: Claude:claude-opus-5-5 * Carry the chat binding in a forwarded add-on request A frontend that is not the add-on owner forwards an add-on call in a signed request. The chat the call was made for now rides in that request as a signed field, chat, and the owner puts it back on the context of the call it serves, where the runtime client records it. A changed, added or removed binding fails the signature check, and a signed but incomplete one is refused. A request that no chat made has no chat field and signs as before. An owner that does not know the field refuses a forwarded call that a chat made, so the owner must be upgraded before the frontends. Assisted-by: Claude:claude-opus-5-5 * Bind every add-on tool call of a chat to the chat The chats consumer ran an add-on tool with the conversation ID only, which the owner used to resolve a selection and, for an action, as the key of the add-on's state. Nothing told the host which chat a read tool or a change came from. The tool adapter now has ExecuteChat, which takes a ChatCall (the chat's user and ID, from the chat turn's own record) and binds the call to the chat on the host side for every tool kind: a read with no resource, an action, and a change made at once. The chats adapter refuses a call that names a conversation without that binding, so a chat's call cannot be made unbound by mistake. Other consumers, such as the OpenAI-compatible route, keep calling without a binding. Assisted-by: Claude:claude-opus-5-5 * Run add-on workspace operations with the chat's access The workspace operations of add-ons (materialize, commit, changes, export and import) worked on the whole home of the request's user. A chat whose agent has a folder could therefore read and write any file through the Office or Sandbox add-on. They now resolve their access from the chat binding of the live request, through a new Access hook that the chats service answers (Service.AddonAccess). A chat's call gets the chat's access, as its file tools do: in a chat whose agent has a folder, the add-on's "/" is that folder, /workspace/chat names the chat folder, the agent's mode applies, and paths resolve through the chat's place, so a parent reference is refused and an encoded separator is part of a name. The mounts go through Access.SubView, which builds a view only inside the access, for its fenced actor. When an add-on mounts its "/" at home, the host adds the chat folder at chat, so the Sandbox sees the chat's layout without a change. Changes list only what the access may read, and a commit entry outside the view is a conflict. A call whose chat cannot be resolved is refused and never runs user-wide. An action request without a binding is resolved by its chat key, as before, and refused when it names no chat. A call that no chat made (an add-on page, the OpenAI-compatible route) still works on the whole home, through Manager.PersonAccess. The four lane 6 entries leave the actor scan and the view scan. PersonAccess joins the view scan's matcher, with AddonAccess as its one allowed caller. An end-to-end spec runs the real Office and Sandbox add-ons in a scoped chat. Assisted-by: Claude:claude-opus-5-5 * Build the chat access of the file index route test files.Service.Tools takes a session.Access since the chat access change, so the route test of the text index passed a bare actor and its package did not compile under the auth tag. The test now builds the access as the chats service does for a chat whose agent has no folder: the user's home as the primary folder of the view, then session.NewAccess. The assertions are unchanged. Assisted-by: Claude:claude-opus-5-5 * Test the folder of an agent through every surface of a chat The specs of the folder feature each test one surface. This suite runs one chat of an agent limited to a folder through all of them at once, on an indexed SQL workspace: the file and media tools, the search and its pending count, a command of the Sandbox in a fake sandbox, a read call and an action call of an add-on through the real workspace operations bound to the chat, a generic and a saved sub-agent, the trigger tools, a file trigger run, a connector reply, a renamed folder, a mode change, an edit that narrows the folder (also seen by a second frontend) and a deleted folder. The files outside the folder hold a token that the scripted model never writes. After each spec the suite collects every text a person or a model can see: tool results and errors, prompts, messages, transcripts with their cards, live events, chat file lists, tool panels, notifications, connector replies and files, the add-on's data directory and the connector log. The token must be in none of them, and the files outside must be unchanged. A control spec runs the same probes from an agent without a folder and checks that they do find the token, so the probes and the collection cannot pass by seeing nothing. Assisted-by: Claude:claude-opus-5-5 * Complete the docs of the folder of an agent Each change of the folder feature documented its own part. This makes the pages one account of it: - Saved agents: the missing and unset states in one bullet, what the folder does not limit (MCP servers, web tools, collections, pages), that the Files page stays user-wide, when an edit applies, the downgrade caveat, and the folder as a stateless row of the cluster table. The Sandbox of a scoped chat mounts the agent's folder and the chat folder only, as the add-on asks for them; the page said it also had the shared folders and skills. - Chats: the chat folder at /workspace/chat for the model, sub-agents of a scoped chat, and commands only in the Sandbox. - Add-ons: the Sandbox and Office sections say what / is in a chat whose agent has a folder. - First agent: the optional folder step and the "Folder missing" case. Assisted-by: Claude:claude-opus-5-5 * Draft the PR description and release note of agent folders No release notes file exists for the next release yet, so the draft text lives next to the spec and the plan. It carries the release note paragraph with the downgrade caveat and the upgrade order of a cluster. Assisted-by: Claude:claude-opus-5-5 * List the chat binding specs in the per-report add-on inventories The chat binding change added five specs to the gateway and runtime packages and named them in the case lists of the gateway, artifacts and apps suites. These three suites also keep one case list per Ginkgo report, and the verifier compares each report with its own list. The new names were missing there, so the three suites failed with an inventory mismatch. A dry run of every Ginkgo suite's commands now lists the same It names as each report's inventory, in both directions. Assisted-by: Claude:claude-opus-5-5 * Hide stale paths from a fenced actor's history A folder moved into a fence makes its parent identities readable. Their historical paths can still name locations outside the fence. Hide each historical side when its readable parent's current path differs. Reuse the generic title when filtering hides a side. Keep the journal and unfenced history unchanged so Undo uses identities. Assisted-by: nib:gpt-6.1-sol * List the chat binding cases in Tables tools The Tables tools runner includes every adapter spec in its output. List the four chat binding cases so the exact inventory accepts them. Assisted-by: nib:gpt-6.1-sol * Keep shared agent folders unset in exports A followed folder outside the home cannot round-trip through a home path. Export its mode with an empty path so import warns and stays fail-closed. Responses keep public shared paths without exposing other internal paths. Distinguish deleted scoped agents from unscoped agents in the guidance. Assisted-by: nib:gpt-6.1-sol * Refuse scoped chats over the folder limit Keep every required shared root in each intersecting fence. Refuse creation and turn access when the complete set exceeds 32 roots. Reserve a chat root before its folder exists and fence listings empty on refusal. Propagate shared enumeration failures instead of omitting roots. Map capacity refusals to a fixed 409 response and give connectors a safe capacity message. Check boundaries, retries, background access, and HTTP handlers with focused regressions. Assisted-by: nib:gpt-6.1-sol * Verify unset imports refuse chat startup Assert the folder-specific refusal without a harness start or saved chat. Clarify public response paths and unset exports in the API metadata. Assisted-by: nib:gpt-6.1-sol * Keep the folder retry test under user control A background refresh consumes the one-shot successful response before this test observes its load error. Isolate the mocked Files page from the live workspace stream and agents list. Keep reads failing until the error assertions pass, then allow the actual Retry click to recover. Check that Retry reads again and removes the error, without changing the existing assertions or their timeouts. Assisted-by: nib:gpt-6.1-sol * Test and document folder capacity refusals Use the existing Ginkgo suites for capacity regressions. Exercise a successful turn, refusal after shares change, and a retry through a second service on the same stores. Check that refusal leaves no claim or pending message. Verify that connectors send one fixed refusal and that triggers stay enabled after capacity failures. Document the 32-root budget and the all-required-roots-or-refuse contract. Assisted-by: nib:gpt-6.1-sol * Control crashes in the restart budget test The crash fixture exits after 100 ms, before startup necessarily finishes. A busy runner can fail the readiness handshake instead of testing restarts. Start a normal fixture and kill each published incarnation explicitly. Keep the exact restart count and persistent failed-state assertions. Assisted-by: nib:gpt-6.1-sol * Check capacity test cleanup errors Assert service and workspace cleanup through Ginkgo. Keep service cleanup before workspace cleanup and report close failures instead of discarding them. Assisted-by: nib:gpt-6.1-sol --------- Co-authored-by: Ettore Di Giacinto <mudler@localai.io>	2026-11-01 18:30:08 +01:00
mudler-agentandEttore Di Giacinto	e45dc5e9f7	feat(addons): installable add-ons foundation and the Tables add-on (#12702) ... * feat(addons): add the add-on runtime, navigation and first-party add-ons Add the add-on runtime to LocalAI: manifests, the host operation broker, admin gating by account role, the add-on UI bundle builder and the SDK for add-on pages. Move the navigation to Chat, Models, Add-ons and Settings, with pinned add-ons in the sidebar and an Add-ons drawer. Ship the first-party add-ons (voice, face, fine-tuning, quantization) as packages for linux/amd64, linux/arm64 and darwin/arm64. Intel macOS (darwin/amd64) is enabled in the platform files. Squashed from the review branch. The tree is unchanged; the pre-squash history is kept on a local backup branch. Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(gosec): tighten file modes and annotate false positives Write job state, configs and imported models with mode 0600, clean the paths that are read from disk, and mark the route tables, the header name and the retry jitter as reviewed false positives. Assisted-by: Claude Code:claude-sonnet-5-5 gosec Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): keep API keys off recovery mutations and same-site cookies POST /api/addons/dispatch forwarded the recovery and update mutations to the owner for any administrator key, which skipped the browser-session rule of their own routes. Refuse those actions there. Also apply the same-origin rule to the legacy token cookie, not only the session cookie, because the global CSRF check lets same-site requests through. Do not fail the start of LocalAI when an add-on library cannot be refreshed; log it and keep the installed add-ons up. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): refuse a reinstall that would migrate retained data unbacked An upgrade takes a verified backup before the new package migrates the data. A reinstall over retained data has no running generation to stop, so the new package would migrate it without one. Refuse a reinstall whose data format differs from the retained one. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): release the manager lock while a release is fetched Submit held the state lock across the catalog lookup and the package download, so the apps list and status reads stalled for the whole install. Serialize Submit and Reconcile with their own lock and drop the state lock around the fetch only. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): kill an add-on only after three missed health probes One slow 100 ms probe killed a busy add-on and dropped the work it was serving. Require three misses in a row. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(ui): move settings under the operate hub The Operate hub already has Settings as a tab, so the sidebar no longer shows a separate Settings entry. The /app/settings route stays, and the hub tab still reaches it. The navigation test now expects Chat, Models and Add-ons as the primary items. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): accept same-host browser requests that carry no fetch metadata Browsers do not send Sec-Fetch-* headers over plain HTTP on an address that is not localhost, so every add-on request from a LAN address was refused as cross-site. Keep refusing a Sec-Fetch-Site value other than same-origin. When the header is absent, accept the request only if its Origin, or failing that its Referer, names the same host and port as the request. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(ui): show the server's reason when an add-on request is refused A 403 or 400 answer showed a generic message and hid the reason in the response body, so a refusal by the browser guard could not be told from a missing permission. Show error.message from the body as the server sent it, and keep the generic text when the body has none. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): run the add-on owner in the normal binary The owner was only enabled when an embedding host set the add-on config, so a normal run answered every add-on request as unavailable. Add --addons-enabled (default true) and --addons-ownership-mode (default named-user, or local-owner; anything else stops startup). The node is its own owner: state lives under the data path, and the carrier uses loopback keys made at each start and kept in memory. --addons-enabled=false turns the owner off completely. Named-user mode needs the account database. With authentication off the owner stays off and a warning says how to use local-owner. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): keep the loopback owner address stable across restarts The single-node loopback transport took a new ephemeral port at each start. The owner stores its address in its identity file and refuses to start when the address differs, so every start after the first failed with "invalid addon owner configuration". Choose the port once, keep it in the add-on state root (loopback-port, mode 0600) and reuse it. If the port is taken at a later start, stop with an error that names the port and --addons-enabled=false, because another port would break the identity check. The keys and certificate stay in memory. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): let add-on pages keep the host modules they were written against A page written for the web UI imports React, the router, i18next and a few shared components. The add-on builder refuses a bundle that holds a host file, so moving such a page into an add-on meant rewriting it. Add a compat mode to the shared builder. It answers those imports from a directory of stand-ins that read the SDK, bundles the dynamic import of the page code into the one output file, and collects the style sheets the page imports. A relative import that is not in the add-on's own source resolves to the file at the same path under the compat directory. Widen the SDK for these pages, without a version change: more host components (spinner, modal, lightbox, model picker) and hooks (models, resources, voice profiles, operations, MCP client), a style on icons, the icon names the pages draw, sdk.navigation.openApp to open a page of the app (only addresses under /app, and the way back as the only state) and sdk.portal. The shell passes the query string to the page. The stand-ins cover the router (the tab in the path, the model in the query), the translator over the host locale files, the core API calls through sdk.core.fetch, and byte copies of the pure helpers, with tests that keep the copies equal to the originals. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): ship Studio and Talk as add-ons instead of built-in pages Studio and Talk were compiled into the web bundle and always listed in the Add-ons drawer. They are add-ons now, like Voice, Face, fine-tuning and quantization: a person installs and removes them, the drawer lists them only while they are installed, and they are packaged the same way. Move the pages, their components, hooks and helpers into addons/studio and addons/talk. Each has a manifest, a UI bundle, a release platform matrix and a catalog template, and is built by the compat mode of the shared builder. The core API stays where it is: the pages call it with the signed-in person's session. The history keeps its browser storage keys. The unit tests of the moved helpers move with them. In the core, drop the two pages, the Create group of the sidebar (Chat joins Home and Models in the old layout), the built-in catalog entries (the catalog is empty) and the talk locale namespace. The old addresses (/app/studio, /app/talk and the generator links) redirect to the add-on pages, with the model as ?model=. The Home /studio command is offered only while the Studio add-on is installed and opens it. The release workflow and its tests now list seven add-ons. Assisted-by: Claude Code:claude-sonnet-5-5 go node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): run the Studio and Talk specs against the add-on bundles The pages are add-ons now, so a spec that draws one installs the real built bundle first: the apps list names it and its module and style sheet are served from the build output, the way the add-on owner serves them. studio-addon.js holds that helper, and the Studio and Talk fixtures call it. Update the specs for the new addresses (/app/addons/studio/studio, the model as ?model=), the session permission the add-on route needs, the legacy redirects, the Home /studio command that appears only while the add-on is installed, and the sidebar without a Create group. Add specs for the add-ons themselves: every tab draws with no script error, the shell titles the page once, the old addresses say so when the add-on is not installed, a button of the page reaches a core page with the way back, and the drawer lists both only after they are installed. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(ui): centre the icon of a built-in tile in its icon box The drawer drew the icon of a built-in tile (Studio's palette was one) in a bare 40px box. Only the placeholder box was laid out as a centred grid with the 20px size, so the real icon sat in the top-left corner at the size of the page text. Give the built-in tile the same classes as the placeholder box, and check in a browser that the icon is centred. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * docs(addons): describe Studio and Talk as add-ons Replace the built-in list (now empty) with the Studio and Talk add-on sections, the new targets of the old links, the Home command, and the seven packaged add-ons. Describe the SDK additions the pages use: components, hooks, icons, openApp and portal. Say on the Studio page that it is installed from the drawer. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): click the shell title in the Studio slash-key spec The add-on shell titles the page, and the Studio overview no longer draws a second title, but the generator tabs keep theirs, so a bare h1 locator matched two elements. Click the first, which is the shell's. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): read the loopback port file through os.Root The persisted port file was read with a path built from the add-on root, which gosec reports as a file inclusion through a variable. Open it through os.Root so the name cannot leave the root, even by a symbolic link, and require a regular file with no group or other access. A looser file now fails closed instead of being trusted. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): expect Settings under the Operate hub, not the sidebar Settings moved out of the sidebar into the Operate hub. The navigation spec still expected a sidebar link. Assert that the sidebar has no Settings entry, and that the Operate hub opens Settings as a tab. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): drop Settings from the 404 places Settings is a tab of the Operate hub and not a destination of its own, so the 404 page does not list it. Assert that it is absent. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): drive the media history and TTS specs through the Studio add-on The image, video, sound and speech generators are pages of the Studio add-on now, and the old addresses redirect to it. Install the add-on with the Studio fixtures, open its pages and use its compose card, so the specs run against the page that exists. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): count the first-run steps, not every list item The recommended models are a list inside the second step, so counting all list items read 3 only while the models were still loading. Count the step elements, which does not depend on the load order. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): fail the node refresh by state, not by call count The spec served the list to the first request and failed the rest. The first request is not always the one from the page, so the page could get the failure first and show no list. Serve the list until the page shows it, then fail the refreshes. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): default to local-owner when auth is off A server without authentication has no accounts, so named-user left the add-on owner off. Resolve the unset mode in one place: local-owner when authentication is off, named-user when it is on. A flag or environment value still wins, and an unknown value is still refused. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): register an official add-on library by default Add gallery/addons/index.yaml, a YAML index of the four first-party add-ons (fine-tuning, quantization, voice, face) in the library format. The entries come from addonpkg catalog over locally built linux/amd64 packages, so the digests pin those images. On the first start, when the owner has no sources.json, register the raw GitHub URL of that index on master as the "official" library and write the file. The file is then the record: a library the admin removes stays removed, and an existing file is never changed. --addons-official-library=false skips the default. Assisted-by: Claude Code:claude-sonnet-5-5 go node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * docs(addons): document the ownership default and the official library Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): list Studio and Talk in the first-party index Add the Studio and Talk entries to gallery/addons/index.yaml next to the four existing ones. They come from addonpkg catalog over locally built linux/amd64 packages, so the digests pin those images. Assisted-by: Claude Code:claude-sonnet-5-5 go node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): expect Studio and Talk in the official index The official index now lists six add-ons. Update the test that decodes it so it accepts Studio and Talk. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): add a real icon to each first-party add-on Each icon is a 256 by 256 PNG: a rounded square in one colour of the UI kit palette with a white outline glyph from the kit sprite. Fine-tuning uses sliders, quantization layers, voice waveform, face user, studio palette, talk phone and tables database. They were rendered with headless Chrome from the sprite paths. Assisted-by: Claude Code:claude-sonnet-5-5 chrome Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): ship a committed icon.png instead of the generated square The shared UI builder and the Tables builder copy ui/icon.png from the add-on source tree to the package unchanged when the file exists. They write the generated placeholder only when it does not. Add a fixture with an icon and a test for both cases. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): list the tables add-on in the first-party index Add the Tables entry to gallery/addons/index.yaml next to the six existing ones. It comes from addonpkg catalog over a locally built linux/amd64 package, so the digest pins that image. The official index test now expects seven add-ons. Assisted-by: Claude Code:claude-sonnet-5-5 go node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): make the Voice add-on one page with tabs The Voice add-on had four pages: recognition, library, create and speech, and the drawer listed two of them. It now has one page, "voice", and one drawer entry. Recognition, Library, Text to speech and From a recording are tabs of that page, drawn with the same tab strip the recognition page already used. The tab is the first path segment (voice/library), as in the Studio add-on, and the form that adds a voice is a view of the Library tab (voice/library/new). The old page names stay declared in the manifest. Each one redirects to its tab and keeps the query string, so saved links still open. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(ui): send the old voice routes to the Voice tabs /app/voice, /app/voice-library and /app/voice-library/new now open the matching tab of the Voice add-on page while the add-on is installed and running, and the core pages otherwise. The moved-page helper compares the first segment of the target with the declared pages, so a target can name a tab. The docs and the navigation spec list the new addresses. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): cover the Voice tabs and the old page redirects The add-on unit tests render the tabs instead of the four pages. The Playwright spec checks the tab strip, the address of each tab, the missing Library tab for a member, and that the old page addresses of the add-on redirect to their tab with the query string kept. The migration table test follows the new targets. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(studio): keep the model menu inside a narrow screen The Home model picker sizes its menu from the viewport, and assumes the picker sits at the page gutter. In the Studio composer card the field is further in, so on a 390px screen the menu of the Sound expansion picker ended 7px past the right edge. Size the menu from the field it opens under instead. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): build the add-on bundles once for the whole run Each worker built the Studio and Talk bundles into the same dist directory, and the build empties that directory first. A worker that started, or restarted after a failure, removed the files another worker was serving, so a Studio spec saw "the style sheet of the add-on could not be loaded". Build once in a global setup before the workers start. A run without the setup still builds per worker. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): register the worker when the add-node spec says so The mocked roster added the worker on the third read of /api/nodes. The shell and the page both read it, and which one asks first depends on load, so the page could take the new worker as part of the roster it opened with and never show it as found. The worker now joins after the page shows it is listening. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): hold the gallery answer until the skeleton is seen The spec delayed the answer by a fixed 800 ms and then looked for the skeleton. The assertion polls at growing intervals, so on a slow machine it could step over that window. The answer now waits until the skeleton has been seen, and the spec then checks that the skeleton goes away. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): give the PDF tag the time the other PDF specs have pdf.js and its worker load on first use. The other specs in this file wait up to ten seconds for the result of that load. The first one waited five, and missed the tag on a busy machine. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): build the Face and Fine-tuning bundles in the global setup The navigation spec serves the built Fine-tuning bundle, but nothing built it, so two specs failed on a fresh checkout when the dist folder was missing. The spec also built the Face bundle in a hook that every worker runs, and a build rewrites the folder the other workers serve. The global setup now builds Studio, Talk, Face and Fine-tuning once, before the workers start. The spec builds the two bundles itself only when it runs without the global setup. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): fix the Home answers in the stale pin spec The spec asserts that the page shows no alert. The Home page raises its own alert when the model list fails or a staging operation has failed, and both answers come from the shared test server. A slow reply or a failed install left there counted as an alert about the pin. The spec now fixes both answers, so the alert count tells only about the pin. The assertions are unchanged. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): read the server address in the add-node spec from the page The spec expected the register address to carry port 8089, so it failed on any other port. It now expects the origin the page was opened from. Assisted-by: Claude Code:claude-sonnet-5-5 node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): give the navigation routes spec its own catalog No page is built in today, so the catalog is empty and the three specs that expect the studio and talk entries failed on the list and on the pin seed. They passed only while Studio and Talk were built in. The spec now sets a catalog of two ungated entries for each example and restores the old one afterwards. The assertions are unchanged. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(cli): report a failed write of the MLX hostfile The tunnel callback ignored the error of os.WriteFile and set the hostfile variable even when the file was not written. It now logs the error and leaves the variable alone. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): discard the close error of the held listener errcheck flags the deferred Close of the listener that keeps the port busy. The test has no use for that error, so the defer drops it explicitly. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): move the add-on tool tests to Ginkgo The fine-tuning, quantization and add-on host library tests used t.Errorf, t.Fatal and t.Run, which the forbidigo rule rejects. They now use Describe, It and Gomega, with a suite bootstrap in each package. The cases and the assertions are the same. The tables in the host client and the tool schema tests keep one entry per case. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): move the host operation tests to Ginkgo The hostops tests used the testing package calls that forbidigo rejects. They now run as Ginkgo specs under one suite bootstrap. Every check and every per-operation case is kept. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): move the pin store tests to Ginkgo The pin service, file store, sweep and shared store contract tests used the testing package calls that forbidigo rejects. The store contract is now a function that registers its specs for each store, so the file store, the memory-only store and the database store run the same cases. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): move the remaining add-on tests to Ginkgo The built-in catalog, tool arguments, loopback carrier, host operation contract, packaging, application, config, CLI and endpoint tests used the testing package calls that forbidigo rejects. They now run as Ginkgo specs. The endpoint tests also drop the unchecked Close errors that errcheck reports when the auth tag is on. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): wait for the targeted Reinstall button before the install click The "generic deletion blocks targeted install at confirmation" spec dispatches a popstate to set the target node, then clicks Reinstall with a script click. The click can run before the targeted page has rendered or while the button is still disabled, so no install request is sent and the poll on the install count times out. It failed 1 run in 10 with two workers and on every retry in CI. The spec now waits for the button to be enabled first. The assertions are unchanged. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * chore(addons): refresh the voice package digest in the first-party index The Voice add-on became one page with tabs and got a new icon, so the digest in gallery/addons/index.yaml no longer matched the build. Render the entry again with addonpkg catalog over a locally built linux/amd64 package; the main page is now voice. The other entries are unchanged. Assisted-by: Claude Code:claude-sonnet-5-5 go node Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): wait for the target node's Reinstall button after the popstate The "generic deletion blocks targeted install at confirmation" spec dispatches a popstate to set the target node, then waits for a button named Reinstall and clicks it. Until React renders the targeted page, the page still draws the generic Reinstall button. It is enabled and has the same name, so the wait passed on it, the click started a global install, and no node install request was sent. The poll on the install count timed out with the confirm dialog still open. With the CPU throttled to 8x, the spec failed on 20 of 20 runs, and the button it clicked had the title "Reinstall". The spec now waits for the button titled "Reinstall on <node>". With the throttle it passes 30 of 30 runs. The assertions are unchanged. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): give the Studio hand-off spec a budget for the cold bundle load The "a result made through a hand-off records which result it came from" spec opens the Studio add-on straight from an address, twice. Each is a cold load: the page shows "Loading" until the add-on module has run, and the next assertion had the default five seconds. The load takes about two seconds on an idle run and seven to ten under CPU load, so the spec failed on a loaded machine with the hand-off note not yet drawn. With the CPU throttled to 6x and eight busy loops running, it failed on 21 of 30 runs. The first assertion after each load now waits up to 20 seconds, and the spec then passed 30 of 30 under the same load. The assertions are unchanged. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): carry the identity page styles in the Face add-on The Face page is drawn with the shared identity views, but its style sheet held only the clip and error rules. The page, card, model list, known-faces table, enrol sheet and distance scale classes had no rules. They looked right only when the host had already loaded the style sheet of its own Faces page, which a visit through the add-on drawer does not do. Opened that way, the cards had no gap, the model list showed bullets, and the install buttons ran into the names. The Face sheet now holds the same identity rules as the core sheet, so the page looks the same whichever way it is opened. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): scope the narrow-screen identity rules of the Voice add-on The rules for narrow screens (single-column pairs, smaller tool padding, compact rank rows) were copied into the Voice style sheet without their media query, so they applied at every width. They now sit in a max-width 720px query, and the reduced-motion rule in its own query, as in the core sheet. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): drop the repeated title from the Voice and Face pages The add-on shell already titles the page, so the recognition pages showed the name twice: "Voice" above "Voices", "Face" above "Faces". Keep the supporting line and the model picker, as the Studio page does, and remove the unused title strings. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(ui): replace the Pinned sidebar section with an Apps entry The sidebar no longer lists pinned add-ons. It shows one Apps entry that opens the add-ons drawer, with a Show all link below it that opens the same drawer. Pins are used from the drawer, where a pinned tile keeps its pin and move buttons. The server pins API is unchanged. Remove the PinnedNav component and its locale title, rename the items.addons label to Apps, and update the e2e specs and the add-ons documentation to match. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): assert the single shell title on the Voice and Face pages The add-on shell now shows the one title, "Voice" or "Face", and the page no longer repeats it. The tests still looked for the h1 "Voices" and "Faces". Assert that the add-on page has exactly one h1 and that it is the shell title. The core pages keep their own "Voices" and "Faces" titles. Assisted-by: Claude Code:claude-sonnet-5-5 playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): drop the repeated title from the Voice Library and Text to speech pages The add-on shell already titles the page "Voice", so these two tabs showed a second heading below it ("Speech voices", "Speak text"). Keep the supporting line, as the Studio and recognition pages do, and remove the unused title strings. The e2e spec now checks that each tab has exactly one h1, the shell title. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(ui): list pinned apps under Apps in the sidebar A pinned app now shows as an indented child of the Apps entry, with its icon and title, in pin order. Show all stays the last child. The pins come from GET /api/addons/pins through the navigation context, and the apps from the add-on registry, which the drawer feeds on every list read, so the links follow the drawer. A pin without an installed app is not drawn, nothing extra shows when no app is pinned, and the children are hidden when the sidebar is collapsed to the rail. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * docs(addons): say that pinned apps are listed under Apps in the sidebar The sidebar lists the pinned apps between Apps and Show all, in pin order. The pins section and the navigation section said that pins do not appear in the sidebar. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(ui): remove the Show all link under Apps in the sidebar The link repeated the Apps entry, which opens the same drawer, and looked redundant when no app was pinned. Apps is now the only add-on entry; pinned apps still list under it in pin order. The link, its locale key and the style comment are gone, and the e2e spec and the add-ons docs now say that Apps is the only entry. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(ui): show a first-run card on Apps when nothing is installed An administrator who opens Apps with no add-on installed now sees a short card with three steps: choose a library, browse and install, start the add-on. Its button opens the Browse tab. The card is hidden once an add-on is installed and for anyone who cannot install. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(ui): hide the pinned apps in the icon rail When the window is narrower than 1024 px the sidebar shrinks to the icon rail by CSS alone, without the collapsed class. The pinned app links were still drawn there, with the indent meant for the full sidebar, so their icons sat to the right of the rail and were cut off. Hide the pinned app links in both rail states. The Apps entry keeps its centred icon. The e2e spec checks that the rail shows no pinned app and that every icon is centred at 1280 px collapsed and at 1000 px. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): stop the backend redirect test racing the installed list The test reads the redirected URL right after the path changes. The Backends page then loads the installed list and drops a selected backend that is not installed, so the backend parameter was sometimes already gone when the test read it. The mock server has no llama-cpp, and about 15 of 40 repeated runs failed on the backend assertion. The redirect itself was correct, including show_all. Serve the selected backend in the installed list, so the page keeps the selection and the assertions stay as strict as before. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): accept a same-host Referer or Origin for human confirmation Browsers send no Sec-Fetch-* headers over plain HTTP on an address that is not localhost, so creating a resource from a LAN address failed with "Creating a resource requires your own browser session". When Sec-Fetch-Site is present it must still be same-origin with an empty destination, as before. When it is absent, Origin or, failing that, Referer must name the request host and port. A destination or mode that is present must still be the expected one. This matches the rule in BrowserProtection. The credential, token cookie, API key and tool-context checks are unchanged. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(ui): keep hub entries off the Apps route in the sidebar The Build hub still owned /app/addons through its legacy Add-ons tab, so the sidebar lit both Apps and Build on the Apps page. A tab whose gate is closed now owns no route when the sidebar asks, so only the Apps entry is active there. The hubs keep their own routes, and the legacy navigation still gives /app/addons to the Build hub. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(ui): label the pin control on app tiles and in the detail view The pin was a small icon-only button and hard to find. Each app tile now shows a button reading Pin, or Pinned with a filled pin, and the detail view has the same control in its header. Both toggle the same stored pin. The Apps grid lists pinned apps first, in pin order, then the others. The sidebar list and the server pins API are unchanged. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): check the Voice From a recording tab has one title The Library and Text to speech tabs already assert that the add-on shell title is the only h1. Do the same for the From a recording tab, so a heading added there later fails the navigation spec. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(ui): stop the add-on shell drawing a title over add-on pages The app decides what its page shows. The shell drew the add-on name as a header above every add-on page, so an add-on could not choose its own title. The shell now draws no header on a live, loading or frozen add-on page; each add-on titles its own pages. The unavailable and missing-page states keep the name, because no add-on page is drawn there. The runtime and shell specs now check that the shell adds no page title. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): let each add-on draw its own page title The shell no longer titles add-on pages, so each add-on draws one h1 per page. Voice titles its tabs "Voices" (Recognition and From a recording), "Speech voices" (Library) and "Speak text" (Text to speech); "Add a speech voice" already had its own. Face draws "Faces", Studio "Studio" and Talk "Talk". Tables promotes the database list and database name from h2 to h1. Fine-tuning and Quantization already drew a title. The add-on unit tests and the navigation and Studio specs now assert exactly one h1 per page, with the page's own title. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): add a kind to library entries and read unknown kinds tolerantly A library entry now has an optional kind: addon (the default when it is absent), backend or model. Every index written before kinds existed stays valid and its entries are add-ons. A reader keeps the entries of the kinds it knows and skips the others without reading their fields, so a newer kind never makes an older host refuse the whole index. The refresh result and the library state report how many entries were skipped and of which kinds, and the refresh logs a warning. A kind that is not a plain kind name still makes the index malformed. Search lists add-ons unless the caller asks for a kind, and Resolve returns add-ons only, so an add-on install cannot be pointed at a backend image. A library policy may name the signer with an anchored identityRegex instead of an exact identity, so builds from master and from tags both verify. An add-on install refuses a policy that carries one. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(backends): install a backend from a library entry A library can now list backends. An entry of kind backend names the image of the backend gallery by digest, and POST /backends/library/install installs it on the local node. The gallery stays the source of truth and its install path is the one used: the library resolves the entry, takes the signature policy from the library, pins the image by digest and calls the same install as the gallery. Installing a name that came from a gallery, another library or by hand is refused and changes nothing. The signature policy of a backend library names the signer with an anchored identityRegex, so images signed by the merge workflow on master and on tags both verify. A pattern that is not anchored is refused. An install is bounded by a size limit per kind: add-ons keep 512 MiB and a backend image defaults to 8 GiB, set with --addons-backend-max-bytes. The limit reads the manifest after the signature check and before any layer is fetched. The metadata of an installed backend records the library it came from. scripts/backends/cmd/backendcatalog renders entries from backend/index.yaml and pins them against the registry. The pilot is the CPU build of local-store, in gallery/backends/index.yaml. The library is registered on the first start only with --addons-backend-library, which is off by default. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(ui): show the kind of library entries and install backends from them The Browse tab lists the entries of every kind this host reads and marks each one as an add-on or a backend. A backend installs through the backend route and not through the add-on lifecycle: the confirmation says that the backend gallery is not changed and that a backend runs native code, and a refusal of the host, such as a name installed from another origin, is shown with its own reason. The details give the kind, the alias and the signer pattern. The library editor can name the signer with a pattern. Without this a save would drop the pattern of a backend library. The Libraries tab reports the entries a refresh skipped because their kind is not read. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * docs(addons): describe backends in the library Document the entry kinds, how a reader skips a kind it does not know, the backend entry format, the signer identity pattern, the install route, the size limit of each kind, the pilot library and the command that renders it. The backend page links to it. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(mcp): install a backend from a library entry The backend library route installs a backend from an add-on library entry, and the admin REST surface and the MCP catalog must stay in step. Add the install_library_backend tool with an in-process and an HTTP client, the route map entry, the safety-rule listing and a skill recipe. Listing library entries stays on the add-on routes, which the assistant does not expose, so no list tool is added. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(ui): carry the add-on library keys in every locale The add-on library and backend library strings existed only in English, so the other locales had no value for them. Add the missing keys of the addons namespace to de, es, id, it, ko, pt-BR and zh-CN. The values are the English text until a translation is contributed. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * Revert "feat(mcp): install a backend from a library entry" This reverts commit 7493cff727. Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * Revert "docs(addons): describe backends in the library" This reverts commit 57816ed7e6. Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * Revert "feat(ui): show the kind of library entries and install backends from them" This reverts commit 49b2b151b7. Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * Revert "feat(backends): install a backend from a library entry" This reverts commit 1d8d3e3421. Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * Revert "feat(addons): add a kind to library entries and read unknown kinds tolerantly" This reverts commit 484813f856. Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(ui): drop the backend library keys from the locales Revert the part of 39f77ae29 that added strings for backend libraries: the kind labels, the backend install texts, the signer identity pattern and the skipped entries notice. The add-on library keys stay. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(ui): add an add-ons control to the chat header Add-on tools were on or off only through the /addons command, with a toast and no state a person could see. The chat header now has an Add-ons button in the style of the MCP dropdown. It lists each running add-on that ships tools with a switch, and a badge shows how many are on. The chat keeps the ids that are on (addonToolIds) next to the older boolean, and both are saved with the chat. A chat that has only the boolean means every add-on. The request sends addon_tools alone when every add-on is on, and adds addon_tool_ids when only some are. /addons turns all on or all off and uses the same state. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): let a chat request name the add-ons whose tools it uses addon_tools=true still offers the tools of every add-on the caller may use. A new addon_tool_ids metadata key, a comma-separated list of add-on ids, narrows that to some add-ons. The list counts only with the opt-in, and a list that names nothing offers no tool rather than all of them. The executor drops the tools of add-ons that are not listed and refuses a call to one as an unknown tool, so a model cannot reach a tool the person turned off. Both keys are consumed so they do not reach the backend. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): cover the per-add-on tool list and the chat header control Go tests cover the list form (the list filters the tools offered and the calls allowed) and the unchanged boolean form. Unit tests cover the chat add-on rules. Playwright specs cover the header control: listing only add-ons that ship tools, toggling each one, the count, /addons in step with the switches, and the request metadata. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): check each add-on page has one title when not enabled The shell names an add-on only where the add-on page cannot mount (not enabled, failed, no UI, bundle not loaded, no such page). Once the page mounts it draws its own title, including when it says it is not enabled on this server, and the shell draws none. The shell code already works this way; this change states the rule beside the unavailable state and pins it in the specs. The shell spec now expects exactly one title in the unavailable states. The navigation spec checks the Face page without a face model (the add-on title only) and the Face page of a stopped add-on (the shell title only). Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(addons): upgrade add-ons on their own when the setting is on A new auto_upgrade_addons setting (flag LOCALAI_AUTO_UPGRADE_ADDONS, default off) lets the owner upgrade an installed add-on when its library lists a newer version. It follows the backend setting: a startup flag, a runtime setting, and the same schedule as the backend update check (a first pass shortly after start, then every six hours). Each pass fetches the library of every installed add-on, and for each available update builds the same pinned upgrade command an administrator sends and runs it through the same lifecycle path. The channel rules, the signer identity, the digest checks, the SDK compatibility check and the backup before the upgrade all apply unchanged. The only difference is the gate: the owner acts on its own setting, so no administrator is asked. A refused or failed upgrade changes nothing and is logged; a candidate that failed is not retried until the library lists another digest. With the setting off, nothing runs and upgrades stay manual. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(ui): add the Upgrade add-ons automatically toggle to Settings The toggle sits beside Upgrade backends automatically and is off by default. It saves the auto_upgrade_addons runtime setting. The English locale gets the label key, and the Settings test fixture lists the new field. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): cover the automatic upgrade setting and document it The setting defaults to off in the config, the runtime settings and the flag, and is read back from the saved settings file. With it on, a real owner upgrades an installed add-on through the manager; with it off, nothing changes, and a change of the setting at run time takes effect on the next pass. The manager specs show the upgrade goes through the same pinned path as the manual one, and that a corrupted package, a failed signature policy, an incompatible release, a missing update checker and a caller who is not an administrator each leave the installed version in place. The new specs are added to the lifecycle case inventory. The add-ons page describes the setting, its schedule and its default. Assisted-by: Claude Code:claude-sonnet-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * refactor(addons): name the library entry identifier id The library entry of an add-on used addonId while the shared envelope and the model entries use id. Release now has the field ID, written as id, and every writer emits it: the index encoder, the package workflow templates, the catalog generator and gallery/addons/index.yaml. The digests in the index did not change. DecodeIndex still reads addonId as a legacy alias for one release, so an existing library and a library served by an older tool keep working. An entry that holds both names is refused. The Apps UI reads id and falls back to addonId. Assisted-by: Claude Code:claude-sonnet-5-5 go node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(addons): use the id field in the auto-upgrade test release The auto-upgrade test arrived after the identifier rename and still named the release field AddonID, so the application tests did not build. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(addons): annotate the auto-upgrade actor label for gosec The actor label looks like a credential to gosec G101. It is a fixed name for upgrades the owner starts itself. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * fix(schema): persist the per-chat add-on tool fields The chat header persists addonTools and addonToolIds, but Conversation had no fields for them, so the server dropped them on save. Add both and update the generated swagger files by hand because swag is not installed here. Assisted-by: Claude Code:claude-sonnet-5-5 go Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): count the add-ons auto-upgrade setting in the settings groups The setting sits in the Backends and galleries group, once. The page now lists 54 settings plus the three branding images, so the spec expects 57. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): pause the fake clock ahead of now in the clear-all spec The fake clock runs from install, so pausing at the current time failed with 'Cannot fast-forward to the past' on a slow runner. The save itself is synchronous and was not lost. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * test(ui): hold the Studio capabilities reply longer in the skeleton spec 800 ms was shorter than a slow runner needs to render the page, so the skeleton was gone before the check. The product shows it. Assisted-by: Claude Code:claude-sonnet-5-5 node playwright Signed-off-by: Ettore Di Giacinto <mudler@localai.io> * feat(i18n): add the French add-ons locale Master added the fr locale after this branch forked. The add-ons unit test requires every locale to carry the add-ons namespace, so fr needs its own addons.json. Assisted-by: Claude Code:claude-sonnet-5-5 node 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>	2026-10-22 17:57:19 +02:00
Ettore Di Giacinto	9bbcde4b1b	chore: drop design specs and plans from the change ... Design specs and implementation plans are working notes and are not kept in the tree. Signed-off-by: Ettore Di Giacinto <mudler@localai.io> Assisted-by: Claude:claude-opus-5-5 [Claude Code]	2026-09-27 19:55:18 +00:00
Ettore Di Giacinto	6738478c8a	docs: plan distributed failover, localai-proxy and the chain UI ... Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io>	2026-09-27 07:42:20 +00:00
Ettore Di Giacinto	f4ce839bdc	docs: plan model failover chains ... Assisted-by: Claude:claude-opus-5-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io>	2026-09-27 07:42:20 +00:00
Ettore Di Giacinto	cec62c3dd3	feat(backends): add Whisper-Medusa transcription ... Add a dedicated Python gRPC backend for aiola Whisper-Medusa checkpoints, including mono 16 kHz preprocessing, bounded clip validation, CPU/CUDA 12 images, backend gallery metadata, and user documentation. Assisted-by: Codex:gpt-5 Signed-off-by: Ettore Di Giacinto <mudler@localai.io>	2026-09-11 21:48:07 +00:00