Hexis Files

Agents and MCP

• Every MCP session is told what Hexis is and to search the knowledge base before answering from memory. The text is a short platform header followed by mcp-description.md, a new file at the repository root that an admin writes, seeded from the template on the first start after upgrading and never rewritten by the platform. It arrives as instructions on the initialize handshake, from the hosted endpoint and from hexis-mcp alike. For clients that drop that field, its first line is also prepended to the descriptions of start_session, grep, list_files and read_file. The External agent access page shows both channels with their character counts and, for admins, an Edit link.
• Non-admin marketplace setup. The Claude marketplace walkthrough now guides a person who is not an administrator through five focused steps: where to open the repository picker, the deployment-specific Connect to URL action, and the complete install choice.

Skills & Tools

• Everyone leads the Groups list. Its page shows what is org-wide: the plugins, skills and tools every signed-in person and their agents can use, with no group or role needed.
• Personal plugin. A person's own space is called "Personal plugin" everywhere, one name for everyone, and no longer has a row under Groups — it is a plugin, not a group — while staying reachable from Everything, the Plugins tree and its URL.
• Private plugins say so. A personal access.md now states its privacy in both blocks: deny everyone followed by the owner, in the file's own block as in the folder's. Spaces created by earlier releases get the same statement on the next start. Every plugin whose access rules have that shape shows a "Private" mark on its row.
• A file inside a plugin says which plugin it belongs to. Opening a plugin's plugin.json, its access.md or any other file of its own shows the file, with one line above it naming the plugin and an Open plugin link to its page. The manifest no longer jumps to the plugin page on its own; the page still shows it in its collapsible section.

Upgrading

No new required settings. Three optional ones since 0.13.6 are documented in .env.example; take the release's docker-compose.yml so they reach the container. Database migrations run on start. Version 0.17.0 was tagged but never published; this release supersedes it.