Anton Panasenko 03e6c5f600 fix(remote-control): cap reconnect backoff (#24164) ...

## Why

Remote-control websocket reconnects currently use the shared exponential
backoff helper without a local ceiling, so a long failure streak can
stretch retries out indefinitely and leave the runtime behavior hard to
inspect from logs.

## What Changed

Cap the remote-control reconnect delay at 30 seconds, then reset the
reconnect attempt counter once that capped delay is emitted so the next
failure starts from the initial jittered delay again.

The reconnect failure log now records the attempt number, chosen delay,
and whether the cap triggered a reset, with a separate info log when the
backoff counter is reset after the cap.

## Verification

`just test -p codex-app-server-transport`

Related issue: N/A

2026-05-23 00:38:22 +00:00

..

src

fix(remote-control): cap reconnect backoff (#24164)

2026-05-23 00:38:22 +00:00

BUILD.bazel

…

Cargo.toml

Restore app-server websocket listener with auth guard (#22404)

2026-05-12 18:40:53 -07:00