OpenClaw v2026.5.28: iOS Overhaul, ClawPDF, and Agent Runtime Fixes

OpenClaw v2026.5.28 shipped on May 29, 2026, as a pre-release. The update includes a rebuilt iOS app, native PDF extraction, and runtime stability improvements for multi-agent deployments. Here's what changed, why it matters, and whether you should upgrade.

What Is It?

OpenClaw is an open-source AI agent framework that runs coding agents, automation workflows, and Telegram integrations on local hardware. Version 2026.5.28 is a pre-release (beta.1) that adds iOS Pro UI support, ClawPDF for document extraction, and runtime fixes for subagent and Codex reliability.

This release continues the May 2026 hardening cycle that began with v2026.5.22's Gateway performance overhaul.

Why Should Developers Care?

iOS Pro UI

The iOS dev app now includes four dedicated tabs — Pro Command, Chat, Agents, and Settings — wired directly to gateway sessions, diagnostics, real-time chat, and Talk. Each tab surfaces live gateway state rather than static configuration screens.

For business owners who approve agent actions from their phone, this is the difference between a working mobile experience and one that drops state on every reconnect.

ClawPDF

OpenClaw now uses ClawPDF for PDF extraction, including encrypted PDF support. Structured MCP content surfaces in agent tool results when processing PDFs, giving agents richer data rather than raw text dumps.

This replaces the previous ad-hoc extraction approach and removes external dependencies for document analysis workflows.

Agent Runtime Fixes

Several reliability improvements address production deployment issues:

Subagent workspace isolation: Spawned agents no longer bleed cwd or workspace state into each other.
Hook context isolation: Hook context is now prompt-local, preventing contamination across turns.
Session lock cleanup: Session locks release properly on timeout abort, eliminating stuck sessions.
Restart state management: Stale restart continuations are avoided, fixing incorrect state resumption after restarts.
Codex shared runtime: Codex app-server/helper failures no longer tear down shared runtime state.

If you've run multi-agent setups where a subagent crash cascades or sessions get stuck after timeouts, these fixes are relevant.

Security Hardening

Multiple security-focused changes:

Group prompt metadata: Untrusted group prompt text is routed outside the system prompt, mitigating prompt injection in group chats (Discord, Slack, Teams).
Hostname validation: Repeated trailing dots in hostnames are normalized, preventing validation bypass.
Tailscale auth: Configurations that expose the gateway without authentication are rejected.
Admin authority: Node/device-role approvals now require admin authority, not just owner status.
Microsoft Teams: Untrusted service URLs no longer get elevated treatment.

Provider Expansion

Pixverse video generation: First-class provider support with API region selection.
DeepInfra: Full credential-aware model catalog during onboarding.
OpenAI-compatible embeddings: Core support for any OpenAI-compatible embedding endpoint (local or hosted).

What Are the Limitations?

Pre-release status: v2026.5.28 is beta.1, not yet promoted to stable. The diffs-language-pack plugin blocked the ClawHub publish run — expected to clear before stable promotion.
iOS rebuild scope: The iOS update is a dev app refresh, not a full production release.
ClawPDF coverage: Encrypted PDF extraction is supported, but complex layouts or scanned documents may still require OCR preprocessing.
Mobile state preservation: While reconnects are improved, long-running sessions on mobile may still experience interruptions due to OS background limits.

When Should You Use It?

Upgrade to v2026.5.28 if:

You run multi-agent deployments and experience subagent crashes or session locks.
You use OpenClaw in group channels (Discord, Slack, Teams) and want prompt-injection mitigation.
You process PDFs in agent workflows and want structured extraction.
You use the iOS app for mobile agent management.

Wait for stable if:

You require production-grade stability (pre-release status).
You rely on plugins that may have compatibility issues with beta releases.

When Should You Not Use It?

Production critical systems: Pre-release status means potential regressions.
Legacy plugin dependencies: The diffs-language-pack issue shows some plugins may need updates.
Teams unfamiliar with beta testing: If your team doesn't have rollback procedures, wait for stable.

Sources

Content type: News | Published: May 31, 2026