Hexis Files

The reliability release: ninety changes from two weeks of testing the platform as a business user, as an admin and as a connected agent. Most of them make something say what it is doing, refuse what it should never have allowed, or recover on its own.

Agents and MCP

• An agent proposes and syncs; a person merges. merge_change_request is gone; merge_branch refuses while a change request from that branch is open.
• A tool manual or skill added, changed or removed on the default branch is live within ten seconds on the connection you already have, with no reconnect.
• Skills carry a version. list_skills reports it and get_skill can load an earlier one; an unknown version answers with the versions the skill declared.
• The local MCP server answers its client at once and discovers tools in the background, so setup no longer times out in Claude Code or Cursor.
• Externally registered tools and their sign-ins survive a server restart; the hosted endpoint is stateless, so a restart is invisible to clients.
• file_stat says whether an item is platform-managed, whether the caller may move or delete it, what kind of content it holds, and, on request, who holds which permission and why. Move and delete offer a dry run and ask for confirmation when access would change.
• write_file defaults to create and refuses to overwrite by accident; write_files answers for every path. A denied write says whether the agent may propose the change instead, and how.
• A missing path answers 404 with a stable error code on every tool; a branch that never existed answers 404 and a deleted one 410; an invalid connection key is refused in one plain sentence.
• The repository's internal git folder is unreachable through every tool and route.
• Word and PowerPoint extraction keeps words whole across soft breaks and tabs.
• The agent guide says where a new file belongs, documents group roles, and can be given its own file name so a customer's AGENTS.md is never overwritten.

Change requests

• A request that has fallen behind brings itself up to date when opened, keeps the approvals its update did not disturb, and never shows a business user a branch name.
• The dialog shows only what the author changed, previews proposed documents and images, labels the approve control, and explains a file the viewer may not read.
• Owner approval gates every file type, not only Markdown. An applied request stops showing as pending for everyone, and a failed apply says so.
• A tool proposed in an open request shows as a Proposed card, as a proposed skill already did.

Files and the sidebar

• Deleting asks first; moving names who gains and who loses access; deleting a folder with proposed files asks what to do with the proposals.
• A rename onto an existing name is refused instead of replacing the file. Platform files stay in their folder. Folders persist until someone deletes them.
• Every workspace path resolves inside the repository, and the explorer takes its roots from the checkout, never from a folder that merely looks like one.
• Uploads report once, in full, where they landed; a suggestion can be withdrawn from its sidebar row; an empty tree says why.
• Copy path gives a link that works from anywhere. The file page is never silently blank.

Access and accounts

• A denial strips every permission that depends on it. A download grant implies read. Restricting someone keeps them visible in the dialog.
• The Manage access sheet has one primary action, explains its terms where they appear, keeps long names inside the field, and lets download and edit change independently.
• Sharing is offered on every plugin row and skill card, on the skill page, and on proposed files.
• Every account changes its own password; the accounts page shows the sign-in methods an account really has and offers Set or Reset accordingly; the roles page shows the deployment admin as a fixed Admin.
• Deleting a user asks whether to remove them from roles, groups and access rules, and does it in one commit. Admins always keep write at the repository root.
• A grant to an email with no account is allowed and labelled.

Setup and operations

• A repository connection is validated for reading and writing before it is saved; setup shows and checks the three root folders; a failed initialization names its cause and offers a retry.
• An OIDC configuration is verified against the provider before it is saved and takes effect without a restart.
• A deployment whose git host is unreachable still boots. Git commands carry a deadline, migrations take a lock, the process stops cleanly, and a stalled remote costs one workspace instead of all of them.
• GET /api/ready reports whether commits are draining and how far behind they are, for alerting.
• One structured logger replaces 294 bare console calls.

Library and connect

• Adding a skill or tool has its own tabs; an owner can delete a tool from its page; a saved key is probed and a refused one is reported; the library refreshes at once after a key is saved.
• Setup counts match between the plugin banner and the Connect page. Linked skills and tools wear a Linked pill. Card names stay readable.
• Every connect surface leads with Claude and ChatGPT; the Codex command is complete; the Claude walkthrough ends with the connector.
• Subscribing to a locked plugin answers instantly.

Upgrading

• merge_change_request is removed from every agent tool set. Agents that merged should hand the request's link to a person or use merge_branch where no request is open.
• The knowledge-base folder settings are deployment settings, not environment variables; existing values are imported once.