Translation out of date
The source content changed after this translation. See the Português version. View original
Use from elsewhere
From the terminal, from the command line, from the web and from mobile. Scenarios and reference times.
Updated on Sep 16, 2026
With a machine unlocked, you start a session on it from anywhere else. The conversation stays with you; the work happens there.
- 1
Open HiNow Code where you are
In any folder; the local folder doesn't matter, the work will be on the other machine.
- 2
Click This machine
It's the machine chip on the prompt line (or
ctrl+p→ Run on). The list shows your online machines, with the ping for each one. - 3
Choose the folder
The selector navigates the folders on the other machine. Type to search;
ctrl+ncreates a new folder;ctrl+hshows hidden ones. - 4
Chat as usual
The chip now shows the machine name and ping. Each message runs there; approvals arrive on your screen.
hinow-cli run accepts --machine (name or id from hinow-cli connect devices) and --remote-dir (the folder there; without it, the user's home folder on the other machine):
hinow-cli connect devices
hinow-cli run --machine "HiNow Code · servidor-01" --remote-dir /srv/loja "Rode os testes e corrija o que falhar."running on HiNow Code · servidor-01 in /srv/loja · 9ms
> build · hinow/hicode
🔧 bash
🔧 edit
🔧 bash
Dois testes falhavam por causa do fuso horário no helper de datas; corrigi src/util/date.ts e agora os 38 passam.It also works with --format json and with --attach, when you already have a hinow-cli serve running locally and prefer to use it as the initiator.
If the interface is open on this machine
It's the one holding the bridge with the hub, and run --machine warns: use the This machine chip on it, or point the run to a serve with --attach http://127.0.0.1:<port>.
On chat.hinow.ai and the HiNow app, the Remote tab lists your online machines. Choose one, choose the folder, and the conversation continues as on the terminal: approvals and responses arrive wherever you are. It's the way to command the server from the street, or request a deploy from your phone.
| Scenario | How |
|---|---|
| Secure the server | Install and leave it serving. Ask to review access logs, block IPs, close ports, apply updates. Each command with your approval |
| Deploy without leaving your phone | Ask to update the service, check if it's up and read the log |
| The code is on the desktop | From your laptop at home, work on the project that's on your office desktop, with its tools |
| CI and automations | hinow-cli run --machine in a script, with --format json to handle the result |
In a battery of real sessions between a workstation and an Ubuntu server in the cloud, via connect.hinow.ai: create a project and run the script, 15 s; create three files and list, 10 s; Python module with four tests, run, 19 s; initialize a git repository and commit, 31 s; a two-minute command on the server, 135 s end-to-end. Each number includes the startup of the local instance and the model time.