memcode docs
Halo

Safety

What Halo does on its own, what needs your approval, and how you stay in control.

Halo does what you ask, shows what it's doing, and stops to ask when an action is dangerous or can't be undone.

Halo Research is experimental

The safeguards on this page reduce risk. They do not remove it. Halo can misunderstand a request, it can have bugs, and a correct action can still have unexpected results because of your machine's state or the tools installed on it.

During Research, don't use Halo on:

  • production systems;
  • machines where downtime or lost data would be costly;
  • systems that hold sensitive, confidential or regulated data;
  • critical infrastructure or business-critical environments;
  • anywhere an incorrect action could cause serious loss or disruption.

Halo Research is for hobbyists, developers, researchers and technical enthusiasts who understand they are trying experimental software, working on machines and folders where a mistake is recoverable. Read what Halo proposes before you approve a change, and keep backups of anything important.

Modes

Press Shift+Tab to switch modes. The current mode is shown at the bottom of the screen, and Halo remembers it.

ModeWhat runs without asking
Auto (default)everything you ask for, except what's dangerous or can't be undone
Askonly actions that change nothing; every change asks first
Allow alleverything, except what's catastrophic

You can also start Halo in a mode with halo --mode ask.

What Auto runs

Searching the web, reading pages, using the browser (opening sites, clicking, typing, filling in and submitting forms, attaching files), writing, editing and moving files, deleting to the Trash, Git, builds and tests, stopping a process you named, downloads and exports.

What still asks in Auto

ActionWhy
Deleting permanently, force-pushing, and other commands rated dangerousthey can't be undone
Administrator access (sudo) and commands on another machinethey reach beyond your account
Sending a file of secrets (keys, .env, credentials) to a siteit exposes them
Giving a site your camera, microphone or locationit exposes you
Anything catastrophic, such as erasing a diskasks in every mode

A multi-step job is shown whole and approved once when it asks.

Exactly what you approved

When you approve a change, Halo acts on exactly the files it showed you. Files that start matching afterwards are not added. If something changes after the preview, Halo stops.

Your working folder and the rest of your machine

Halo works in the folder you start it in. In Ask mode, reaching beyond it (other folders, running processes, network ports, system information) asks, and some of that access you can allow permanently. Administrator access always asks and is never remembered.

/permissions shows what you've allowed.

Commands you type with $

A line that starts with $ runs as a shell command directly, without the Halo service. It still gets the same local checks: risky commands ask first, and some commands are always blocked.

For how these guarantees are enforced, see Security architecture.

On this page