Cherry Studio v2.0.9 unifies tool approval into one declarative policy and lets the provider catalog hot-update without an app release

GitHub·medium signalXBlueskyLinkedInCopy link

Released 2026-08-24, Cherry Studio (51,087 stars) refactored its agent runtime to a single declarative tool approval policy (PR #18865) rather than per-surface approval handling, and added remote provider-catalog hot-update so new model providers ship without an application release (PR #16857). The release also tightened the skills subsystem twice, supporting valid GitHub SKILL.md links and changing skill blocking to fire only on provable dependency gaps rather than guesses, and fixed the API gateway to skip Anthropic tools that arrive with no input_schema. Notably its own repo policy now requires dual sources for network downloads, a supply-chain rule enforced in code review.