release aidev SIG 3/5

OpenClaw 2026.6.9: official provider plugins split to npm, Codex Spark OAuth restored

Stable release that makes official provider packages independent npm releases discovered at Gateway startup, restores GPT-5.3 Spark OAuth routing for Codex, and adds OpenTelemetry log export. Also a security round covering secret redaction in debug/config output and blocked internal HTTP session overrides.

PUBLISHED2026-06-21
OBSERVED2026-08-11
AGE1mo
SOURCES1
  • Providers: external provider packages ship as first-class npm releases; Gateway discovers installed channel plugins at startup; StepFun installable from npm or ClawHub
  • Codex: automatic plugin approvals, SecretRefs, GPT-5.3 Spark OAuth routing restored, remote-node exec exposed as a dynamic tool when a node is connected, more reliable app-server teardown
  • Search: Codex Hosted Search added; key-free search providers stay explicit opt-ins; ClawHub skill installs retain verified source provenance
  • Telegram: rich HTML send, preserved rich markdown and sticker paths, progress drafts and command output rendering, safe HTML table normalization, mention and spooled-handler routing
  • Agent runtime: retry thinking-only and empty post-tool turns, no duplicate hook execution, pending subagent delivery preserved, usage preserved through compaction, partial JSON/history artifacts repaired
  • Security: secrets redacted from debug/config output, internal HTTP session overrides blocked, open-DM tool exposure audited, plugin write ownership checks retained
  • Storage: no SQLite WAL on network filesystems, reindex artifacts cleaned, setup state kept out of workspace dot-directories, default-agent auth profiles imported into SQLite
  • Model fixes: Gemini CLI OAuth behind proxies, corrected Bedrock embedding model IDs, configured defaults preserved in embedded runs
  • Observability: OpenTelemetry log export; Control UI gains a session workspace rail and extension health; iOS Watch controls; Android chat context

COMMUNITY

No curated reactions recorded for this event. Facts and takes are kept in separate layers — community context is added by hand, never blended into the record above.