openclaw v2026.9.9

v2026.9.9

openclaw 2026.9.9

Added 2
  • Adds GPT-6.1 Sol to the Codex model list
  • Supports Claude Haiku 5.5 through Anthropic and Claude CLI
Fixed 17
  • Fixes guided channel setup where saving stayed stuck on Working while adding channels one after another
  • Fixes creating an empty workspace on Windows failing due to how OpenClaw calls Git, without requiring changes to global Git settings
  • Allows conversation naming to be retried after the first reply finishes when the model server handles one request at a time, instead of leaving a random name; user-chosen names are preserved
  • Prevents the chat from being pulled to the newest messages on resize after jumping to the latest message and scrolling back
  • Keeps messages sent from the dashboard into a channel associated with their original conversation
  • Stops new messages from linked requesters appearing twice in Claude CLI chat history and keeps internal requester instructions out of displayed text; existing records are not rewritten

From openclaw

2026.9.9
v2026.9.9

For formatted release notes, read this release on the docs site.

OpenClaw 2026.9.9 adds GPT-6.1 Sol to the Codex model list and supports Claude Haiku 5.5 through Anthropic and Claude CLI, improves recovery after failed updates, fixes missing iMessage replies, and keeps an old scheduled job from interrupting a newer conversation.

Release scale: 112 pull requests, 69 direct commits, and 91 contributors.

Installation and Onboarding
  • Channel setup. Adding channels one after another in guided setup no longer leaves saving stuck on Working while OpenClaw waits for the setup window itself. #161116 by @steipete.
Web UI
  • Windows workspaces. Creating an empty workspace on Windows no longer fails because of the way OpenClaw calls Git. You can choose New workspace and start a conversation without changing your global Git settings. First install Git for Windows using the native Windows setup guidance. Folders nested too deeply can still hit a separate Git limit. #164202 by @steipete.
  • Conversation titles. When your model server handles one request at a time, OpenClaw can try naming a new conversation again after its first reply finishes instead of leaving it with a random name. Names you choose yourself are preserved. #163817 by @MertBasar0 and @obviyus.
  • Chat reading position. After jumping to the latest message and scrolling back, resizing the chat no longer pulls you down to the newest messages. #162411, with coauthor @steipete.
  • Channel conversation history. Messages sent from the dashboard into a channel keep their original conversation association. New messages from linked requesters also stop appearing twice in Claude CLI chat history, with internal requester instructions kept out of the displayed text. Existing records are not rewritten. #151786 by @Alix-007, reported by @Rotocruz; #161012 by @Marvinthebored and @Peetiegonzalez, with reports from @Oldrich333, @holgergruenhagen and @obnoxious2011-cmd.
  • Opening and updating chats. Chats can open while their labels or activity details change, and saved background replies stay visible when an older history request finishes late. #162681, #162763, with contributions from @VACInc and follow-up investigation by @steipete.
  • Chat scrolling. Chats keep following incoming turns and large updates when you are watching the latest messages, while scrolling back preserves your reading position. Expanding details and delayed layout changes retain that choice. Refreshing history without changing its height also avoids an unwanted jump. be6713b, 0c01cc6, #166239, #166258, #166301, #166341, with contributions from @steipete and @RomneyDa.
  • Expanded chat details. Opening a message's expandable details keeps the clicked content in place instead of pulling it toward the bottom of the chat. #166200 by @RomneyDa, with included source work by @steipete.
  • Streaming replies and composer spacing. Replies keep scrolling as text arrives after a jump to the bottom that needed no movement. Empty notices also stop leaving a blank gap above the message box. #166348 by @RomneyDa, with the spacing fix by @vincentkoc.
Updates and Maintenance
  • Update completion. Updating OpenClaw no longer fails just because it is saving data at the same time. Updates from affected older versions keep the files plugins need to finish their upgrades, and global npm installs avoid a false recovery-file check failure. Once required database work has finished, a stalled shutdown can also stop holding up the update result; that safeguard applies to subsequent updates run by the fixed installation. 30c180a, ecac0d3 (original migration fix), 55360c6 by @RomneyDa; #161258 by @steipete.
  • Maintenance errors. Fixed a false maintenance warning that could interrupt an update and unnecessarily return OpenClaw to the previous version. #164554 by @RomneyDa, with source work by @steipete and reporting and investigation by @DasX.
  • Failed-update recovery. Supported updaters can recover a compatible OpenClaw installation after a failed update while preserving data written during the attempt. Returning to 2026.9.8 also keeps later updates possible. An older updater already running cannot gain these safeguards. On macOS and Linux, restart stays blocked until Doctor processes are confirmed stopped. Follow the repair steps and rollback guidance. #164497, #164724 by @RomneyDa, with original recovery work by @steipete and reports from @DasX and @jarvisnextgeneration20-lang.
  • Backups on FUSE storage. If you use storage mounted through FUSE, backups and restores no longer fail solely because a file's recorded times changed. OpenClaw checks that the contents still match before proceeding. This covers updates, Doctor repairs and rollbacks; see the container upgrade guidance. 3ecb62a (original FUSE fix) by @steipete.
  • Older memory databases. Doctor can finish upgrading an older memory cache even if some saved entries are too large or damaged. It warns you about skipped entries, which rebuild as needed while your original data stays intact. Before a database upgrade, stop processes using it and take a verified backup as explained in the migration guidance. #164303 by @steipete.
  • Package-manager updates. pnpm updates avoid the “not a terminal” failure, and optional plugin syntax errors can produce warnings instead of blocking the update snapshot. Large npm installs can continue past a scan limit with a warning that full package contents are unverified. An older updater may need a manual first update or the plugin recovery steps. df11aae by @alkor2000; #161001, #162298 by @steipete, with reporting by @jamiezigelbaum.
  • Windows update checks. Fixed an older-updater compatibility problem that could make the first Doctor check fail and roll back a Windows update. #162245 by @steipete, reported and diagnosed by @WG-Mojo.
  • Docker startup. Fixed an upgrade loop on affected older Linux hosts that repeatedly rejected an unchanged database. Retries reuse verified rollback backups instead of making another full set each time; historical backups remain available. See the Docker recovery guidance. #162305 by @steipete, with reports and investigation by @Ludwigtheo0815, @rebarshop-24 and @nweishar.
  • Doctor maintenance. Long database checks show progress and respond to Ctrl+C, waiting for work already underway to finish cleaning up before exiting. Rerun Doctor after interruption to finish the repair. Doctor can also continue when optional update-history checks are unavailable. Doctor also lets cleanup finish before closing, avoiding a Windows crash risk during shutdown. Maintenance guidance, #162213, #163608 by @steipete, with reports from @fenglanhua and @ringbe-cyber. 5d7fa8e.
  • Session archive repairs. Doctor can import sessions blocked by older migration records and retry interrupted archive repairs. Missing file copies stay flagged for recovery, with the original database content retained. Doctor also attempts to restore a managed Gateway it stopped once maintenance has finished. Rolling back OpenClaw does not undo archive changes already committed. #164867 by @steipete, reported by @hshs38033-cmd; #165854 by @RomneyDa and @Olli0103, with reports and investigation from @A1fred-AI, @mpquemel, @goncalonc and @steipete. …
View original

Upgraded? How did it go?

Discussion