​
Agent Reports Empty Codebase

If Codex reports that the codebase is empty when you create a workspace, the repository on the host may have Git sparse-checkout enabled. Solution: Run the following command in the root directory of your repository: 
git sparse-checkout disable
After disabling sparse-checkout, create a new workspace or continue the thread and try again.

​
Host Is Offline

If a host is listed in Remote Access but appears offline, check the machine running jaidu-agent.
  • Confirm jaidu-agent is running.
  • Confirm the host can reach the control-plane API and relay.
  • Restart jaidu-agent if the relay connection was interrupted.

​
Pending Registration Is Not Visible

If the host does not appear under pending registrations, confirm that jaidu-agent was started with the correct control-plane API base and that the host can reach it. A host must create a pending registration before an admin can approve it.

​
Host Loses Authorization

If a previously registered host can no longer authenticate, restart jaidu-agent. If the stored host credentials are no longer valid, remove the host’s agent_auth.json, start the agent again, and approve the new pending registration.

​
Main Chat Project Folder Is Missing

Main Chat is bound to a folder on a specific host. If that folder was moved or deleted, reconfigure Main Chat for the project and host with the current folder path.

​
Codex Is Not Available On The Host

Install and authenticate OpenAI Codex on the host. Then reopen the Main Chat or workspace thread so Jaidu can start Codex from the host environment.

​
Workspace Cannot Start

Check that the selected host is online, the repository path exists on the host, and the workspace repository settings point to a valid target branch.

​
Preview Cannot Connect

The built-in browser preview needs a dev server script for the workspace repository. Configure the script in project or repository settings, then start the dev server from the preview panel.

​
Telegram Is Not Delivering

Confirm the Telegram account is linked to the correct Jaidu user, the user has access to the destination project, and the deployment has Telegram delivery configured.