Hey Sumo-lings! 👋
A lot of you told us Hyprcore was great at remembering your calls, but you wanted it to actually do something with everything it captured, not just store it. We heard you. Our v1.10 release, out August 14, adds three new capabilities: routines, connectors, and webhooks. Here's what's new and why we built it the way we did.
🧭 It works while you're not there
The most requested feature was some form of automation, so we built routines: describe a job in plain English, tell it when to run, and it happens on its own, before a meeting, after one, or on a schedule, laptop shut or not. No canvas, no nodes to wire up. One of our shipping routines, quoted exactly as it runs:
When: 30 minutes before a meeting with external guests Do: Look up the event, then brief me: who is attending and their company, the last email threads with them, and what my notes say we discussed or promised last time. Keep it under 200 words, and write it into the meeting's Prep section. Can reach: your mail (read), your meetings (read)
We shipped 10 starter routines to get you going, including meeting prep, a morning briefing, a Friday weekly review, an action item sweep, and follow-up drafts.
🔒 You told us you didn't want a black box
The biggest hesitation around letting AI act on your behalf was trust. So permissions are two separate settings, not one slider: machine access (can it touch files and run commands on your Mac?) and state change (can it change anything, anywhere?). Every new routine starts read-only and sandboxed. Autonomy is something you turn on, not something you have to turn off.
📎 Connectors, so it can reach your other tools
Gmail, Outlook mail, Notion, and web search are connected now. Every connector tells you what it can reach in plain language (read your mail, draft replies, send mail) instead of a scope string you have to decode yourself. And any limit you set gets enforced on the request itself before it leaves your machine, so it's a real boundary, not just a setting you hope holds.
🔌 Webhooks, because Hyprcore doesn't need to be your whole stack
If you already run automations elsewhere, a routine can post straight to your own endpoint instead of running the AI at all. Signed, retried automatically, and logged down to the byte. Plain HTTP is allowed on localhost too, so a self-hosted n8n never needs a public relay.
💸 On usage: we heard you there too
Connector calls draw from your monthly allowance, same as before, but we added real ways to run routines without spending it down. Routines that only read your own meetings and notes are unmetered, and you can bring your own API key or run everything through your own Claude Code subscription instead.
Also in this release: Quick Ask, a keyboard shortcut you can summon from anywhere to ask your own meetings and notes a question on the spot.
None of this changes how your data is handled. Everything is still local-first, still yours, and every routine lives as a plain markdown file in your vault that you can open, edit, or delete whenever you want.
Full release notes: hyprcore.ai/updates
Thanks for pushing us here. Keep the feedback coming.
— Adil & the Hyprcore team