Productivity
File my invoices
Photograph a receipt and it's filed, named, and added to a spreadsheet you can total up.
Automations
The work you keep redoing, wired up once.
Drag a few nodes into a row and your Mac runs them for you. Read the file, pull out what matters, put it where it belongs, tell you it's done. The watching and the thinking both happen here, on your machine.
Every automation you have, in one list
What it runs on, when it last ran, and whether it worked. Nothing happens invisibly.
See it in action
Three minutes, one real flow.
Built on the canvas, run live, and the result lands in the notch and on a phone. No mockups: this is the app, recorded on a Mac.
How it works
Four small steps, then it just runs.
01
Start it however you like
Say what you want in a sentence, open a template, or drop the first node on a blank canvas. All three land you in the same place.
02
Pick what sets it off
A new email, a message, an issue, a page that changed, a time of day, or you pressing Run. One flow can have several, all feeding the same steps.
03
Wire up what happens
Drag from one node to the next. Split the path in two when the answer matters. Every node does one job you can read off the card.
04
Watch it run
When it fires for real, the canvas lights up node by node, so you can see where it went and what each step actually produced.
The line that matters
Every node tells you what it's allowed to do.
There's no fine print to go hunting for. Each step wears a small badge on the canvas, and the badge is the rule. You can see the whole consent model of an automation by looking at it.
Auto
Runs on its own
Reading, summarizing, filing, tagging, nudging you. Nothing here reaches anyone else or leaves your Mac, so it just happens.
One tap
Waits for you
A reply, a message into Slack, an issue filed, a task handed to a coding agent. Halo writes it and holds it. You look, then you press send.
Leaves Mac
Goes to the internet
A request to an address you typed, or a tool on a server you connected. Marked on the card so you never have to guess which steps are local.
So, does it send things on its own? Only if you tell it to. Out of the box a message or a reply is prepared and waits for your tap. If you'd rather one particular automation just send it, you can say so when you make it, and that automation says so on its card from then on. A shell step is the same idea: the ordinary ones run, and anything reaching for your whole disk or the wider system stops and asks first.
What sets it off
One flow, as many ways in as you need.
A trigger is its own node, so a flow can have several. An invoice you photograph and an invoice that arrives by email can walk exactly the same steps, and neither one needs to know the other exists.
The screen trigger is the quiet unlock: if Halo can see it on your screen, it can watch for it, even in an app with nothing to connect.
- A new email, from your inbox or any account you connected
- A message in Slack, Teams, or iMessage
- An issue assigned to you, a status change, a comment, or an @mention
- A pull request waiting on your review
- A calendar event, or a time of day you pick
- A photo or a PDF you send it on Signal, from your phone
- A website that changed, even the heavy ones
- Anything on your screen, in any app
- A result changing on a tool you connected
- You pressing Run
The nodes
Small jobs that snap together.
Each one does a single thing and hands the result to the next. Most of them never touch the internet, and the ones that do say so on the card.
Understand it
Read the thing that arrived and make sense of it, on your Mac.
- Ask the AI
- Extract
- Classify
- Summarize
- Read a file
- Your memory
Decide where it goes
Split the path, keep only what matters, or stop early.
- Branch
- Switch
- Filter
- Merge
- For each
- Stop
Shape the data
Plain, predictable reshaping with no model in the loop.
- Transform
- Sort
- Limit
- Remove duplicates
- Split out
- Summarize data
- Keep track
Do it on your Mac
The things your Mac already does well, done for you.
- Save a document
- Add a reminder
- Add to Calendar
- Add a note
- Copy to clipboard
- Run a shortcut
Reach you, or someone else
A nudge, a draft in your voice, or a message into an app you connected.
- Notify
- Draft
- Send to an app
- Tag
Pictures and video
Resize, crop, clean up, or make something new. The plain edits need no model at all.
- Get files
- Resize image
- Crop image
- Remove background
- Adjust image
- Convert image
- Add text
- Take a frame
- Trim video
- Convert video
- Make a picture
- Change a picture
- Make a video
- Open it
Wait for the right moment
Pause inside a run, or park it and pick it up later.
- Delay
- Wait
Go further
The escape hatches, for when a ready-made node isn't enough.
- HTTP request
- Code
- Shell command
- Connected tool
- Delegate to agent
- Delegate to a CLI agent
- Sub-flow
Per step, not per app
Choose the brain for each node.
Every thinking step has its own small lane under it where you pick what runs it. Leave the whole flow on your Mac, or send just the one step that needs more muscle somewhere bigger.
-
On your Mac
The default for every step. Nothing leaves, and it keeps working with the wifi off.
-
Your own key
Bring an account you already pay for. The key lives in your Keychain and your Mac talks to them directly.
-
A Halo plan
For the heavier steps, without setting anything up. Off unless you choose it.
When a node isn't enough
Three ways out of a flow.
-
Connected tools
Point Halo at a server you run or trust and its tools become nodes you can drop in. Halo keeps no special code per service, so a tool that server adds tomorrow shows up on its own.
-
A request, or a few lines of code
Call any address that speaks HTTP, or write a short snippet to reshape whatever came through. For anything else there's a shell step.
-
Hand it to an agent
Pass the job to one of your standing agents, or stage it for a coding agent in your terminal. That last one always waits for your go-ahead.
Pictures and video
It can work on files, not just words.
Point a flow at a folder and the nodes that handle files can read from it. Resize a batch, crop them, strip the background, put text on them, pull a frame out of a video, or read what a photo actually says. The plain edits use no model at all, so they're instant and they're free.
Then there are the three that make something new: make a picture from a description, describe a change across pictures you already have, or make a few seconds of video. Those need a brain behind them, which you pick per step like any other.
Files an automation makes are kept apart from your own and cleaned up on their own, and nothing outside the folder you picked can be opened, not even by an automation you imported.
Product shots, done on arrival
Get files Remove background Resize image Add text Save a document
A receipt becomes a row
Read a file Ask the AI Keep track Notify
One clip, three sizes
Get files Trim video For each Convert video
Templates
Or start from one that already works.
Open a template and it lands on the canvas fully wired, yours to change. Every one is a real job someone wanted doing, not a feature demo.
Productivity
Before every meeting
Ten minutes ahead: who they are, what you last discussed, what's still open.
Communication
Chase my follow-ups
Emailed someone and heard nothing? Draft the nudge three days later.
Developer
PRs waiting on me
A short gist of what changed and why, so review starts faster.
Developer
Yesterday's errors into tickets
Group them, file them, hand them to an agent.
Monitoring
Watch a competitor
Only tells you what changed, and why it matters.
Developer
Write my standup
What you closed yesterday, drafted before the call.
Productivity
What did I actually do?
A Friday look back at where the week really went.
Monitoring
Poll a connected tool
Anything with a connected server: your error tracker, your logs, your own.
Living with it
Always inspectable, always reversible.
Watch a real run
Press Run and the canvas lights up node by node as it goes. Each card shows what that step actually produced, so a flow that went sideways shows you exactly where.
Just ask it about itself
Every automation has its own chat. Ask why it did that, ask it to run now, ask it to pause. It answers from its own steps and its own history, not from a guess.
A history for each
Every automation keeps a log of what it found, so you can look back long after a nudge has scrolled away. Pause, edit, or delete any time.
A note on sleep. Because the thinking happens on
your Mac, automations watch while your Mac is awake. When it wakes, Halo
checks in and asks whether to keep watching, or you can set one to run
continuously and catch up quietly on its own.
Wire it once
Build it in an afternoon.
Forget about it for good.
The receipts that pile up, the follow-up you never send, the page you keep refreshing. Drop the nodes in a row, and your Mac takes it from there. On your machine, where you can see every step.