Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WARNING: This version bump introduces a breaking Firecrawl config migration that KiloClaw does not handle yet
openclaw@2026.4.2moves Firecrawl web fetch auth fromtools.web.fetch.firecrawl.*toplugins.entries.firecrawl.config.webFetch.*, but KiloClaw still validates and re-patches the old key viacustomSecretMeta/KILOCLAW_SECRET_CONFIG_PATHS(kiloclaw/packages/secret-catalog/src/catalog.ts:463,kiloclaw/controller/src/config-writer.ts:351). On restart,openclaw doctor --fixwill migrate the config file and thengenerateBaseConfig()reintroduces the stale path, so existing Firecrawl integrations can lose their API key after this image update.