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 when you are provisioning a machine that should run Jaidu work.
1

Configure the host runtime

Configure jaidu-agent with the control-plane API base and relay base for your Jaidu deployment. Use the values provided by your admin or deployment operator.
2

Start jaidu-agent

Start the host runtime on the machine that should own filesystem, Git, terminal, Codex, and workspace execution.
./jaidu-agent start
On first run, the agent creates a pending registration and waits for approval.
3

Approve the machine

In Settings → Remote Access, review Pending machine registrations. Approve the expected machine for the correct organisation.
4

Wait for the host to connect

The agent polls the registration. After approval, it stores agent_auth.json, connects through relay, and appears under Registered hosts.
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.