Back to blog

Blume 2.0.25: Multi-window stability and faster delivery operations

Desktop window stability

Closing a desktop window that owns a delivery session no longer causes Blume to exit when another open window continues making requests. Session callbacks now check whether the original window is still active before handling requests or completing image lookups. Signing out also clears the session cache even after the owner window has been closed.

Faster plugin routing and phase changes

Plugin routing and delivery phase changes now read less data in workspaces with many deliveries.

  • Plugin routing checks whether a repository is in use with a single database lookup when there is a direct match on the primary repository, rather than loading all related delivery records.
  • Moving a delivery between phases now loads the full visit history only for the delivery being changed and reads only the sibling deployment facts needed to infer release steps.
  • Legacy file diffs remain available on demand when opening older visits.

Cleaner related delivery lookups

Related delivery lookups now exclude both manually archived deliveries and deliveries archived due to inactivity, matching the filtering rules of the main delivery list. This keeps checkpoint overlap hints and open-request discovery focused on active work.

Projects with only archived deliveries are still recognized as using Blume, and authorized coding agents can still open an archived delivery directly by ID.

Try it

In this release

  • #1630 Fix fatal session requests after desktop window destruction
  • #1643 Reduce delivery lookup reads and answer direct plugin routes in one D1 trip
  • #1645 Read only the sibling visits needed for delivery phase changes
  • #1646 Filter archived neighbors from related delivery reads