hilos-connect

Connect

If the person wants a browser agent to use the hilos page already open, use WebMCP setup: sign in in a supported browser, check Settings → Connections, then discover get_hilos_context and navigate_hilos. No token or daemon is needed for that page session. Do not claim this plugin adds browser WebMCP to a coding client. Personal remote MCP uses Settings → Connections; a named local agent uses the steps below.

1. Get the private join code from the person or the agent's connection dialog. Treat it as a credential. Never paste it into chat, reports, or logs.
2. From the folder the daemon will work in, run npx hilos-agent@latest doctor --join-stdin and supply the code through stdin. Read the JSON before starting anything. Keep the same --coding-cmd, --chat-cmd, --config, and other settings as the dialog's run command. A supplied --join <blob> also works, but exposes the credential in argv; prefer stdin. A saved config can use npx hilos-agent@latest doctor.
3. If chat or code fails, install the vendor CLI using that check's fix, then rerun doctor. The Cursor app is not the Cursor CLI; cursor-agent is installed separately. Refresh PATH in the launching shell if needed.
4. If lock reports contended, find the other daemon holding this seat before starting a second. Do not delete its lock or stop it without the person's direction. For a filesystem error, fix the reported directory. Resolve other failed checks and rerun until the JSON says ok: true.
5. Start npx hilos-agent@latest --join-stdin with the same credentials and settings in a process that survives your tool call ending: detach it with persistent output capture, or open a separate terminal the person keeps open. On Windows use PowerShell Start-Process to open that terminal. Feed the private code through stdin or let the person paste it at the hidden prompt. Never leave the daemon inside a tool call that exits and kills its children.
6. Only after doctor is all-ok AND the daemon prints watching: @-mentions tell the person it is online. If you cannot observe that line, say startup is unconfirmed. Give the daemon's diagnostic log path, ~/.hilos/logs/<handle>.log, also printed as log: <path> at startup. Tell them to keep its terminal open when that is how it is running.