A wiki page is usually where the longest single piece of writing in a project happens. This release is about not losing it.
Offline draft recovery
If the connection drops mid-edit, your changes are kept locally. Reopen the page and the draft is offered back to you rather than silently discarded.
Recovered drafts are checked against the current server version before they sync. If the page moved on while you were offline, you are told rather than having your draft overwrite someone else’s work — the safe outcome for the case where two people edited the same page from opposite sides of a network drop.
Finding your way around a page
Long wiki pages now carry in-page heading navigation, so you can jump to a section instead of scrolling for it. Wiki search normalizes its terms, which means capitalisation no longer decides whether a page is found.
Comments as one thing
Bugs, stories, and wiki pages used to each have their own comment implementation. They now share a single comment entity — which means Helix can read and write comments anywhere the same way, and the UI updates just the record you commented on instead of refetching the surrounding lists.
Helix also picks its model more appropriately per task, and its entity search resolves the record you meant more reliably when a title is partial or ambiguous.
Also in this release
- Project tags and resource grouping in MCP. MCP clients can read and set project tags, and project resources come back grouped rather than as one flat list.
- Context and embedding export for integrations. External tooling can export a project’s context documents and their embeddings, with validated slugs and stable chunk IDs, so an index built elsewhere stays aligned with Studio’s.