mirror of
https://github.com/hanzoai/cli.git
synced 2026-10-30 15:00:27 +00:00
zeekay
437866cbfe
hanzo dev starts every coding session: our own agent by default, another tool as a flag (--claude, --codex, --cursor, --agy), the rest after --. hanzo code keeps only the code index and hanzo run is gone; each old launching spelling exits 2 with one line naming hanzo dev. A third-party tool now talks straight to the account it is signed in to. --cloud opts into Hanzo's metered models, and --no-route is removed, being the default. Hanzo Dev's account is Hanzo's, so it still routes when signed in. 8.5.700.
25 lines
849 B
Desktop File
25 lines
849 B
Desktop File
# Keep this machine present in the fleet between sessions.
|
|
#
|
|
# systemctl --user enable --now units/hanzo-beat.service
|
|
# loginctl enable-linger $USER # beat at boot, before anyone logs in
|
|
#
|
|
# It runs the ONE beat that `hanzo dev` and `hanzo link` already hold while they
|
|
# run — so a box at an idle prompt is not read offline by the console and by
|
|
# whatever is choosing where the next session lands. Nothing else: no shell, no
|
|
# session, one best-effort request every 30 seconds.
|
|
[Unit]
|
|
Description=Hanzo fleet presence
|
|
After=network-online.target
|
|
Wants=network-online.target
|
|
|
|
[Service]
|
|
ExecStart=%h/.local/bin/hanzo beat
|
|
Restart=always
|
|
RestartSec=30
|
|
# A beat that cannot reach the API changes nothing about this box, so never
|
|
# spin on it — the scheduler already reads the machine as offline.
|
|
Nice=19
|
|
|
|
[Install]
|
|
WantedBy=default.target
|