Version 1.7.4 added the control. Version 1.7.5 makes it usable.
The per-role and per-connection allowlist shipped in 1.7.4 as a genuinely useful control with a genuinely awkward front end: a free-text area where you typed ability slugs, one per line, from memory or from another tab. The rules underneath were exactly right. Entering them was not.
Nothing about those rules changes in 1.7.5. The stored data is the same, the narrowing logic is the same, and a site that never opens the screen still sees no change. What changes is the input control.
What the screen looks like now
The Connection tab replaces the textarea with a searchable checkbox picker. You see the abilities, you search them, you tick the ones this connection should reach. There is no slug to spell correctly and no way to save a line that refers to nothing.
The role and client fields are selects now too, listing what actually exists on your site instead of asking you to type an identifier and hope. The client ID gets a copy control, which matters because it is a long opaque string whose entire purpose is being pasted somewhere else. Connection tables paginate, so a site with a lot of connections stops rendering all of them at once. And the Abilities tab gained a search that works across its sub-tabs rather than only the one you happen to be looking at, which with 179 abilities in the catalog is the difference between finding one and hunting for it.
A large allowlist also no longer renders every checkbox at load, so the screen stays quick on a site with plenty of abilities enabled.
The scoping rules, unchanged
Worth restating, because the new control makes them easier to reach and it would be easy to assume they also got looser. They did not.
The lists only ever narrow. An ability has to clear the global list on the Abilities tab, then the role’s list, then that connection’s list, before an agent can call it. A row here can take reach away and can never add it. That order is enforced twice, once when the agent asks what tools exist and again when it actually calls one, so a tool a connection cannot use does not appear in its list either.
Scoping works at the role level and the connection level. There is still no per-Application-Password scoping, so if you need two agents with genuinely different reach, give them separate connections or separate users.
Full detail is in safety controls.
The fixes on the same screens
The picker arrived with the usual crop of first-version problems, and 1.7.5 fixes them in the same release:
A zero-match search left the Save button stranded on an empty card. Search for something that matches no ability, and the results vanish while the savebar stayed behind, attached to nothing. It now hides with the results and comes back with them.
The client picker’s hover and selected states looked identical, so the card your pointer happened to be over was indistinguishable from the one you had actually chosen. Hover is now a border outline only.
Ability order survives a re-save. It did not before, which meant the list you carefully arranged came back rearranged.
A stale search now clears on keyboard navigation. Tabbing through the interface used to leave a previous search term filtering results you were no longer looking at.
The new controls also carry accessible names and translations, which is less a fix than finishing the job. A checkbox picker that screen readers announce as nothing is not an improvement over a textarea.
What did not change
No default flipped. No permission or capability changed. No ability was added, removed, renamed, or repermissioned, so the catalog is the same 179 it has been since 1.7.4: 85 core and 94 across the integrations. Read-only mode, the high-risk lock, and what the Activity Log records are all untouched.
The other half of this release is correctness work that does not show up on any screen, including one bug where an update could switch OAuth back on for a site that had deliberately turned it off. That one is worth reading on its own: absent and unknown are not the same answer.
Full release history is on the changelog.