fix(gateway): accept port for health and probe by BryanTegomoh · Pull Request #94687 · openclaw/openclaw

BryanTegomoh · 2026-06-18T21:25:53Z

Summary

gateway health --port now targets a local gateway on the requested port instead of rejecting the option.
gateway probe --port now uses the requested port for the local loopback probe target and SSH tunnel remote port.
Port parsing is shared with gateway run style validation, so invalid values fail before transport.
Docs list --port for both commands.

Out of scope: no remote URL behavior changes, no gateway runtime changes, and no auth changes.

Review focus: CLI option inheritance, local target selection, and the new regression tests.

Linked context

Closes #79100

Related #91907

Was this requested by a maintainer or owner? No. The issue is labeled source-repro and queueable.

Real behavior proof (required for external PRs)

Behavior or issue addressed: openclaw gateway health --port ... and openclaw gateway probe --port ... no longer fail at option parsing and target the selected local gateway port.
Real environment tested: source checkout on Darwin arm64, Node v22.22.3, pnpm 11.2.2, isolated temp HOME, live local gateway on loopback port 19082.
Exact steps or command run after this patch:
- Start live gateway: pnpm openclaw gateway run --dev --allow-unconfigured --auth none --bind loopback --port 19082 --force --verbose
- Health proof: pnpm openclaw gateway health --port 19082 --json --token test-token
- Probe proof: pnpm openclaw gateway probe --port 19082 --json --timeout 3000 --token test-token
Evidence after fix: copied live output from real CLI commands against the local gateway:

{
  "command": "pnpm openclaw gateway health --port 19082 --json --token test-token",
  "ok": true,
  "durationMs": 51,
  "plugins": {
    "loaded": ["acpx", "bonjour", "browser", "canvas", "device-pair", "file-transfer", "memory-core", "phone-control", "talk-voice"],
    "errors": []
  },
  "defaultAgentId": "dev"
}

{
  "command": "pnpm openclaw gateway probe --port 19082 --json --timeout 3000 --token test-token",
  "ok": true,
  "capability": "read_only",
  "primaryTargetId": "localLoopback",
  "network": {
    "localLoopbackUrl": "ws://127.0.0.1:19082"
  },
  "targets": [
    {
      "id": "localLoopback",
      "kind": "localLoopback",
      "url": "ws://127.0.0.1:19082",
      "connect": {
        "ok": true,
        "rpcOk": true,
        "error": null
      },
      "health": {
        "ok": true
      }
    }
  ]
}

Observed result after fix: both commands accept --port, connect to the live gateway on ws://127.0.0.1:19082, and return successful health/probe results. The proof token was a disposable test value used only in the isolated temp setup.
What was not tested: live gateway execution on Windows.
Proof limitations or environment constraints: live proof was run on macOS only. It covers the reported CLI parsing failure and local loopback target selection, not Windows shell behavior.
Before evidence: gateway health/probe reject --port while gateway run accepts it #79100 reports that gateway health and gateway probe reject --port while gateway run accepts it.

Tests and validation

Focused coverage added:

shared gateway port parser accepts valid ports and rejects invalid strings/ranges
gateway health forwards --port into local gateway config
gateway probe forwards --port into status command options
status target resolution and JSON network hints use the override port

Commands run:

node scripts/run-vitest.mjs src/cli/gateway-port-option.test.ts src/cli/gateway-cli/register.option-collisions.test.ts src/commands/gateway-status/helpers.test.ts src/commands/gateway-status.test.ts
pnpm exec oxfmt --check --threads=1 src/cli/gateway-port-option.ts src/cli/gateway-port-option.test.ts src/cli/gateway-cli/register.ts src/cli/gateway-cli/register.option-collisions.test.ts src/commands/gateway-status.ts src/commands/gateway-status.test.ts src/commands/gateway-status/helpers.ts src/commands/gateway-status/helpers.test.ts docs/cli/gateway.md
pnpm exec oxlint src/cli/gateway-cli/register.ts src/cli/gateway-port-option.ts src/commands/gateway-status.ts src/commands/gateway-status/helpers.ts src/cli/gateway-cli/register.option-collisions.test.ts src/cli/gateway-port-option.test.ts src/commands/gateway-status.test.ts src/commands/gateway-status/helpers.test.ts
git diff --check
pnpm changed:lanes --json
env OPENCLAW_CHECK_CHANGED_REMOTE_CHILD=1 OPENCLAW_CHANGED_LANES_RAW_SYNC=1 CI=1 PNPM_CONFIG_VERIFY_DEPS_BEFORE_RUN=false corepack pnpm check:changed

Validation output:

Targeted tests: Test Files 4 passed (4), Tests 54 passed (54), passed 3 Vitest shards.
Formatter: All matched files use the correct format.
Direct oxlint on touched TypeScript files exited cleanly.
Changed lanes: core, coreTests, and docs.
Changed gate completed cleanly through typecheck, oxlint shards, and runtime guards.

What failed before this fix: command registration did not define --port on health or probe, so Commander rejected the option before the command reached gateway transport.

Risk checklist

Did user-visible behavior change? Yes

Did config, environment, or migration behavior change? No

Did security, auth, secrets, network, or tool execution behavior change? No

What is the highest-risk area? Local gateway target selection for health and probe.

How is that risk mitigated? The change only applies when --port is explicitly provided. Health still rejects --url with --port, and probe continues to preserve explicit remote URL behavior while adding the local port override.

Current review state

Ready for review. Waiting on ClawSweeper re-review and maintainer review.

clawsweeper · 2026-06-18T21:26:55Z

Codex review: found issues before merge. Reviewed June 21, 2026, 11:15 PM ET / 03:15 UTC.

Summary
The PR adds --port support for gateway health and gateway probe, threads local port overrides through gateway RPC/status resolution, updates docs, and adds regression tests.

PR surface: Source +96, Tests +238, Docs +10. Total +344 across 13 files.

Reproducibility: yes. Current main source registers gateway run --port but not child gateway health --port or gateway probe --port, matching the linked issue's unknown-option behavior.

Review metrics: 1 noteworthy metric.

Public CLI options: 2 added. gateway health --port and gateway probe --port become user-facing command contracts, so precedence, diagnostics, docs, and tests need to agree before merge.

Stored data model
Persistent data-model change detected: serialized state: src/commands/gateway-status.test.ts. Confirm migration or upgrade compatibility proof before merge.

Root-cause cluster
Relationship: fixed_by_candidate
Canonical: #79100
Summary: This PR is the strongest current fix candidate for the open gateway health/probe --port rejection issue; related duplicate PRs do not supersede it.

Members:

canonical: gateway health/probe reject --port while gateway run accepts it #79100 - The issue reports the exact gateway health --port and gateway probe --port unknown-option behavior and is linked by this PR's closing reference.
superseded: fix(gateway): accept --port for health and probe #95181 - This later open same-root PR has weaker proof and an existing ClawSweeper review pointing back to this PR as the canonical implementation path.
superseded: fix(gateway-cli): add --port option to gateway health/probe and RPC commands #94917 - This closed unmerged PR targeted the same issue with narrower wiring and missing real behavior proof.
superseded: fix(gateway): accept --port on gateway health and probe (#79100) #89623 - This earlier same-root PR is closed unmerged and no longer owns the remaining work.
superseded: fix(gateway): accept --port on gateway health and probe (#79100) #89555 - This earlier same-root PR is closed unmerged and had weaker proof than the current candidate.

Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything.

Merge readiness
Overall: 🦐 gold shrimp
Proof: 🦞 diamond lobster
Patch quality: 🦐 gold shrimp
Result: needs maintainer review before merge.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

[P2] Patch the health auth diagnostic path so it uses the selected --port target and add focused regression coverage for the credentials-required or unresolved-SecretRef error path.

Risk before merge

[P1] A credentials-required or SecretRef-unavailable gateway health --port <port> path can still probe/report the configured or env-selected gateway until the auth diagnostic receives the same selected port as the main health call.
[P1] The linked report was on Windows and the supplied live proof is macOS-only; source inspection suggests Commander parsing and loopback URL construction are platform-neutral, so this is a proof gap rather than a known Windows defect.

Maintainer options:

Decide the mitigation before merge
Keep this PR as the canonical implementation path, patch the health auth diagnostic to preserve the explicit selected port, then continue maintainer review/automerge on the exact head.
Pause or close
Do not merge this PR until maintainers decide whether the risk is worth taking.

Next step before merge

[P2] The PR is automerge-armed but has an explicit human-review pause plus a remaining diagnostic correctness finding, so the next step is maintainer-directed repair or approval rather than cleanup close.

Security
Cleared: The diff changes CLI option parsing, local gateway target selection, docs, and tests without dependency, workflow, secret-storage, permission, or third-party code-execution changes.

Review findings

[P2] Preserve --port in health auth diagnostics — src/cli/gateway-cli/register.ts:589

Review details

Best possible solution:

Keep this PR as the canonical implementation path, patch the health auth diagnostic to preserve the explicit selected port, then continue maintainer review/automerge on the exact head.

Do we have a high-confidence way to reproduce the issue?

Yes. Current main source registers gateway run --port but not child gateway health --port or gateway probe --port, matching the linked issue's unknown-option behavior.

Is this the best way to solve the issue?

No, not yet. Adding the option at the CLI boundary and carrying an explicit local port through health/probe resolution is the right shape, but the health auth diagnostic must use the same selected port before this is the best fix.

Full review comments:

[P2] Preserve --port in health auth diagnostics — src/cli/gateway-cli/register.ts:589
resolveGatewayRpcOptionsWithLocalPort builds the selected-port config for the main health call, but the catch path still re-reads raw config before calling emitReachableGatewayAuthDiagnostic. On credentials-required or unresolved-SecretRef errors, gateway health --port 19082 can probe/report the configured or env-selected gateway instead of the requested port; pass the same selected port/config into the diagnostic and cover that path.
Confidence: 0.88

Overall correctness: patch is incorrect
Overall confidence: 0.88

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against a1828110704f.

Label changes

Label changes:

add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦞 diamond lobster and patch quality is 🦐 gold shrimp.
remove rating: 🐚 platinum hermit: Current PR rating is rating: 🦐 gold shrimp, so this older rating label is no longer current.

Label justifications:

P2: This is a bounded gateway CLI correctness fix for local automation with limited blast radius and no data-loss, outage, or security-bypass signal.
rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🦞 diamond lobster and patch quality is 🦐 gold shrimp.
status: 🚀 automerge armed: This PR is in ClawSweeper's automerge lane. Sufficient (live_output): The PR body includes copied live CLI output from a source checkout against a real local gateway on ws://127.0.0.1:19082, directly showing after-fix health and probe behavior.
proof: sufficient: Contributor real behavior proof is sufficient. The PR body includes copied live CLI output from a source checkout against a real local gateway on ws://127.0.0.1:19082, directly showing after-fix health and probe behavior.

Evidence reviewed

PR surface:

Source +96, Tests +238, Docs +10. Total +344 across 13 files.

View PR surface stats

Area	Files	Added	Removed	Net
Source	7	121	25	+96
Tests	5	239	1	+238
Docs	1	10	0	+10
Config	0	0	0	0
Generated	0	0	0	0
Other	0	0	0	0
Total	13	370	26	+344

What I checked:

Repository policy read: Root AGENTS.md plus scoped docs and gateway AGENTS.md were read fully; the PR review depth, CLI compatibility, proof, and gateway hot-path guidance affected this review. (AGENTS.md:1, a1828110704f)
Current-main source reproduction: Current main registers gateway health without a child --port option and gateway probe without a --port option, while adjacent gateway run exposes --port, matching the linked unknown-option report. (src/cli/gateway-cli/register.ts:554, a1828110704f)
PR health port wiring: At the PR head, resolveGatewayRpcOptionsWithLocalPort parses the explicit port, rejects --url plus --port, and builds a local gateway config plus localPortOverride for the main health RPC. (src/cli/gateway-cli/register.ts:172, 6ba0afbe106c)
Remaining diagnostic mismatch: After the PR creates the port-patched rpcOpts, the health catch path still re-reads raw config for emitReachableGatewayAuthDiagnostic; that callee builds its probe from the supplied config/env, so credentials-required diagnostics can target the configured/env gateway instead of the requested port. (src/cli/gateway-cli/register.ts:589, 6ba0afbe106c)
PR probe port wiring: The PR threads the parsed port into probe target selection, network hints, and SSH remote port inference, so the probe path is covered by the intended selected-port plumbing. (src/commands/gateway-status.ts:60, 6ba0afbe106c)
Linked issue evidence: The linked issue reports OpenClaw 2026.5.6 and 2026.5.7 on Windows rejecting gateway health --port and gateway probe --port with unknown option '--port'.

Likely related people:

vincentkoc: Recent live commit history touches gateway CLI request-error handling and gateway call paths, and this member armed the PR's automerge path. (role: recent area contributor and automerge sponsor; confidence: high; commits: b41c0b674654, 9594300f8c92, 20964d3e3bbc; files: src/cli/gateway-cli/register.ts, src/gateway/call.ts)
steipete: Path history shows repeated recent work on gateway status, gateway CLI docs, and strict numeric option parsing adjacent to this change. (role: adjacent gateway CLI/status contributor; confidence: medium; commits: 09df56ee1f26, 6b391efa4e69, 69c27677f663; files: src/commands/gateway-status.ts, src/commands/gateway-status/helpers.ts, src/cli/gateway-cli/register.ts)
RomneyDa: The remaining review finding is in the health auth diagnostic path introduced by the merged gateway health diagnostic work. (role: health auth diagnostic contributor; confidence: medium; commits: d48b9274d819; files: src/commands/health.ts, src/gateway/call.ts)

What the crustacean ranks mean

🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works

ClawSweeper keeps one durable marker-backed review comment per issue or PR.
Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
Maintainers can also comment @clawsweeper review to request a fresh review only.
Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 22c8762612

ℹ️ 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".

BryanTegomoh · 2026-06-18T21:33:02Z

@clawsweeper re-review

clawsweeper · 2026-06-18T21:33:05Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

BryanTegomoh · 2026-06-18T21:56:28Z

Addressed the env precedence finding in 6ba0afb.

@clawsweeper re-review

clawsweeper · 2026-06-18T21:56:32Z

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

vincentkoc · 2026-06-22T03:33:27Z

Clownfish 🐠 reef automerge status

This pass ended as a no-op: no narrow repair surfaced, so Clownfish left the branch untouched.

Target: #94687
Executor outcome: declared allowed_fix_files excludes uncommitted paths: src/commands/health.ts.
Worker summary: Canonical path is repair of open PR #94687. The PR is editable and already owns issue #79100, but it is not merge-ready because the hydrated Codex review has an actionable blocker: health --port must override OPENCLAW_GATEWAY_PORT/OPENCLAW_GATEWAY_URL the same way probe is intended to honor the explicit local port. Merge and close are blocked by job policy, so this result emits only non-mutating classifications plus one executable repair artifact for the existing contributor branch. The executable artifact is scoped only to the canonical PR and issue; blocked-label related PRs remain historical credit evidence, not repair targets.

Worker actions:

keep_related on #79100: planned - Keep the source issue open until the canonical PR is repaired and merged by a human-approved path.
keep_closed on #89555: skipped - Historical superseded attempt; no mutation valid for already closed PR.
keep_closed on #89623: skipped - Historical superseded attempt; preserve credit as context only.
keep_independent on #91907: planned - Separate test-auth cleanup cluster, not part of this gateway CLI repair.
fix_needed on #94687: planned - Repair the existing contributor PR branch, then rerun review/changed checks; do not merge in this job.
keep_closed on #94917: skipped - Already closed superseded PR; no mutation valid.

Nothing moved downstream from this pass: no branch update, replacement PR, merge, or re-review.

fish notes: model gpt-5.5, reasoning medium.

vincentkoc · 2026-06-22T03:56:44Z

Clownfish 🐠 reef update

Thanks for the work on this. Clownfish could write to this branch, so it kept the fix in the original PR instead of making a new one.

Source PR: #94687
Validation: node scripts/run-vitest.mjs src/cli/gateway-cli/register.option-collisions.test.ts src/cli/gateway-port-option.test.ts src/commands/gateway-status.test.ts src/commands/gateway-status/helpers.test.ts src/gateway/call.test.ts; pnpm check:changed
Attribution stays exactly where it should: with the original branch and PR history.

fish notes: model gpt-5.5, reasoning medium; reviewed against b0a0c8f.

clawsweeper · 2026-06-22T04:08:48Z

🦞✅
ClawSweeper is pausing this repair loop for human review.

Source: clawsweeper[bot]
Reason: - No automated repair is currently needed; the remaining action is maintainer review plus current-head required-check handling for the existing PR branch.; Cleared: The diff changes CLI option parsing, gateway target selection, docs, and tests without dependency, workflow, lockfile, secret-storage, permission, or third-party code-execution changes. (sha=b0a0c8f89c77242f75c45500537d4b0227060147)

Why human review is needed:
This item has security-sensitive risk. ClawSweeper is pausing instead of making an autonomous change that could affect trust, credentials, permissions, or exposure.

What the maintainer can do as a next step:
If the maintainer accepts the current risk and wants ClawSweeper to continue merge gates, comment @clawsweeper approve. If the security-sensitive detail still needs changes, describe the safe path or push the fix, then comment @clawsweeper automerge. If the risk should not be automated, keep the PR paused for manual review or comment @clawsweeper stop.

I added clawsweeper:human-review and left the final call with a maintainer.

vincentkoc · 2026-06-22T06:00:19Z

Clownfish 🐠 reef update

Thanks for the contribution here. Clownfish gave the branch a tidy little reef repair and kept this PR as the main lane.

Source PR: #94687
Validation: node scripts/run-vitest.mjs src/cli/gateway-cli/register.option-collisions.test.ts src/cli/gateway-port-option.test.ts src/commands/gateway-status.test.ts src/commands/gateway-status/helpers.test.ts src/gateway/call.test.ts; pnpm check:changed
Contributor credit stays on this reef marker, with the PR history doing the receipts.

fish notes: model gpt-5.5, reasoning medium; reviewed against 2c91dba.

* fix(gateway): accept port for health and probe * fix(gateway): repair health port override * fix(gateway): repair health port override * fix(gateway): accept port for health and probe --------- Co-authored-by: openclaw-clownfish[bot] <280122609+openclaw-clownfish[bot]@users.noreply.github.com>

openclaw-barnacle Bot added docs Improvements or additions to documentation cli CLI command changes commands Command implementations size: S triage: mock-only-proof Candidate: PR proof only shows tests, mocks, snapshots, lint, typecheck, or CI. labels Jun 18, 2026

chatgpt-codex-connector Bot reviewed Jun 18, 2026

View reviewed changes

Comment thread src/cli/gateway-cli/register.ts

clawsweeper Bot added rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. status: 📣 needs proof The PR needs real behavior proof before ClawSweeper can clear the contributor ask. labels Jun 18, 2026

openclaw-barnacle Bot removed the proof: sufficient ClawSweeper judged the real behavior proof convincing. label Jun 18, 2026

clawsweeper Bot added proof: sufficient ClawSweeper judged the real behavior proof convincing. P2 Normal backlog priority with limited blast radius. merge-risk: 🚨 other 🚨 Merging this PR has meaningful risk outside the owned taxonomy. labels Jun 18, 2026

BryanTegomoh force-pushed the bryan/fix-gateway-health-probe-port branch from 22c8762 to 6ba0afb Compare June 18, 2026 21:54

openclaw-barnacle Bot added gateway Gateway runtime size: M and removed size: S labels Jun 18, 2026

clawsweeper Bot added rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. and removed rating: 🧂 unranked krab Not merge-ready due to missing proof or serious correctness/safety concerns. labels Jun 18, 2026

clawsweeper Bot mentioned this pull request Jun 20, 2026

fix(gateway): accept --port for health and probe #95181

Closed

vincentkoc mentioned this pull request Jun 22, 2026

chore: queue guarded gateway repair openclaw/clownfish#182

Merged

vincentkoc force-pushed the bryan/fix-gateway-health-probe-port branch from 6ba0afb to 9cbd92a Compare June 22, 2026 03:24

vincentkoc mentioned this pull request Jun 22, 2026

fix: allow gateway health repair path openclaw/clownfish#183

Merged

vincentkoc force-pushed the bryan/fix-gateway-health-probe-port branch from 77d81a9 to a4ea987 Compare June 22, 2026 03:41

vincentkoc force-pushed the bryan/fix-gateway-health-probe-port branch from 36a040a to b0a0c8f Compare June 22, 2026 03:56

clawsweeper Bot added rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. and removed rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. labels Jun 22, 2026

clawsweeper Bot added rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. and removed rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. labels Jun 22, 2026

vincentkoc force-pushed the bryan/fix-gateway-health-probe-port branch from b0a0c8f to f0cbaf4 Compare June 22, 2026 05:46

openclaw-barnacle Bot added size: L and removed size: M labels Jun 22, 2026

BryanTegomoh and others added 4 commits June 22, 2026 06:00

fix(gateway): accept port for health and probe

a2990aa

fix(gateway): repair health port override

1263ee3

fix(gateway): repair health port override

7342a5f

fix(gateway): accept port for health and probe

2c91dba

vincentkoc force-pushed the bryan/fix-gateway-health-probe-port branch from 55f8d6f to 2c91dba Compare June 22, 2026 06:00

vincentkoc merged commit 8e4213b into openclaw:main Jun 22, 2026
11 checks passed

vincentkoc added the clownfish Tracked by Clownfish automation label Jun 22, 2026

clawsweeper Bot mentioned this pull request Jun 22, 2026

fix(cli): add missing recovery hints to reset errors and warn on silent option fallbacks #95680

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

fix(gateway): accept port for health and probe#94687

fix(gateway): accept port for health and probe#94687
vincentkoc merged 4 commits into
openclaw:mainfrom
BryanTegomoh:bryan/fix-gateway-health-probe-port

BryanTegomoh commented Jun 18, 2026 •

edited

Loading

Uh oh!

clawsweeper Bot commented Jun 18, 2026 •

edited

Loading

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

Uh oh!

BryanTegomoh commented Jun 18, 2026

Uh oh!

clawsweeper Bot commented Jun 18, 2026 •

edited

Loading

Uh oh!

BryanTegomoh commented Jun 18, 2026

Uh oh!

clawsweeper Bot commented Jun 18, 2026 •

edited

Loading

Uh oh!

vincentkoc commented Jun 22, 2026

Uh oh!

vincentkoc commented Jun 22, 2026

Uh oh!

clawsweeper Bot commented Jun 22, 2026

Uh oh!

vincentkoc commented Jun 22, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Uh oh!

Conversation

BryanTegomoh commented Jun 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Linked context

Real behavior proof (required for external PRs)

Tests and validation

Risk checklist

Current review state

Uh oh!

clawsweeper Bot commented Jun 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

BryanTegomoh commented Jun 18, 2026

Uh oh!

clawsweeper Bot commented Jun 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

BryanTegomoh commented Jun 18, 2026

Uh oh!

clawsweeper Bot commented Jun 18, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vincentkoc commented Jun 22, 2026

Uh oh!

vincentkoc commented Jun 22, 2026

Uh oh!

clawsweeper Bot commented Jun 22, 2026

Uh oh!

vincentkoc commented Jun 22, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

BryanTegomoh commented Jun 18, 2026 •

edited

Loading

clawsweeper Bot commented Jun 18, 2026 •

edited

Loading

clawsweeper Bot commented Jun 18, 2026 •

edited

Loading

clawsweeper Bot commented Jun 18, 2026 •

edited

Loading