LobeHub v2.1.52-canary.5 is a small canary release focused on polishing the agent tooling experience. This automated build adds back missing tools in manual agent runtime mode, improves how successful tool calls are displayed when no return value is produced, and makes a minor UI wording cleanup in the API key section. As a canary release, it is intended for testing rather than production deployment.
The most important fix in this build restores lost tools in manual agent runtime mode. For users testing custom agent flows, this should reduce confusion and bring expected tool availability back into the interface.
Another meaningful update improves status visibility for tool calls that complete successfully but do not return a value. Instead of appearing ambiguous, those calls now show a clear success state, which should make agent execution results easier to understand.
The final change is a minor interface refinement: the word “Management” has been removed from the API Key tab title. While small, it contributes to a cleaner and more concise settings UI.
This release is mainly about reliability and clarity in LobeHub’s agent workflow experience. The restored tools in manual runtime mode address a functional regression, while the improved success display helps users better interpret tool execution outcomes during testing.
Although the visual label change is minor, the combined update shows continued iteration on both usability and agent-facing behavior. Teams experimenting with LobeHub’s canary branch may find this build useful for validating tool-driven workflows before changes are promoted further.
Because this is an automated canary build, it may still contain unstable or incomplete work. It should be evaluated in non-production environments, with backups in place before installation.
Official Source: https://github.com/lobehub/lobehub/releases/tag/v2.1.52-canary.5