Hexis Files

This release introduces the local MCP server. Until now, agents reached a workspace only through the hosted MCP endpoint — which meant tools that must run on your own machine couldn't be used at all, and the local server existed only as unreleased groundwork. It is now a first-class way to connect, visible everywhere an agent gets set up:

• One command, sign-in in the browser. npx @bevel-software/hexis-mcp with your workspace URL opens a browser sign-in — no key to mint or paste. The grant refreshes silently on later runs; --key remains for pipelines and CI.
• Local-only tools, actually local. Plugins whose MCP servers are marked local are downloaded and run on your machine, with a persistent data directory that survives restarts. Their ${VAR} credentials resolve from your local environment — vault secrets stay on the server, local secrets stay on your laptop, and neither crosses over.
• Everything else comes along. The same connection serves the workspace's remote tools and its skills (as slash commands), so the local server is a superset of the hosted endpoint, not a trade-off.
• In the UI. Onboarding and the agent-access page now lead with the local server for desktop agents — Claude Code, Claude Desktop, Cursor, Windsurf, Cline and similar — with the hosted MCP endpoint as the option for everything else. (Claude Desktop works through its config file; only its Connectors UI is remote-only.)

Groups joined roles in access control. A group and a role are now distinct principals — even when they share a name — with groups badged as such in the share dialog and roles reduced to membership on their admin page. Hexis ships the group model and its guarantees (machine-owned files can't be written through a human's lock; group denials can't be masked by a same-named role); syncing groups automatically from your identity provider is part of the enterprise edition.

Hardened by five review rounds before shipping. The local server's sign-in lifecycle is race-free and its startup and teardown are bounded — a wedged or orphaned server exits and cleans up its children instead of lingering and holding plugin directories hostage. On the platform side, lock releases only announce disk changes that actually happened, and publication checks only read settled git states.

Packages @bevel-software/platform-{shared,mcp-core,core-backend,core-frontend} and @bevel-software/hexis-mcp are on npm at 0.11.1; the image is ghcr.io/bevel-software/hexis:0.11.1. Self-hosters: this release adds one database migration (a lock-mode column), applied automatically on boot.