mirror of
https://github.com/mudler/LocalAI.git
synced 2026-11-06 12:33:16 -05:00
Ettore Di Giacinto
5df9c43578
A binding with its capabilities ticked still gave nothing to the owner's own allowlisted account: Authorize wanted a pairing or a role even for capabilities that are not sensitive, so the agent had no reminder, memory or talk-back tool. A sender whose ID or @name is an entry of the allowlist now holds every capability that is not sensitive, within the ceiling of the binding and while no switch is off. The decision says Via "allowlist". A sensitive capability still needs a pairing, and a role never grants it. The entry of a channel or group lets its members talk to the bot but does not trust them: the trust is matched against the sender only, and a binding that accepts anyone lists nobody. Such a sender still gets capabilities from a pairing or a role. The capability gate takes the handle of the sender for the same match, and a sensitive request ignores the allowlist as it ignores roles. When a tool is held back for a missing right, the turn now carries a short note with the reason in plain words and tells the model to relay it, instead of saying that it has no such tool. The reasons are kept in the grant of the turn, so a worker reports the same words. The access view lists a "listed" sender apart from one let in through a channel. Assisted-by: Claude:claude-sonnet-5-5