fix: support explicit remote daemon endpoints#189
Conversation
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d1d2227941
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| port: url.port, | ||
| path: url.pathname + url.search, | ||
| method: 'GET', | ||
| timeout: 500, |
There was a problem hiding this comment.
In remote daemon mode, ensureDaemon gates every command on canConnectHttp, but the probe still uses a hard-coded 500ms timeout that was originally tuned for localhost. On higher-latency links (VPN, cross-region CI runners, busy reverse proxies), /health can exceed 500ms even when /rpc would succeed under the normal request timeout, causing false Remote daemon is unavailable failures before commands are sent.
Useful? React with 👍 / 👎.
1 participant
Summary
Support explicit remote HTTP daemon endpoints via --daemon-base-url / AGENT_DEVICE_DAEMON_BASE_URL and optional auth tokens, so the client skips local daemon discovery/startup and sends JSON-RPC directly to the configured remote daemon.
Add the matching CLI log-tail guard for remote debug mode, parser and transport tests, and docs updates. Touched files: 8. Scope stayed within daemon client/CLI/docs.
Closes #188
Validation