RepoJournal
OpenClaw @openclaw
62 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-22
stories 54
GitHub RSS Archive Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

Telegram lane recovery fixes stuck inbound events

By RepoJournal · Filed · About OpenClaw

openclaw-docs-sync[bot] Vincent Koc yetval mikasa0818 LiuwqGit
5 people shipped this
openclaw-docs-sync[bot] @openclaw-docs-sync[bot] 5 cited Vincent Koc @vincentkoc 2 cited yetval @yetval 2 cited mikasa0818 @mikasa0818 1 cited LiuwqGit @LiuwqGit 1 cited

OpenClaw shipped fixes that unblock Telegram inbound events stuck behind live-held claims and image-heavy sessions that silently failed to compact.

OpenClaw fixed a class of Telegram isolated-ingress failures where a claim held by a live worker could stall the whole lane. PR #95299 [1] now recovers claims that exceeded the spooled handler timeout and aren't owned by active handler state, failing them with `lane-released-on-stuck` through the existing token-guarded durable spool path. The same effort [2] wakes the Telegram isolated polling drain immediately after a worker-spooled update lands in `channel_ingress_events`, and fixes the race where pending drains were lost while a drain was already active. Stuck updates now dead-letter and later updates in the same topic drain without a gateway restart.

Compaction also got a real fix. The cut-point estimator charged images 4800 chars in the tool-result branch but zero in the user branch, so image-heavy recent turns never reached the keep-recent budget and compacted to a no-op, looping on context overflow [3]. The shared per-image accounting now applies to both branches [4]. Separate housekeeping landed in the GoogleChat test suite [5] and in fs-safe's write and identity paths [6].

Docs mirrored five times from openclaw/openclaw [7] [8] [9] [10] [11], tracking the underlying code changes.

Action items

References

  1. [1] fix #95248: OpenClaw release_lane is a no-op when claim is held by a live worker; stuck Telegram inbound events block agent response until gateway restart ↗ openclaw/openclaw
  2. [2] fix #86957: drain worker-spooled Telegram updates immediately ↗ openclaw/openclaw
  3. [3] fix(compaction): count user-message image blocks in cut-point estimator ↗ openclaw/openclaw
  4. [4] fix(compaction): count user-message image blocks in cut-point estimator (#95128) ↗ openclaw/openclaw
  5. [5] fix(googlechat): remove useless test string concatenation ↗ openclaw/openclaw
  6. [6] fix: harden fs-safe write and identity paths ↗ openclaw/fs-safe
  7. [7] chore(sync): mirror docs from openclaw/openclaw@674b4f337241a7e773c908995a86c9e9b8713045 ↗ openclaw/docs
  8. [8] chore(sync): mirror docs from openclaw/openclaw@0374892fd86d942fc50b23ef1b0136f967d28d96 ↗ openclaw/docs
  9. [9] chore(sync): mirror docs from openclaw/openclaw@9e8ab083dd6b9df4dadf40ee523ff18ac1472bd3 ↗ openclaw/docs
  10. [10] chore(sync): mirror docs from openclaw/openclaw@a0714a3d685516b8e2a88d0667f6fb0324d497bd ↗ openclaw/docs
  11. [11] chore(sync): mirror docs from openclaw/openclaw@ec7a548062d3ad489079d6737da973a9171bad28 ↗ openclaw/docs
Topics: AI Agents AI / ML Full archive →

Quick answers

What shipped in OpenClaw on June 22, 2026?
OpenClaw shipped fixes that unblock Telegram inbound events stuck behind live-held claims and image-heavy sessions that silently failed to compact. In total, 42 commits and 12 pull requests landed.
Who contributed to OpenClaw on June 22, 2026?
5 developers shipped this update, including openclaw-docs-sync[bot], mikasa0818, Vincent Koc, yetval, and LiuwqGit.
What were the notable OpenClaw updates?
fix #95248: OpenClaw release_lane is a no-op when claim is held by a live worker; stuck Telegram inbound events block agent response until gateway restart, fix #86957: drain worker-spooled Telegram updates immediately, and fix(compaction): count user-message image blocks in cut-point estimator.
♥

$ log @openclaw --recent

Gesture update rollback guard fixed; Slack slackens redundant work 150 shipped Telegram webhook durability and reply-target RPC calls land 98 shipped ClawSweeper passes security fix for agent skill MCP boundary drift 56 shipped OpenClaw ships seven security fixes across HTTP, Browser, and Exec surfaces 63 shipped

$ log --all # elsewhere on the wire

Meta React Native adds Stable API guards to renderer attributed string FastAPI & Pydantic Pydantic fixes Mypy plugin crash, tightens datetime constraints

$ ls showcases/

Rails Django Laravel Node.js Go Vercel Vue.js Kubernetes HashiCorp Arch Linux Linux Anthropic

$ init your-desk

RepoJournal can write one of these for any repo you care about. Sign in with GitHub, pick your repos and sources, and your desk gets a wire like this one every morning.