Translation out of date
The source content changed after this translation. See the Português version. View original
Enable a machine
Online and offline, the allow, ask and deny policies, via command line and interface.
Updated on Sep 16, 2026
A machine only receives remote sessions if it is online on the hub and has a policy that allows it. Both are configured via command line or interface, and apply to the running process (interface or serve).
hinow-cli connect online # ficar visível para as suas outras máquinas
hinow-cli connect offline # sumir (o login continua)
hinow-cli connect allow # aceitar sessões remotas sem perguntar
hinow-cli connect ask # perguntar antes de cada sessão (padrão; precisa da interface aberta)
hinow-cli connect deny # recusar sessões remotas
hinow-cli connect status # como esta máquina está
hinow-cli connect devices # quem mais está online agoraCommands save the preference and the running bridge reacts in seconds: online reconnects, offline disconnects, policy changes immediately. A machine running only serve should be in allow.
$ hinow-cli connect devices
HiNow Code · servidor-01
b63b837f5c69… · vmi3525429 · linux/x64 · 9ms
HiNow Code · notebook
087cadfbb2c1… · teclia · linux/x64 · 204ms
run something there: hinow-cli run --machine <name> --remote-dir <folder> "…"In the right sidebar there is a dot: green when the machine is online on the hub, off when not. Click it (or open ctrl+p → Remote control) to go online or offline and choose between Allow remote sessions, Ask before allowing and Do not allow. With ask, each remote session appears as a request on screen, showing who requested it and which folder.
While you decide, the requester sees awaiting authorization (on chat.hinow.ai, in the conversation language) and the first message is already queued: if approved, it runs next. The request is valid for 90 seconds; without response, or if refused, the requester receives the reason and nothing runs here. Within the same conversation, approval applies to following messages: only a new conversation requests again.
| Policy | When to use |
|---|---|
allow | Servers and headless machines (serve). You already own it: whoever enters is your account |
ask | Your work machine, with the interface open: you see and approve each session |
deny | Machines that should not execute anything from outside, even if online |
Each installation gets an identity (device.json) with a name, HiNow Code · <hostname>. This name appears in the list and is what you use in run --machine. The name is in ~/.local/share/hinow/hinow/device.json and can be edited; the id cannot.
Revoke remotely
On chat.hinow.ai (Remote tab) you see all machines in your account and can disconnect any one. The revoked machine stops trying to reconnect until a new connect online.