HEADING OS

One person.
An army of agents.
Nothing leaves
without your yes.

HEADING OS is the command post an executive runs their work from: mail, meetings, relationships, research and documents. It runs on your machine, and your data lives in your own private repository.

Source code opens soon under the Apache-2.0 licence. The list hears first.

A draft never leaves until you approve it. The send happens in that command, not in the background. Names in this example are invented.

Where an executive's week goes

  • Chief executives spent 72% of their working time in meetings, 37 of them in an average week. Porter and Nohria, How CEOs Manage Time, Harvard Business Review, 2018. Twenty-seven CEOs tracked for 13 weeks.
  • People working in Microsoft 365 are interrupted every two minutes by a meeting, an email or a notification, and receive 117 emails a day. Microsoft, Breaking down the infinite workday, Work Trend Index, 2025.
  • 48% of privacy and security professionals admit entering non-public company information into generative AI tools. Cisco, 2024 Data Privacy Benchmark Study, 2,600 respondents.

The work is not too hard. It is too scattered, and the tools that promise to gather it want your data on someone else's servers.

A day with HEADING OS

morning dashboard, 07:30

Calendar3 meetings, first at 10:00

Mail41 new, 6 need you

Going coldDana Reyes, 38 days

Leo Park, 52 days

PipelineNorthwind moved to proposal

Radarbackup due today

One page before the day starts. Names and numbers in this example are invented.

  1. morning dashboard

    Calendar, mail, relationships going cold and the deals that moved, on one page. A separate radar tells you which routine you have let slip.

  2. process my inbox

    Mail grouped by conversation into one digest, with suggested actions and replies drafted in your voice. Nothing goes out until you approve it.

  3. prepare me for the 14:00

    A brief on the person you are meeting: your history with them, your earlier correspondence, a plan for the conversation and three questions worth asking.

  4. research the shortlist, in parallel

    Several agents work at once, each in its own yard, and hand back one summary with sources.

  5. what did we decide about pricing?

    An answer from your own records, with the file it came from. Memory that survives the session, and belongs to you.

A command post, and an army that cannot touch it

One session is yours. It holds everything live: your mail, your calendar, the background services, and every send.

Agents do the work beside it, each in its own copy of the system. They can research, write and build. They cannot send, and they cannot start, stop or change anything that is running.

How it works

You run the command post. Three agents work in isolated copies beside it and hand their work back. Command post you, mail, calendar, background services, sends Agent isolated copy Agent isolated copy Agent isolated copy
Only the command post can send, run services or change what is live. Agents hand their work back to it.

Three guarantees, held by code

Each one is enforced by code on the commit, push or send path, not by a sentence in a policy.

Your data never ships with the code

The engine and your data live in two separate repositories. Seven mechanical layers stop a private file from reaching the engine, including on a push.

Nothing leaves without your yes

Every outbound message is a draft. It is sent only when you type the approval, in that command. An unknown kind of action is treated as a send and waits for you.

Your memory belongs to you

What you decided, promised and learned is kept in files in your private repository and indexed on your machine. A new session starts from it, not from zero.

What it does not do

  • It does not replace people. It gives one person more reach and keeps them accountable for every action that leaves.
  • It does not hire for you, and it will not fix burnout. It removes some of the scatter that feeds it.
  • It does not run in a browser. You work in a terminal, through Claude Code, on Linux, macOS, or Windows with WSL2.
  • It is not free to run: it needs a Claude subscription, and some features need other services.
  • It is not finished. The current version is v0.14.0, and interfaces may change before 1.0.

Install it yourself, or have it installed

The source opens soon. When it does, you can install it yourself, or ask for an installation and ongoing support.

I want to

One email when the source opens. Your address stays with the author and is used for nothing else. Privacy