ewilliams28/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-08-26 20:35:39 -06:00
Code Issues Packages Projects Releases Wiki Activity

refactor: move session/transcript runtime state to SQLite

Browse Source 
Migrate OpenClaw session, transcript, and runtime state off per-file
.jsonl/JSON storage onto the SQLite state and agent databases, brought up to
date with current main. Channel plugins persist via the plugin-state SDK
keyed-store seam rather than the raw DB; storage-heavy plugins keep their own
SQLite stores via SDK path helpers.
This commit is contained in:
Josh Lehman
2026-05-31 09:23:11 -07:00
parent 4b1e5b7943
commit 43ea501f38
3309 changed files with 175707 additions and 136819 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/cli/plugins.md
+1 -1
View File
@@ -336,7 +336,7 @@ Use `--pin` on npm installs to save the resolved exact spec (`name@version`) in
### Plugin index
Plugin install metadata is machine-managed state, not user config. Installs and updates write it to `plugins/installs.json` under the active OpenClaw state directory. Its top-level `installRecords` map is the durable source of install metadata, including records for broken or missing plugin manifests. The `plugins` array is the manifest-derived cold registry cache. The file includes a do-not-edit warning and is used by `openclaw plugins update`, uninstall, diagnostics, and the cold plugin registry.
Plugin install metadata is machine-managed state, not user config. Installs and updates write it to the global SQLite database at `state/openclaw.sqlite` under the active OpenClaw state directory. The typed `installed_plugin_index` row keeps the durable `installRecords` map, including records for broken or missing plugin manifests, plus the manifest-derived cold registry cache in `plugins`. Legacy `plugins/installs.json` files are doctor migration inputs only.
When OpenClaw sees shipped legacy `plugins.installs` records in config, runtime reads treat them as compatibility input without rewriting `openclaw.json`. Explicit plugin writes and `openclaw doctor --fix` move those records into the plugin index and remove the config key when config writes are allowed; if either write fails, the config records are kept so the install metadata is not lost.