Routines overview

A routine is a standing instruction Hyprcore runs for you. It wakes up on a trigger, does the work with the access you grant it, and reports back — so a brief on the people you are about to meet is waiting before the call, and a draft follow-up is waiting after it.

You write the instruction in plain language. There is no workflow to build and nothing to wire together.

Routines are available on every plan, including Free. What differs by plan is your monthly allowance of connector calls — what a routine spends when it reaches Gmail, Outlook, Notion, or web search on your behalf.

What a routine is made of

Every routine has four parts, and the editor asks for them in this order:

• When — the trigger that starts it.

• What it does — your instruction, written in plain language.

• How much rope — how far it is allowed to go.

• Where it lands — what happens with the result.

Open Routines

Click Routines in the sidebar. The page lists everything you have, grouped by health — a routine that needs attention sorts above five working ones, so a broken one never hides in the middle of the list.

Create a routine

There are three ways in, from the New routine button.

From a template

Ten routines come already written. Pick one and it fills in the editor — it does not create anything. Nothing runs until you click Create routine, and you can change every part of it first.

• Meeting prep — 30 minutes before meetings with external guests: who they are, the last threads with them, and what you promised last time.

• Morning briefing — your calendar, unread mail that needs a reply, and open commitments. 8:00 on weekdays.

• Weekly review — Friday at four, what was decided and what carries into next week, grouped by project.

• Action item sweep — Monday mornings, commitments you own that have not moved.

• Follow-up drafts — after a meeting, a draft reply to the attendees for you to review.

• Research brief — a company you are about to meet, looked up before you walk in.

• News watch — a topic you are tracking, and only what is actually new.

• Push to an automation, Meeting started ping, and Full meeting export — three webhook routines that post to your own systems.

Templates with [bracketed] spans are waiting for you to fill something in. The editor highlights them and warns while any remain.

Describe it

Choose Describe a routine, say what you want in a sentence, and Hyprcore drafts one from the tools you actually have connected. You get a draft to review, not a running routine.

Blank routine

Start from an empty editor.

Choose a trigger

On a clock

• Every day at a time you pick

• On chosen weekdays

• Every N hours

• Custom schedule for anything else

Each shape ends in a plain-English restatement of what you picked, and the editor tells you how often it would fire — "Based on this trigger, it would run 5 times a week" — so there is no cron guessing. Set the Time zone here too.

On something happening

• Before an upcoming meeting — a number of minutes ahead of a calendar event. You can narrow it to only meetings with guests outside your company, only ones with a join link, or specific calendars, and skip meetings you have declined.

• When a meeting starts — as recording begins.

• After a meeting ends — once a recorded meeting finishes.

Only when I ask

The routine never fires on its own. This is the default for anything new.

Triggers for incoming mail, files landing in a folder, and notes shared with you appear in the menu marked soon. They are not available yet.

How much rope

Two settings control a routine, and they are deliberately separate. One is about your machine; the other is about change. "Draft my replies but never touch my disk" is a normal thing to want, and a single slider cannot say it.

Machine access

• Sandboxed — can read the web, use memory, and message you. Cannot run commands or change your files. This is the default.

• Unrestricted — can run commands and change files on this Mac.

What it may change

• Read only — it will look and report. It will not send, label, move, or delete anything. This is the default.

• Approval — it prepares the change and waits for your yes.

• Autonomous — it does the work and tells you after. This unlocks only after a routine has run under approval a few times.

A new routine starts manual, sandboxed, and read only. You change that yourself, on purpose.

Give it tools

The Tools section lists what the routine may reach. Your meetings, notes, people, and open commitments are built into Hyprcore and available without connecting anything. Gmail, Outlook, Notion, and web search appear once you connect them — see the Connectors article.

If a routine needs an account you have not connected, the editor says so before you can create it: "This routine reads from Gmail. Connect an account with that access before it can run."

Where results land

• A quiet notification with the result — and you can tell it to stay quiet when a run found nothing.

• Save each run as a note in a folder you choose, so there is a record you can search.

• Deliver into a meeting's Prep or Follow-up section, which is how meeting prep gets in front of you at the right moment.

You can also set quiet hours, so a routine never runs between the times you pick.

Test before you trust it

Once a routine exists, Send test runs it once, immediately, in read only, and shows you the result. It cannot change anything on a test run regardless of its settings.

After it runs

Every run is accounted for in the run log: what fired it, what it called, what it produced, and what it cost in tokens. Runs that stopped for approval appear as a card you can review and answer — approving one resumes the run from where it parked rather than starting over.

Results are raised as notifications app-wide, because a routine runs while you are somewhere else and a result only visible on the Routines page is not a result.

Where routines live on disk

Each routine is a plain markdown file in your vault, under .routines. Open it in any editor, keep it in version control, or delete it — the same as everything else Hyprcore stores. You can also export one to a file and import it on another machine.

Scheduling bookkeeping — when it last ran, when it runs next — is kept separately, so a routine file that syncs between your machines does not rewrite itself on every tick.