fix: persist trusted plugin install records to SQLite for packaged WhatsApp#1140
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b6e8052774
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| `; | ||
|
|
||
| function resolveOpenClawStateDir(): string { | ||
| return process.env.OPENCLAW_STATE_DIR?.trim() || join(homedir(), '.openclaw'); |
There was a problem hiding this comment.
In normal installs this resolves the plugin index database as ~/.openclaw/openclaw.sqlite, but OpenClaw 2026.6 stores the shared state/plugin index in ~/.openclaw/state/openclaw.sqlite. As a result, every upsertPluginInstallRecordsIntoSqlite call creates or updates a sibling DB that the Gateway never reads, so packaged WhatsApp/Discord/QQBot still won't get trusted install metadata. Include the state subdirectory (or reuse OpenClaw's path helper) before appending openclaw.sqlite.
Useful? React with 👍 / 👎.
1 participant
No description provided.