Release notes

Meeting recaps now reach every attendee: hosts, Heyno users, and invited guests alike. When a meeting ends, Heyno writes the recap, emails it to everyone who was part of the meeting, and files the document in Drive under Meeting Documents.

Previously the recipient list was resolved only from a calendar invitation, which meant a meeting started on the spot had no list to resolve and quietly sent nothing at all. The list is now built from the people who actually joined, unioned with anyone on the invitation, and falls back to the host when nobody else can be identified.

The list is resolved when the meeting ends rather than when it was scheduled, so somebody added an hour beforehand is included and somebody who declined is not. It can be edited before the recap sends, and a meeting can be marked to send no recap at all.

• Ad-hoc and scheduled meetings share one rule: in the room or on the invite, the recap lands in your inbox.
• Recap documents save into Meeting Documents automatically, and the emailed copy is the same document.
• Guests without a Heyno account receive the recap at the address they were invited on.
• Action items are extracted as a list rather than left buried in the summary.

When Heyno is about to act on your behalf, such as sending an email, delivering a quote, or posting an update, it shows an approval card instead of proceeding. The card contains exactly what would be sent, to whom, and what triggered it.

You approve it, edit it first, or decline it. Nothing goes out on a timer, and nothing goes out because a card was ignored; an unanswered approval stays outstanding and appears in the day queue until somebody deals with it.

Reversible internal work does not produce a card. Drafting, filing, tagging a record and adding a calendar hold are all undoable in seconds, and stopping for approval on each one turns the assistant into a form. The line is drawn where an action becomes visible to somebody outside your business.

• High-risk categories, including anything that moves money, are off by default and enabled explicitly.
• Approvals can be scoped by role, so payment approvers and reply approvers need not be the same people.
• Cards can be approved from a notification without opening the app.

The Heyno Connector links your AI tools to everything Heyno manages for you. Set it up once, and an assistant in another application can work with your calls, calendar, mail, tasks, documents and business memory instead of starting from nothing.

It is the same data and the same permissions as the Heyno app: connecting a second tool does not create a second copy of anything, and it does not widen what that tool may do.

A connected tool may read the context you granted and propose actions. It may not send mail, deliver quotes or take any other side-effecting action without the same approval card a request inside Heyno would produce, and that boundary is enforced on the Heyno side rather than trusted to the connecting tool.

• Connections are per tool and revocable independently, with created and last-used dates shown.
• Revocation takes effect immediately and does not require the other tool to cooperate.
• Built on MCP, so any client that speaks it can connect.

Heyno Drive now produces real documents: Word files with proper heading levels, Excel sheets with live formulas rather than pasted values, and PowerPoint decks with real slides. Opening one gives you something you can edit rather than something you have to rebuild.

The distinction matters most in spreadsheets. A sheet of numbers is a report; a sheet with formulas is a model somebody can change an assumption in and get a new answer from.

Content is written as structured markup and converted, so headings become heading styles and tables become tables. That is why a document asked for as markdown comes back with a real outline instead of a wall of body text with bold lines in it.

• Files are filed into the folder that matches the work; meeting documents go to Meeting Documents automatically.
• Folder names are unique across your account, so a file has one unambiguous destination.
• Revisions update the same file and keep versions, rather than creating a second file with a similar name.

Heyno now includes a full mail client and calendar. You read and send from your own address rather than a Heyno one, so nothing about how you appear to the people you write to changes.

Replies are drafted in your writing style, learned from mail you have already sent rather than from a generic template, and a thread is read as a thread: a reply drafted halfway down a long exchange accounts for what was already agreed, not just the message above it.

The calendar is read whenever anything is scheduled, so a proposed time is one that is actually free. Working hours, buffers and the meetings you never want stacked are yours to set and are respected rather than optimised around.

• Nothing sends without an approval.
• Lapsed provider authorisations stop mail rather than failing silently, and the account is flagged for re-authorisation.
• Invitations arriving by mail are parsed into calendar entries, including badly formed ones.

Ruby-Horizon is the model behind Heyno, the assistant that runs the day with you. Talk to it like a colleague, and it does the work rather than describing how the work might be done.

It was built for repetitive agentic work rather than for single impressive answers: long chains of small tasks, run reliably, with the judgement to stop and ask when something is about to have a consequence outside the conversation.

Voice is built in rather than bolted on, so a phone call and a chat are the same assistant with the same context, not two systems that share a name.

• Runs where your work runs, including on your own hardware for enterprise deployments.
• Safety and approval behaviour are part of the model’s design, not a filter in front of it.
• See the system card for evaluation detail and known limitations.