Write the instruction once. It runs while you are away.
Until now Hyprcore only worked while you were sitting in front of it. Routines change that: a trigger, an instruction in plain English, and a list of what it is allowed to touch. A routine can run on a schedule, half an hour before a meeting, or the moment one ends — reading your mail and your notes to brief you, drafting a follow-up for you to look at, or posting a finished meeting to whatever you already automate. Ten of them come already written, and every one of them is a file in your vault you can open and read.
Routines — tell Hyprcore what to do in plain English, and when
Connect Gmail, Outlook, Notion and web search, read-only until you say otherwise
Webhooks that POST a finished meeting to n8n, Zapier, Make or your own endpoint
Ask a question from anywhere, by voice or by typing, answered from your vault
Run routines and chat on your own Claude Code subscription instead of ours
- Routines: a trigger, an instruction written in plain English, and a list of what the routine may reach. It can run on a schedule, a set number of minutes before a calendar event, when a recording starts, when a meeting ends, or only when you press the button
- Ten routines come already written — meeting prep before an external call, a morning briefing, a Friday review, a sweep for commitments going stale, follow-up drafts, a research brief, a topic watch, and three that post to your own systems. A template fills in the editor and waits; nothing starts running because you clicked a card
- Two separate settings decide how much rope a routine gets. One covers your machine — whether it can touch files and run commands. The other covers change — read only, stop and ask you first, or act on its own. “Draft my replies but never touch my disk” is a normal thing to want, and one slider cannot say it
- Connect Gmail, Outlook mail, Notion and web search. The settings panel tells you what a connection can reach in words — read your mail, draft replies — rather than showing you a scope URL and leaving you to work it out
- Every tool in a connected account is marked read or write by hand, and anything unrecognised counts as a write until someone has looked at it. The limits you set are applied to the request before it leaves your Mac, not asked of the model as a preference
- Webhooks: a routine can POST to any HTTPS endpoint — or to localhost, for the n8n running on your own machine. Signed so the receiver can verify it, retried six times over about eight hours, and you choose what goes in the body: summary, action items, attendees, transcript, notes, links
- A delivery log showing every attempt, its result, and the exact body that was sent — plus a test button that posts a real payload built from a real meeting before you turn anything on
- A run log that accounts for every run: what fired it, what it called, what it produced, and what it cost
- Ask a question from anywhere with a shortcut — by voice or by typing — and get an answer from your own meetings and notes. Type @ to point it at a specific note or meeting
- If you have Claude Code installed, routines and chat can run on your own subscription instead of Hyprcore’s. The settings panel names which credential it would actually sign in with, because an API key in your environment quietly outranks a subscription and would otherwise bill the wrong account
- PDFs open in the app with a real page view, images come into your vault as files in their own right, and the assistant can look at either — asking you first, every time
- Support moved into the app, and it arrives already knowing your version, your platform, and what went wrong
- The meeting page was rebuilt — a new header, clearer tabs, and a transcript panel that is easier to read and move around in
- A progress bar while a meeting is being made, showing which step is running and which are still to come, instead of an unexplained wait
- The Usage tab says which routine spent what, so a routine quietly working through your monthly allowance is visible rather than deduced from a bill
- Import a file straight into the folder you are looking at, from the folder’s own menu
- Renaming a speaker not showing up until you reopened the meeting
- Renaming a meeting leaving its own record pointing at the old folder
- Notes written by the assistant using formatting the note editor could not display
- Images not appearing in the import dialog
- Spacing in chat answers, and @-tagging not working in the in-app composer