openclaw sync: preflight-probe the AIMA proxy and warn loudly if unreachable#91
Open
rjckkkkk wants to merge 1 commit into
Open
openclaw sync: preflight-probe the AIMA proxy and warn loudly if unreachable#91rjckkkkk wants to merge 1 commit into
rjckkkkk wants to merge 1 commit into
Conversation
…achable
`aima openclaw sync` writes an OpenClaw provider that points the chat data
plane at the `aima serve` proxy (default :6188). Two real-world integration
failures both surface inside OpenClaw as an opaque "connection error/timeout"
that looks nothing like a config problem:
1. Only the MCP control plane (`aima mcp`) is wired, so nothing is serving
:6188 — the provider has no listener to reach.
2. An HTTP_PROXY/HTTPS_PROXY env intercepts loopback; OpenClaw runs on Node
and routes 127.0.0.1 through the proxy, so it times out even though curl
(which bypasses the proxy for localhost) works.
Probe the proxy address during sync with two requests — one direct, one
honoring the env proxy — so the warning names the actual failure mode and the
fix. Surface it both as a loud slog.Warn and as proxyReachable/proxyWarning on
the sync result (so software embedding AIMA can show it in their own UI). The
probe never blocks the config write; it only adds a diagnostic.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rjckkkkk
added a commit
that referenced
this pull request
Jun 12, 2026
) New version-stamped build aima-windows-amd64-v0.5-dev-amd-strix-halo-20260612.exe (source commit fa35aa4) on top of the HIP-engine build. Adds, vs the 20260610 exe: #87 native deploy readiness uses the real runtime name (no false "not ready") #88 deploy launcher hidden (no cmd.exe console popup) via VBS launcher #89 Qwen2.5-VL-3B-Instruct catalog knowledge (vlm + aliases + verified perf) #90 zero-config vision: llama.cpp --mmproj auto-wired for VL gguf models #91 openclaw sync preflight-probes :6188 and warns loudly when unreachable serve.bat now points at the 20260612 exe; older builds kept for rollback. README build table + fixes list + OpenClaw data-plane guidance updated. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
aima openclaw syncwrites an OpenClaw provider that points the chat data plane at theaima serveproxy (default:6188). This adds a preflight that probes that address during sync and surfaces a loud, actionable warning when it is unreachable — instead of letting the failure show up inside OpenClaw as an opaque "connection error / timeout".Why
Two real partner-integration failures both look identical from OpenClaw (Node) — an opaque connection error/timeout that resembles nothing in the config:
aima mcp --profile operator(what OpenClaw auto-launches) serves STDIO and does not open:6188. Ifaima serveisn't running separately, the provider has no listener to reach.HTTP_PROXY/HTTPS_PROXYenv intercepts loopback. OpenClaw runs on Node and routes127.0.0.1through the proxy, so it times out even thoughcurl(which bypasses the proxy for localhost) works.Every in-band proxy error is already fast and legible (wrong key → 401, wrong model → 404, dead backend → 502). A genuine timeout therefore means a connection-level failure to
:6188itself — exactly the two cases above.How
probeProxyReachableruns two probes against<proxyAddr>/models:aima servelistening at all?http.ProxyFromEnvironment) — mirrors clients that honorHTTP_PROXY, so we can tell "serve down" from "proxy intercepting loopback".The result is exposed both as a loud
slog.Warnand asproxyReachable/proxyWarningon the sync result (so software embedding AIMA can render it in their own UI). The probe never blocks the config write — it only adds a diagnostic.Test
TestProbeProxyReachable(server up / down / empty-addr) +go vetclean.proxyReachable: true, no warning; serve down →slog.Warn+proxyReachable: false+ a warning pointing ataima serve(and notingaima mcpdoes not open the port).🤖 Generated with Claude Code