fix(cli): don't demand local daemon config when the daemon is explicitly remote#1567
Merged
Aaronontheweb merged 2 commits intoJul 3, 2026
Conversation
…tly remote netclaw-dev#1540's chat preflight blocks with 'daemon not configured' whenever the local netclaw.json is missing — but NETCLAW_DAEMON_ENDPOINT and paired-client (client.json) endpoints mean the daemon's config lives on the daemon host. This regressed paired/remote clients and broke the containerized eval harness (every case failed 0/5 with 'daemon not configured' from the host CLI). Preflight now stands down when either endpoint source is present — the same sources DaemonApi.ResolveEndpoint prefers over local daemon config.
Aaronontheweb
enabled auto-merge (squash)
July 3, 2026 17:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
#1540 added a chat preflight that blocks with
daemon not configured - please run netclaw initwhenever the localnetclaw.jsonis missing. But "no local daemon config file" does not mean "no daemon": two supported client topologies are file-less by design, and both regressed:NETCLAW_DAEMON_ENDPOINT=… netclaw chatagainst a daemon configured elsewhere (this is how the containerized eval harness drives its daemon — every eval case has failed 0/5 with this message since Require explicit main model configuration for degraded startup #1540; last green run was 2026-06-24 on 0.24.1).client.json(endpoint) but no localnetclaw.json.The daemon side was never broken — a container daemon configured purely via
NETCLAW_*env vars starts healthy. The CLI preflight just conflated "no local config file" with "nothing to talk to."Fix
The preflight stands down when either remote-endpoint source is present — the exact sources
DaemonApi.ResolveEndpointalready prefers over local daemon config:NETCLAW_DAEMON_ENDPOINTenvironment variableclient.jsonendpoint#1540's protection is preserved for the case it was written for: a truly local, truly unconfigured install still gets the clean init guidance instead of a degraded startup.
Testing
CliConfigPreflightTestspass.daemon not configuredbefore any prompt reached the daemon) to executing cases normally with this fix applied.Found while running the memory-pipeline eval gate for the (separate, upcoming) memory quick-wins PR.