Authentication
Halo uses your Memcode account. One sign-in works for both Halo and the Memcode CLI.
Halo signs in with your Memcode account. You do not need the Memcode CLI installed.
halo loginopens your browser at memcode.ai. After you sign in, the key is saved where the
Memcode CLI keeps it, ~/.config/memcode/.env (readable only by you). That
means:
- if you already use the Memcode CLI, Halo is signed in already;
halo loginsigns the Memcode CLI in too, andhalo logoutsigns both out.
Halo never reads a .env file in the folder you are working in, so a project
cannot sign Halo into another account.
What the key is used for
Halo presents the key once when it connects, and the service exchanges it for a short-lived session. The key identifies your account to the Halo service. It is not permission to do anything on your computer: that is always decided on your machine.
CI and scripts
Set MEMCODE_API_TOKEN in the environment to use a key without signing in.