v0.27.0

Getting started

• A fresh deployment asks one question first: where should the knowledge base live? The address-and-token form is a step of that question, not the whole form.
• A new account lands in the knowledge base, with a Get set up list beside it: invite your team, connect your agent, write your first page, learn the command menu. The connect page says when your agent has connected, and finishing the list says "You're set up".
• Starter packs: a new knowledge base asks "What does your team do?" and fills itself with pages and skills that fit the answer (Engineering, Sales, Support, Operations, or a general pack), in one commit. A connected agent offers to draft the first pages.
• Inviting someone who already has an account as Admin makes them an Admin.

The command menu and plain words

• The toolbar's search box finds pages, skills, tools and plugins and runs commands too (Ctrl+K, ⌘K on a Mac). Single-key shortcuts for the commonest actions; Knowledge and Skills & Tools sit side by side.
• What lands for everyone reads as published, never as pushed or merged. New changes from teammates are announced as "New changes available". A folder's access rules read as "Who has access", a plugin's manifest as "Plugin settings", and a page someone else has open says who is editing it.
• Confirmations are the app's own, and "Don't ask again" on branch delete skips the question instead of blocking the delete.
• The product is called Hexis by Bevel everywhere, and the pointer is a hand over everything clickable.

Agents

• open_page: an agent can show a knowledge-base page inside the chat, rendered with the app's own renderer, where the reader can edit it or propose a change as themselves. Hosts that support MCP Apps render it inline; others get the text and the app link.
• File downloads: request_file_download hands out one-time links for files and folder zips, every file judged on its own against the caller's read and download rules.
• move_file rewrites links into and out of the files it moves, in Markdown and HTML, and reports what it could not rewrite.
• Agents can delete a branch; a change request that proposes nothing never blocks it, and branches left over from merged requests are cleaned up.
• Every tool call is checked against the tool's interface before it runs, every tool description starts with a call example, and a tool can declare that it works on the default branch when no branch is given.
• merge_branch waits for the source branch's pending commits and says when there was nothing to merge. list_change_requests refuses an unknown state instead of answering with everything.
• A write whose push the repository host refuses says so and stays saved locally, on every operation. A git call the host refuses for its credential renews the token and runs again, once.

Fixes

• A folder download packs only the files the caller may read and download, and leaves out what they may not read without naming it.
• A change request's link opens the request; a removed file in a change request shows as its deletion.
• A fragment link inside a live HTML page scrolls the page.
• A switched-off account's connection key says why it is refused.
• Log lines carry no email addresses or names.
• The Get set up list stays on screen in an ordinary laptop window; "New page" never overwrites a page.

Upgrading

Self-hosters: the image ghcr.io/bevel-software/hexis:0.27.0 is published. The npm packages @bevel-software/platform-* 0.27.0 follow from this tag.