Halo
Halo ghost

macOS overlay · capture stays local

The router
at the caret.

Highlight anything — or say Hey Halo. Pick an app you already enabled. Send a context pack. Nothing leaves until you click.

Join the waitlist See a send

⌥⇧H Destinations are Cursor, Linear, Gmail, Docs — not “Halo the agent.”

Slack · engineering
maya 2:14 PM

The checkout button on staging is 4px off the grid and the error copy is still lorem.

The bar docks above the highlight. Recommended logo first. Send is the gate.

The last inch

Whatever you’re looking at, in the app you’re in,
sent to the app you choose — and nothing else.

01

Highlight, point, or speak

Drag a rectangle. Sit the pointer on a DoorDash item. Or say Hey Halo. Halo stores a screenshot, the selection, the URL — on this machine.

02

Pick an app you enabled

The bar shows logos you already turned on. Ranking and ads never invent a destination. You are the gate.

03

Send. Stay where you are.

That click is the moment data leaves — and it only goes to that app. The bar lets go. Linear, Docs, Cursor work in the background.

Positioning

Not a canvas. Not an agent you visit.

People will compare Halo to n8n and Claude Cowork. They solve different jobs. Halo should not win by becoming either.

vs n8n

n8n is a graph. Halo is a highlight.

n8n is excellent when systems already emit events. It is not sitting on your screen. It does not know which paragraph you just highlighted, or that you meant this DoorDash item.

  • n8n when the trigger is an API — webhook, cron, Stripe, GitHub.
  • Halo when the trigger is what you are looking at.
  • A webhook destination can feed n8n. If Halo becomes a node editor, we lost.

vs Claude Cowork

Cowork is a worker you visit. Halo shows up where you already are.

You leave the source app, open Cowork, describe an outcome, come back later. Halo stays on the ACS tab or Slack thread and ships a pack to an app you already use.

  • Cowork when the job is multi-step and Claude should author the artifact.
  • Halo when the job is put this in that app.
  • A model behind an adapter is optional glue. Cowork’s product is Claude.
Halo n8n Claude Cowork
Job This pixel, this click, that app This event, this graph, those APIs This goal, this session, come back later
Trigger Highlight, pointer, or Hey Halo Webhook, cron, app event You open Cowork and describe an outcome
Who executes The destination app n8n nodes on a server Claude, with files, browser, plugins
You stay in Slack, ACS, Gmail, Cursor The n8n canvas Claude Desktop / Cowork
Data leaves Explicit send, one destination Whenever a node runs Throughout a session

What Halo must not become

A thinner Cowork that still needs the user to paste.

A smaller n8n with worse connectors.

A chat that sits on the desktop and “helps with work.”

Destinations

Send into the apps you already live in.

Halo does not replace Linear, Gmail, or the inbox. It ships a context pack into them. Compete on intent at the caret — not connector count.

Privacy

Nothing leaves on highlight.

Capture is local. Screenshot, selection, URL stay on this machine until you click a logo. Then the pack goes to one destination — the one you picked — and nowhere else. Users enable. Ranking never inserts an app you turned off.

Marketplace

A storefront at high intent.

The overlay is the surface. What people build and sell are agents for one job at the caret — Slack → Linear, HubSpot → slide 3 — not general assistants. Apps bid for the recommended logo, only among destinations you enabled.

Listing Appear in the catalog a user can enable.
Routing A fee when they actually send to you.
Default bid Compete for the recommended slot. Never for apps they didn’t opt into.

Own the last inch.

Private macOS beta. Highlight, send, stay. We’ll write when it’s your turn.