A host is a machine running jaidu-agent. The control plane stores projects, issues, comments, and routing state, but host-side work runs on a registered host through the relay tunnel. You need at least one online host before you can open Main Chat or create workspace threads.

​
What A Registered Host Provides

The selected host owns:
  • the project filesystem and workspace folders;
  • Git branches, worktrees, diffs, and pull request actions;
  • terminal commands and execution processes;
  • Codex threads and approval prompts;
  • preview/dev-server traffic exposed through relay.
The control plane authorises and routes requests. It does not execute code directly.

​
Registration Path

Jaidu registers hosts through pending approval. The agent asks to join the control plane, an authenticated admin approves the request for an organisation, and the agent receives rotating API keys.

​
Register A jaidu-agent Host

Use this path to understand what happens when a machine is registered for Jaidu work. Installation, manual start, systemd service setup, logs, and update commands are kept with the current public agent release instructions.
1

Start jaidu-agent on the host

Start jaidu-agent on the machine that should own filesystem, Git, terminal, Codex, and workspace execution. The running agent contacts the control plane and creates a pending machine registration.
2

Approve the pending machine

In Settings → Remote Access, select the correct organisation, review Pending machine registrations, and approve the expected machine. Match the displayed host_name and machine_id against the machine you started.
3

Wait for the host to connect

The running agent polls the registration while it waits. After approval, it stores agent_auth.json, connects through relay, and appears under Registered hosts. No terminal input is required on the agent side.
Host registration always ends with a registered host connected through relay. Old browser-local onboarding paths are not current Jaidu user flows.

​
Troubleshooting

Check that jaidu-agent is running, that it is configured with the correct control-plane API base, and that the host can reach the relay base.
The control-plane registration succeeded, but the relay tunnel is not connected. Check JAIDU_SHARED_RELAY_BASE, host logs, and network access to the relay.
The agent refresh key expired, was revoked, or was reused after its grace window. Delete the host’s agent_auth.json, restart jaidu-agent, and approve the new pending registration.
Select the intended host in the app bar or route, then configure Main Chat for that host and project root. Main Chat bindings are host-specific.