Translation out of date
The source content changed after this translation. See the Português version. View original
How HINOW Connect works
Initiator, executor, the hub, what travels, and the rules.
Updated on Sep 16, 2026
HINOW Connect links your machines. Each one, when you open HiNow Code (or serve), enters a room in your account on the hub connect.hinow.ai. A remote session has two sides: the initiator, where you chat, and the executor, where the agent works.
- 1
The executor machine becomes available
It runs the interface or
hinow-cli serve, is online on the hub, and has a policy: accept, ask first, or refuse. - 2
You choose the machine and folder
In the terminal (chip This machine), via command line (
run --machine), on the web (Remote tab in chat.hinow.ai) or in the app. - 3
The session starts on both sides
On the initiator, a shadow session shows everything; on the executor, the real session, in the chosen folder.
- 4
The work happens there
Reading, editing, commands, and tests run on the executor, with the tools and credentials there. Output returns through the hub in real time.
- 5
Approvals reach you
Each sensitive action appears on your screen; the executor waits for the response.
| Goes through the hub | Stays on the machine that executes |
|---|---|
| Your request, the response, the list of tools used, and approval questions | Project files, git, keys, and environment variables |
| Requests to list, search, and create folders (to choose where to work) | The commands executed and their complete outputs |
The connection to the hub is a TLS WebSocket (wss://connect.hinow.ai), authenticated with your account login. Only machines in the same account see each other.
- One bridge per machine. Only one process per machine talks to the hub: the interface, when open, or
serve. The interface has priority; when closed,serveresumes. - Executor without a screen needs
allow. With theaskpolicy, the interface responds; in a standaloneserve, the request expires. - The shadow session remains yours. It stays in the initiator's session list and can be reopened; the full history is on the executor.