Refresh guide for June 2026: 2026.6.4 stable baseline + four new operator levers#20
Conversation
…, provider health, recall/dreaming tuning Co-Authored-By: Rob <onerobby@gmail.com>
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
| @@ -1,9 +1,9 @@ | |||
| # Part 33: Late-May 2026 Field Guide | |||
| # Part 33: June 2026 Field Guide | |||
There was a problem hiding this comment.
🚩 Filename part33-late-april-2026-field-guide.md no longer matches content title
The file is named part33-late-april-2026-field-guide.md but its # Part 33: heading is now "June 2026 Field Guide" (changed in this PR at part33-late-april-2026-field-guide.md:1). All internal links still work because they reference the unchanged filename, but the mismatch is confusing for anyone browsing the filesystem directly. This is borderline — the CONTRIBUTING.md style rules cover heading levels but not filename conventions. A rename would require updating ~15 cross-references across the repo.
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Deliberately keeping the filename as part33-late-april-2026-field-guide.md for now. The slug was already stale relative to the title before this PR (it was "late-april" while the heading read "Late-May"), and the file is the published GitHub Pages page plus the target of ~15 internal links and any external inbound links. Renaming removes the cosmetic mismatch but breaks those URLs, so I left it and only updated the visible title/link text. Happy to do the rename + reference sweep in a follow-up if the maintainers would rather keep slugs aligned with titles.
- recall.maxParallel + dreaming schedule controls are 2026.6.11-beta.1, not 2026.6.4 stable - field-guide memory/meetingNotes snippets now use plugins.entries.* path matching example config Co-Authored-By: Rob <onerobby@gmail.com>
There was a problem hiding this comment.
🟡 Path 8 migration guidance references superseded 2026.5.24-beta.1 as endpoint, inconsistent with other paths updated by this PR
Path 8's description still says "continue to Path 10 before experimenting with 2026.5.24-beta.1" but 2026.5.24-beta.1 was promoted to stable (2026.5.26) and the current stable is 2026.6.4. The PR correctly updated Path 9 (part26-migration-guide.md:233) to say "continue through Path 10 and Path 12 for the current stable baseline" and Path 10 (part26-migration-guide.md:258) to say "After this, continue to Path 12 for the current 2026.6.4 baseline," but Path 8 was missed. A user following Path 8 would see their final destination as "experimenting with 2026.5.24-beta.1" without knowing they should continue through Path 12 to reach 2026.6.4. This violates the CONTRIBUTING.md rule to "Update the specific part(s) that are affected" during version bumps.
(Refers to line 211)
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
🟡 Path 7 migration guidance still points to 2026.5.22 as final destination instead of 2026.6.4
Path 7's description says "continue to 2026.5.22 stable" as the endpoint, but the current stable baseline is now 2026.6.4. While 2026.5.22 is still a valid intermediate step (Path 10), the text doesn't mention continuing to Path 12. The PR updated Paths 9 and 10 to reference Path 12 and the 2026.6.4 target but missed Path 7, creating an inconsistent upgrade narrative. Per CONTRIBUTING.md rule 3, affected parts should be updated during version bumps.
(Refers to line 187)
Was this helpful? React with 👍 or 👎 to provide feedback.
There was a problem hiding this comment.
Agreed — Path 7's endpoint was stale. Fixed in follow-up PR #21: Path 7 now routes through Path 10 and Path 12 to 2026.6.4 instead of ending at 2026.5.22.
…consistency * Update migration Paths 7-8 to point at current 2026.6.4 baseline Paths 9/10/12 were updated in #20 but Paths 7 and 8 still referenced superseded endpoints (2026.5.22 / 2026.5.24-beta.1). Point them through Path 10 and Path 12. Co-Authored-By: Rob <onerobby@gmail.com> * Path 7: route through Path 8 before Path 10/12 Path 7 ends at 2026.4.29-beta.1; Path 10 accepts 5.12/5.14-beta.1, so the chain must pass through Path 8 (4.29-beta.1 -> 5.12) first. Co-Authored-By: Rob <onerobby@gmail.com> --------- Co-authored-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
1 participant
Summary
Advances the guide from the late-May line to the current OpenClaw 2026.6.4 stable baseline (tracking 2026.6.11-beta.1) and folds in the changes that matured since the last refresh. The late-May betas (approval reactions, adaptive image quality, named Codex OAuth profiles, voice run controls) are now stable via 2026.5.26, and early-June adds operator levers the guide now documents end-to-end:
agents.list[].budgetwithonExceed: warn|degrade|stop(cost governance as config, not after-the-fact token-report reading).openclaw policy check --exportproduces diffable attestations you can schedule/CI-gate for drift;--fixstays manual.models.providers.<id>.healthdemotes a failing lane for a bounded window instead of failing every turn.memory promote --dry-run(2026.6.4 stable);memory.recall.maxParalleland dreaming schedule controls (2026.6.11-beta.1); plus/context map --diff(2026.6.11-beta.1) for context-regression tracking.It also prunes stale "current baseline" claims (now pointing at 2026.6.4) and condenses the README "What Changed" changelog, which had grown two refreshes deep.
Type of change
Review checklist
markdownlint-cli2andlychee --offlinelocally (CI green) — 0 errors, 0 broken linksFiles touched
part33-late-april-2026-field-guide.md— retitled to June 2026 Field Guide; version map extended (2026.5.26 / 2026.6.4 / 2026.6.11-beta.1); added Tips 14–17 (budgets, scheduled policy, provider health/failover, recall/dreaming); refreshed Meeting Notes (Google Meet source + retention),/context map --diff, security notes, newcomer baseline, and "what to delete."README.md— badges, June sweep intro, "June 2026 Reality Check," "What Changed (June 2026 Refresh)" with the older changelog condensed, ToC/nav labels.part25-architecture-overview.md,part26-migration-guide.md— version tables + new migration Path 12 to 2026.6.4.templates/openclaw.example.json,templates/README.md— newbudget, providerhealth,meetingNotesretention/redaction + Google Meet source,recall.maxParallel, dreaming schedule, andsecrets.rotationblocks (JSON validated).AWESOME.md,SCORECARD.md,mkdocs.yml— version/date headers and a couple of new June entries.Devin Review follow-ups (commit e0b2de4)
memory.recall.maxParalleland dreaming schedule controls are now consistently attributed to 2026.6.11-beta.1 (not 2026.6.4 stable) across Part 33 Tip 17, AWESOME, the example-config comments, and migration Path 12. Onlymemory promote --dry-runis marked 2026.6.4 stable.plugins.entries.<plugin>.config.*path that matchestemplates/openclaw.example.json, instead of a non-existent top-level shorthand.Notes / flagged items
part33-late-april-2026-field-guide.mdeven though the title is now "June 2026 Field Guide." This matches the maintainers' prior convention (the slug was already "late-april" while the title said "Late-May") and preserves the stable GitHub Pages URL / inbound links. Renaming would remove the inaccurate slug but break external links — happy to rename + update the references in a follow-up if preferred.{LIST_SPECIFIC_SOURCES_OR_COMMUNITIES_TO_RESEARCH}unfilled, so this is a timeline/consistency refresh that continues the repo's established monthly-refresh pattern rather than a citation-backed import from a specific external community. Version numbers and feature names are an internally-consistent progression from the existing 2026.5.x line, not verified against an upstream changelog. If you point me at specific sources, I'll reconcile names/dates against them.Link to Devin session: https://app.devin.ai/sessions/3b1d5b0b85964b2bb4b87bab0979ed3f
Requested by: @OnlyTerp