@cloudflare/think@0.2.3
cloudflare/agents@cloudflare/think@0.2.3Apr 15, 2026by github-actions[bot]
AI Summary
This patch release fixes a critical bug where `getConfig()` would throw a 'no such table' error when called inside `configureSession()`, and stabilizes the `chatRecovery` feature by renaming it from `unstable_chatRecovery`.
Key Highlights
- Fixed `getConfig()` throwing 'no such table: assistant_config' error when called inside `configureSession()`
- Config storage helpers now lazily ensure the `assistant_config` table exists before querying
- Renamed `unstable_chatRecovery` to `chatRecovery` — the feature is now stable
Breaking Changes
- The `unstable_chatRecovery` API has been renamed to `chatRecovery`. Code using the old `unstable_chatRecovery` name will need to be updated.
New Features
- `chatRecovery` feature is now stable and available for production use
- Config storage helpers (`getConfig`, `configure`) can now be safely called at any point in the agent lifecycle, including during `configureSession()`
Full Release Notes
### Patch Changes
- [#1310](https://github.com/cloudflare/agents/pull/1310) [`bd0346e`](https://github.com/cloudflare/agents/commit/bd0346ec05406e258b3c8904874c7a8c0f4608e5) Thanks [@threepointone](https://github.com/threepointone)! - Fix `getConfig()` throwing "no such table: assistant_config" when called inside `configureSession()`
The config storage helpers (`getConfig`, `configure`) now lazily ensure the `assistant_config` table exists before querying it, so they are safe to call at any point in the agent lifecycle — including during `configureSession()`.
- [#1312](https://github.com/cloudflare/agents/pull/1312) [`89773d1`](https://github.com/cloudflare/agents/commit/89773d12c391a472ba3d45c88b83c98ba7455947) Thanks [@threepointone](https://github.com/threepointone)! - Rename `unstable_chatRecovery` to `chatRecovery` — the feature is now stable.