You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Agents can make plugins. Two new tools, my_plugin and create_plugin, give an agent the same doors a person has: its own private space (created on first use, with the folder its skills go in) and a shared plugin, at the root or inside a grouping folder. They describe the app's own endpoints, which now accept a connection key as well as a session.
Private spaces stay private. A personal plugin's rules deny everyone and name only its owner, not even admins, so opening the repository root with read: everyone no longer opens anyone's private space. Spaces from earlier releases get the same rule on the first start after upgrading.
Access rules explain themselves. Every access.md the platform writes carries a comment on each of its two blocks: the top block governs the file, the body governs the folder; entries are a role, a group, a person, or everyone, the built-in principal for every signed-in person and their agents. The managed AGENTS.md is readable by everyone, since agents are told to read it first. The app shows access.md as the YAML it is.
The sidebar is regrouped around who can use what. Everything and Owned by me list plugins as rows above the cards; a Groups / Advanced switch below them shows either your own space and every group from the access rules, each with a page of what it can use, or the Skills/ and Plugins/ folders as they are on disk. A plugin's manifest opens the plugin, whose page now ends with a collapsible Manifest section. A file under either root opens inside Skills & Tools, with that app's sidebar around the same viewer Knowledge uses.
New plugin from a folder creates the plugin inside that folder. A plain folder made under Plugins/ is no longer turned into a plugin at the next start.
Change requests waiting on you are listed under the Skills & Tools sidebar as well as under the Knowledge tree.
hexis-all is a self-contained plugin holding every skill you may read plus the knowledge base's MCP endpoint, so one install means the same thing in Claude Code, Cowork and claude.ai.
Cowork and claude.ai walkthrough with a screenshot of every screen, and the GitHub Enterprise facade logs why it refused a connect step.
Knowledge
Pages show their images. A markdown image with a relative path renders from the workspace in the Knowledge view, on skill pages and in review diffs; the convention is an assets/ folder beside the pages that use it.
Version history is a button of its own, the clock beside Edit, on skill pages and Knowledge pages alike.
Manage-access menus close on a click outside and on Escape; dialogs and menus dismiss more precisely.
Agents and MCP
MCP tool calls survive a server restart. A client whose session the server no longer knows re-registers and retries the call once, so a redeploy shows up as one log line instead of a broken toolset. Only that one failure is retried; nothing that could have run runs twice.
Admin
Settings tabs renamed to say what they hold: "App roles" and "Groups & Members"; an overview of connection keys, with a note to the owner when an admin revoked one; the update-available banner is gone.