45 wires and counting

$ follow OpenClaw

Keep up with OpenClaw in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-06-09
stories 74

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Feishu rate-limit retries, Telegram /compact restored

By RepoJournal · Filed · About OpenClaw

OpenClaw's Feishu connector now retries rate-limited sends while Telegram's /compact command is fixed to actually produce a visible reply.

OpenClaw's Feishu connector now retries rate-limited sends: when Feishu returns code 230020 (per-chat rate limit), requestFeishuApi retries up to 2 times with linear backoff (500ms, 1000ms), and the reply path (im.message.reply) is covered via the same retry helper. A real 20-concurrent-send stress test confirmed all 20 messages succeed after retry. [1]

Telegram native /compact command ran compaction successfully but produced no visible bot reply; the fix bypasses the full dispatch pipeline for native commands that produce status notices (/compact, /status, etc.). This restores visible responses for those commands. [2]

Transcript redaction no longer rewrites validated opaque image payloads with a Unicode ellipsis, while remaining active for adjacent text and fake image-shaped secrets. Already-poisoned session image blocks get repaired with replayable fallback text. [3] A separate fix adds an explicit replacePaths contract for destructive config.patch array replacement and rejects unconfirmed payloads that would remove array entries, including nested arrays under id-keyed config arrays. [4]

In clownfish, the job sweep parked 1024 never-run OpenClaw jobs, moved 94 finalized jobs, and deleted 107 old smoke/test jobs. [5] Worker result review now fails on infrastructure-blocked results (Codex/auth/runtime) and explicit failed statuses. [6] The docs Translate All CI now fails incomplete translation runs instead of reporting success when locale artifacts are missing or carry failed_reason. [7]

Action items

References

  1. [1] fix(feishu): retry on send rate-limit errors (230020/230006) (#89659) ↗ openclaw/openclaw
  2. [2] fix(telegram): restore /compact on generic message ingress ↗ openclaw/openclaw
  3. [3] Fix transcript image redaction ↗ openclaw/openclaw
  4. [4] Fix config.patch explicit array replacement ↗ openclaw/openclaw
  5. [5] chore: sweep openclaw job backlog ↗ openclaw/clownfish
  6. [6] fix(worker): fail infrastructure-blocked results ↗ openclaw/clownfish
  7. [7] ci: fail incomplete docs translation runs ↗ openclaw/docs

Quick answers

What shipped in OpenClaw on June 9, 2026?
OpenClaw's Feishu connector now retries rate-limited sends while Telegram's /compact command is fixed to actually produce a visible reply. In total, 50 commits and 24 pull requests landed.
Who contributed to OpenClaw on June 9, 2026?
6 developers shipped this update, including T-800, joelnishanth, joshavant, vincentkoc, hxy91819, and openclaw-docs-sync[bot].
What were the notable OpenClaw updates?
fix(feishu): retry on send rate-limit errors (230020/230006) (#89659), fix(telegram): restore /compact on generic message ingress, and Fix transcript image redaction.