RepoJournal
OpenClaw @openclaw
99 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-07-31
stories 63
GitHub RSS Archive Topics

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

OpenClaw fixes OOM on oversized attachments, Telegram tap-to-copy login codes

By RepoJournal · Filed · About OpenClaw

vincentkoc jalehman openclaw-docs-sync[bot] openclaw-clownfish[bot]
4 people shipped this
vincentkoc @vincentkoc 4 cited jalehman @jalehman 1 cited openclaw-docs-sync[bot] @openclaw-docs-sync[bot] openclaw-clownfish[bot] @openclaw-clownfish[bot]

Four bug fixes shipped in openclaw/openclaw, including a memory safety fix for oversized local attachments and a Telegram login code convenience improvement.

The most consequential change is a memory fix: oversized local outbound attachments used to be fully buffered before the configured delivery cap was checked, which could OOM-kill the OpenClaw process on constrained systems. The source byte cap now reaches every owned local-read path before allocation, covering direct filesystem reads, sandbox bridge reads, and agent-scoped host reads, via a private capability marker for enforcing readers [1].

Telegram users starting `/login codex` got their one-time device authorization code as plain text, so mobile Telegram did not offer its tap-to-copy affordance. The OpenAI device-code flow now presents the user code through the existing structured device-code prompt when the caller supports it, preserving the plain-text note fallback for other callers [2].

Three other fixes round out the day. Anthropic parity QA scenarios in Code Mode no longer fail when hidden capabilities are invoked as direct tools, and the fanout scenario now waits for both workers to settle [3]. Uninstalling a managed plugin no longer leaves stale peer dependencies or prints an npm cleanup warning when the managed root contains pnpm parent-child selectors or npm alias overrides [4]. And the UI now shows local provider identity after setup: Ollama and llama.cpp were absent from the current-connection visual state, LM Studio used a generic mark, and local-provider logos had inconsistent coloring [5].

Topics: AI Agents AI / ML Full archive →

Quick answers

What shipped in OpenClaw on July 31, 2026?
Four bug fixes shipped in openclaw/openclaw, including a memory safety fix for oversized local attachments and a Telegram login code convenience improvement. In total, 46 commits and 17 pull requests landed.
Who contributed to OpenClaw on July 31, 2026?
4 developers shipped this update, including openclaw-docs-sync[bot], vincentkoc, jalehman, and openclaw-clownfish[bot].
What were the notable OpenClaw updates?
fix(media): prevent OOM on oversized local attachments, fix: make Telegram Codex login codes tap-to-copy, and fix(qa): keep Anthropic parity scenarios working in Code Mode.
♥

$ log @openclaw --recent

Gesture update rollback guard fixed; Slack slackens redundant work 150 shipped Clawsweeper acknowledges PRs at webhook receipt, cuts first-feedback latency 110 shipped MCP login now listens on the loopback redirect 94 shipped Clawsweeper shields against forged reviews, process crash fix 79 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.