Studio learns your project, and writes down what changed

Project context gives Studio a maintained understanding of what your project is. Audit logging records every change and who made it. The project mailbox, the tests page, and wiki editing were each rebuilt, and the codebase moved to a Turborepo monorepo.

The last release opened Studio up — to your editor, to your inbox, to answers you could check. This one turns it inward. Studio now maintains an understanding of what your project actually is, and keeps a record of everything that changes inside it.

Project context

Every project builds a brief — a short, current description of what the project is and where it stands — sitting on top of a set of context documents drawn from the project’s own wiki pages, requirements, meetings, and delivery history.

Both are yours to edit. Correct the brief and it stays corrected. Lock a document and refreshes leave it alone, so a hard-won description of your billing rules isn’t quietly rewritten the next time context rebuilds.

Context documents are searched by meaning rather than by keyword, so a question about who signs off on a release finds the approval policy even when it never uses those words. Helix reads context as an ordinary entity — the same shape as stories and bugs — and has to search it before reading, so answers come from the documents that match the question.

Ingestion works through a project’s full history in pages, chronologically, so later decisions supersede earlier ones. This replaces the earlier project facts pipeline, which has been removed.

Every change on the record

Studio now writes down what changed, who changed it, and what it looked like before. Creates, updates, and deletes are recorded against the entity they touched — across delivery, QA, wiki, resources, meetings, members, and keys.

Actors are recorded by kind, so a change made by a teammate, by Helix, by an MCP client, or by a scheduled job each carries its own label. Sensitive values are redacted before the entry is written, and the entry commits in the same transaction as the change itself.

A mailbox you can work out of

Project email is now threaded. Conversations open as a stack of messages with sender avatars, expandable recipient details, and quoted history collapsed until you want it. Mail syncs in the background, and thread listing stopped fetching message bodies it never renders — large mailboxes open noticeably faster.

Ask Helix to reply and the draft appears inline in the conversation, laid out the way it will send. Edit it in place, open it in the compose pane, or discard it. Nothing leaves the mailbox until you send it.

Wiki editing that survives a dropped connection

Lose the network mid-edit and your changes are kept locally, then offered back when you reopen the page. Recovered drafts are checked against the current server version before they sync, so a page that moved on while you were offline tells you rather than being overwritten.

Long pages gained in-page heading navigation, and wiki search normalizes its terms so capitalisation no longer decides whether a page is found.

Comments, everywhere, as one thing

Bugs, stories, and wiki pages shared their comment implementation. Helix can read and write comments anywhere the same way, and the UI updates just the record you commented on instead of refetching the lists around it.

For integrations and MCP clients

MCP clients can scope which toolsets they load rather than taking all of them, and can now read and set project tags and receive project resources grouped rather than flat. Universal read endpoints cover the core project entities, and a project’s context documents and embeddings can be exported with validated slugs and stable chunk IDs, so an index built elsewhere stays aligned with Studio’s.

One change to note: priority and severity were removed from QA test entities. If you read or write test cases through the API or an MCP client, drop those fields. ⚠️

Under the hood

Studio’s server, web app, docs site, database schema, shared utilities, and component library are now a single pnpm + Turborepo workspace. Builds, typechecks, and tests run through one task graph that knows what depends on what, and unchanged packages come out of cache. Nothing in the product changed — but everything after this ships faster.

Heizen Meets

The desktop companion picked up microphone mute during a recording, project assignment from the app, recordings that stop when the call does, and a much lighter recording pipeline. Linux builds now ship for ARM64 as well as x64.