hey.food

Connect your account

Registration uses a short-lived device code. Identity verification, current agreements, and scope consent stay on auth.hello.food; the CLI never asks for your password.

heyfood register

Device authorization

  1. 01

    Start

    The CLI prints an approval URL and short code.

  2. 02

    Verify

    Complete email or SMS verification in the browser.

  3. 03

    Review

    Accept current agreements and inspect the exact requested scopes.

  4. 04

    Commit

    The client persists credentials only after the complete authorization response validates.

Headless and machine modes

heyfood register --device --no-browser
heyfood register --device --no-browser --json --timeout 600

JSON mode emits one terminal result and never launches a browser. One human approval is still required.