Release Notes

On-demand overage billing, and clearer employee matching

Teams that lean on Bloomy hardest tend to be the ones that hit their included AI credits first. On-demand overage lets those teams keep going and pay for the extra usage on their monthly invoice. This release also adds detail to the Integrations employee picker, so admins can confirm they are matching the right person.

What's new

On-demand overage billing

For teams whose work runs past the AI credits included in their plan, on-demand overage keeps Bloomy available instead of stopping at the limit. Usage above the included allowance is billed monthly, so a heavy month costs more and a quiet month does not.

• Overage is opt-in per company. Nothing is charged unless an admin turns it on.
• Charges arrive on one invoice per billing period, in your own billing currency.
• Every period with overage usage produces an invoice, so charges stay in the period they belong to.

More detail in the Integrations employee picker

Matching an employee to their device or account is easier from the Integrations employee picker.

• The employee picker now shows a details tooltip for each person.
• A device count chip shows how many devices are assigned to each employee, directly in the picker.

Who benefits

• Teams that use Bloomy heavily: keep working past the included allowance and pay for the extra usage, instead of waiting for the next billing period.
• Admins who own billing: overage arrives as one invoice per period, in your own currency, with no gaps between periods.
• Admins connecting integrations: a details tooltip and device count chip make it faster to confirm the right employee match.

Try it

• Turn on on-demand overage in Settings, billing and plans.
• Review overage charges on your monthly invoice, in your own billing currency.
• Open Integrations and hover an employee in the picker to see the details tooltip and device count.

Active time, one number across the Activity Log

This release rebuilds the Activity Log around a single active-time number, with new view modes and page-address accuracy fixes throughout. Microsoft 365 and Google Workspace data gaps now close themselves, and 8x8 Work & Contact Center joins the integrations catalog. Productivity Models see further into connected data sources and now fail with a real reason instead of finishing quietly with no data.

What's new

Active time, one number across the Activity Log and Bloomy

The Activity Log moves to a single active-time number, shown consistently across every view and in Bloomy chat answers.

• New view modes: Compact (default), Events, By App, By App + Title, By Domain, and By URL, each showing one active-time duration per entry instead of separate app and website rows.
• A Columns menu lets you choose what's visible per view, and exports now match exactly what's on screen.
• Active time now counts only the seconds following detected keyboard or mouse input, and excludes locked or sleeping time.
• Bloomy's answers about activity and browsing history now draw on the same events and active-time numbers shown in the table, so chat answers and the dashboard always agree.

Full filter lists and accurate page addresses

Activity Log filters and page-address data are more complete and more trustworthy.

• Filter dropdowns for username, device, and app now show every match across the full date range on large fleets, instead of silently truncating.
• Title-change breakdowns show the page address per segment, with resizable columns and a faster, more forgiving title search.
• Page addresses shown in a session now always match the title being viewed, fixing cases where an unrelated page's address appeared next to it.
• Windows keystroke activity counts, previously showing as zero for a stretch of time due to a data issue, are now accurate, with historical data corrected.
• CSV exports no longer include raw keyboard and mouse-click counts, keeping downloads focused on aggregate activity time.

Productivity Models see further, and fail loudly instead of silently

Productivity Models show more about your connected data before you run, and are honest when a run can't produce a result.

• The run dialog shows how far back each connected source has history, and the date range picker starts where your data begins; sources that aren't connected are clearly marked with a link to reconnect.
• Microsoft 365 connections now pull 21 days of history on first connect, up from 7.
• Sync history now shows "Abloomify" when a team member ran a sync on your behalf.
• Creating a new model no longer loses the name you typed while adding sources, and a description is now optional.
• Custom CSV-based data sources now produce real values instead of silently returning blank results, and failed runs show a specific reason.

Fewer data gaps, a new integration

Connected data sources recover automatically more often, and the integrations catalog grows.

• 8x8 Work & Contact Center joins the integrations catalog, with its own setup guide for connecting your account.
• Microsoft 365 and Google Workspace productivity data now recovers automatically when a provider's report is delayed, closing gaps that used to need manual fixes.
• A dating issue that mislabeled recent Microsoft 365 activity by up to three days has been corrected.
• Sync History now shows the exact dates each sync covered, instead of an approximate single date.

Who benefits

• IT admins managing device fleets: filter dropdowns show every match on large fleets, and keystroke and page-address data is corrected retroactively.
• Leaders reviewing the Activity Log: one active-time number across every view mode, matching what Bloomy reports in chat.
• Teams building Productivity Models: clear visibility into source data availability, and failed runs that explain why instead of returning blank results.
• Admins connecting Microsoft 365 or Google Workspace: fewer manual fixes when a provider's report is delayed, plus accurate sync history dates.

Try it

• Open the Activity Log and switch between Compact, Events, By App, By App + Title, By Domain, and By URL view modes.
• Review the Columns menu in the Activity Log to choose what's visible, then export to match your view.
• Check the run dialog in Productivity Models for data availability before choosing a date range.
• Connect 8x8 Work & Contact Center from Integrations.

Steadier Activity Log, sharper DORA, integrations that keep their history

This release focuses on reliability across the board. The Activity Log filters and loads more predictably, DORA production metrics are more accurate and easier to configure, and reconnecting an integration no longer means losing months of collected history. Bloomy task reports also get shorter and cleaner.

What's new

A more reliable Activity Log

The Activity Log is more predictable when filtering, loading, and exporting.

• Devices with hyphens in their names, a common pattern on Windows machines, now show up correctly instead of being excluded from filtered views.
• The table stops flashing stale rows or getting stuck loading when filters change while a device sync is still running.
• Browser URLs (page address only, no query string) now appear in the Activity Log table and CSV export for companies that have turned on browser URL collection.
• CSV export no longer fails when "Show App Title Changes" is turned on.

Sharper DORA accuracy

DORA production deployment and failure metrics are more accurate, and easier to configure with confidence.

• Run-name filters that used to silently match zero deployments now work, with a live "Matches X of Y runs" preview before you save.
• A picker shows the run names GitHub Actions actually reports, so you don't have to type them from memory.
• The default branch shown in DORA settings now reflects GitHub's real default branch, not a guess.
• Production deployment detection now correctly follows each repo's configured production workflows, so unrelated jobs are no longer counted, and Bloomy's DORA answers in chat now match the dashboard.

Integrations keep their history

Reconnecting or disconnecting an integration is now safer, and problems are easier to spot.

• Reconnecting an integration, such as Microsoft 365, GitHub, or Jira, no longer loses collected metrics; history carries over automatically to the new connection.
• Disconnecting now defaults to keeping collected metrics, with an opt-in option to permanently delete them, and errors now surface as clear messages instead of failing silently.
• Integrations with connection problems are flagged with a clear status on the Integrations page and a one-click reconnect action.
• Settings changes made moments apart, such as two Microsoft 365 toggles, no longer silently overwrite each other.
• Dashboards and Bloomy custom views avoid double-counting metrics after a data update, so numbers stay consistent.

Smarter setup, more integrations

Getting connected and matched is easier, and the integrations catalog grows.

• Azure DevOps and Microsoft Planner are now available to connect from the integrations catalog.
• Microsoft 365 gains a manual "Sync now" option, a clearer status banner when it's the active source for employee data, and a clear error message if sync now is used on a connection that isn't the source.
• Device agent matching to employees is more accurate, and a stale device assignment to a departed employee is flagged when an active match exists.
• The AI-Assisted Engineering card has been rebuilt with daily, weekly, monthly, and quarterly views, usage bands, and a full engineer leaderboard.

Cleaner Bloomy task reports

Scheduled Bloomy tasks are easier to read and easier to schedule.

• Bloomy task reports are shorter, with the delivered email itself viewable directly in the conversation instead of duplicated as text.
• Scheduled biweekly Bloomy tasks can now be pinned to a specific start date.
• Task notification emails no longer show raw formatting characters instead of properly formatted text.

Who benefits

• IT admins connecting or reconnecting integrations: metric history carries over automatically, and broken connections are easy to spot and fix.
• Engineering leaders tracking DORA metrics: more accurate production deploy and failure counts, with a live preview when configuring filters.
• Teams reviewing the Activity Log: more devices show up correctly, plus browser URL context where enabled.
• Anyone scheduling or receiving Bloomy reports: shorter summaries and cleanly formatted emails.

Try it

• Reconnect or review an integration from Integrations to see the new status indicators and reconnect action.
• Revisit your DORA run-name filters in repo settings to use the new live match preview.
• Check the Activity Log for the browser URL column if your company has browser URL collection turned on.
• Review the AI-Assisted Engineering card for the new usage bands and engineer leaderboard.

Every-two-week scheduling and a fresher Activity Log

This release adds an every-2-weeks option to Bloomy scheduled tasks, makes the Activity Log easier to keep current during an active device run, and polishes the login page. Bloomy automations can now follow an every-other-week cadence from a start week you choose, and the Activity Log gains a manual refresh, live updates while a run is in progress, and fresh data sooner.

What's new

Every 2 weeks for Bloomy tasks

Bloomy scheduled tasks can now run every 2 weeks, not just weekly, with control over which week the cadence begins.

• A new Every 2 weeks option sits alongside Weekly when you schedule a Bloomy task.
• A Starting date sets which week a biweekly task begins, so it lands on the right week from the first run.
• Task lists label these as "Every 2 weeks" so the cadence is clear at a glance.
• Ask Bloomy in chat to set up an every-other-week automation, and it schedules the matching cadence.

A fresher, steadier Activity Log

The Activity Log is easier to keep current during an active device run, and its loading behavior is more reliable.

• A refresh button in the Activity Log header pulls the latest results on demand.
• During an active device run, the Activity Log updates on its own so new events appear as they happen.
• Fresh activity now appears sooner, while a run is still in progress.
• Reset filters now clears Activity Log filters too, matching the other tabs.
• Fixed cases where changing filters during a refresh briefly showed outdated rows, or reverting them could leave the table loading.

Clearer login region switcher

The login page region switcher is clearer and easier to use.

• The region switcher shows proper US and EU flag images.
• Improved layout and larger tap targets make the switcher easier to use.
• A single, consistent loading indicator shows while you sign in.

Who benefits

• Teams automating with Bloomy: scheduled tasks that can run every 2 weeks from a start week you choose.
• Anyone scheduling in Bloomy chat: ask for an every-other-week automation and get the right cadence.
• People watching the Activity Log: on-demand refresh, live updates during a run, and fresh data sooner.
• Everyone signing in: a clearer login region switcher with proper US and EU flags.

Try it

• Open a Bloomy task and choose Every 2 weeks, then set a Starting week.
• Ask Bloomy to schedule an every-other-week report or automation.
• Use the refresh button in the Activity Log header, and watch it update during an active device run.
• Use Reset filters on the Activity Log tab to clear its filters.

Bloomy gets a memory, and delivers your reports

This release centers on Bloomy. It can now remember small, durable facts across conversations, list and deliver your saved Engineering Custom View reports with the same numbers you see on the dashboard, and run on the newest GPT-5.6 models. Scheduled Bloomy tasks also run more steadily, with fewer duplicate sends and clearer status when a run is skipped.

What's new

Bloomy remembers what matters

Bloomy can now hold onto small, durable facts you share, so you repeat yourself less from one conversation to the next.

• Bloomy remembers preferences and facts you tell it, and carries them across separate conversations.
• Review, and delete, everything Bloomy has remembered from My Bloomy.
• Scheduled tasks can carry their own remembered context, visible in the Task details dialog.

Bloomy delivers your engineering reports

Bloomy can now read your saved Engineering Custom View and executive reports and return the same numbers you see on the Custom Views tab.

• Ask Bloomy to list the saved Custom View and executive reports available to you.
• Ask Bloomy to summarize or deliver a named report for any date range, with numbers that match the Custom Views tab.
• Reports now include richer per-person breakdowns and clearer employee display names, with email shown only when you choose.
• Export a Custom View to an Excel workbook that includes every card, with consistent number formatting.
• Access follows the same permission as the Custom Views page.

Newer AI models in Bloomy

The Bloomy model picker adds the newest GPT-5.6 models and makes it easier to weigh intelligence against cost.

• GPT-5.6 Sol, Terra, and Luna are now available in the Bloomy model picker.
• Superseded models are retired from the picker and marked "(retired)" in existing chats.
• Model choices are grouped by provider, with clearer intelligence and cost indicators and fuller tooltips.
• Cost breakdowns for chats on retired models keep showing their historical spend.

Steadier scheduled tasks

Scheduled Bloomy tasks run more predictably, with fewer duplicate sends and clearer status.

• A scheduled task now knows what it already delivered, so repeat reports do not send the same thing twice.
• Tasks respect the data sources you currently have access to each time they run.
• When a scheduled task is skipped, you now see a notification instead of silence.
• Report attachments now arrive attached to the task email.

Who benefits

• Everyone using Bloomy: a Bloomy that remembers your preferences and facts across conversations.
• Engineering leaders: saved Custom View and executive reports delivered by Bloomy, with dashboard-accurate numbers and per-person detail.
• Admins choosing models: GPT-5.6 in the model picker and clearer intelligence and cost indicators.
• Teams running scheduled reports: fewer duplicate sends, visible skips, and attachments that arrive attached.

Try it

• Open My Bloomy to review and manage what Bloomy has remembered.
• Ask Bloomy to list your Engineering Custom View reports, then deliver one for a date range.
• Choose a GPT-5.6 model from the Bloomy model picker.
• Review a scheduled task's remembered context in the Task details dialog.

Sharper Usage Insights, from Activity Log to sprint delivery

This release centers on Usage Insights. The Activity Log gained richer filters, a fuller day timeline, and more accurate matching between devices and the people who use them. Engineering Insights adds sprint delivery metrics, admins can pull the current day's data on demand, and EU customers get clearer data residency defaults.

What's new

A richer Activity Log

The Activity Log in Usage Insights is easier to filter, read, and trust.

• Filter by device, application, and more with a collapsible filter row whose options build up as you page through results.
• A redesigned timeline shows a full view at once, with a summary row, an interactive legend, and times displayed in your own timezone.
• Turn on in-app title changes to expand any focus session into a per-title breakdown instead of separate zero-length rows, and export that same breakdown to CSV.
• Devices now map to the right person more reliably, which previously kept some devices out of team and person views.
• Selecting "Unassigned devices" now adds those devices on top of your current filters instead of clearing them, and operating-system and username filters behave correctly.

Sprint delivery in Engineering Insights

Engineering leaders can now measure how Jira sprints are landing, directly in Custom Views and executive reports.

• New sprint metrics cover completion rate, sprints completed, sprints in progress, sprint velocity, and ticket volume.
• A redesigned Sprints and Delivery tab on the Task Velocity card adds a toggle to include in-progress sprints, with plain-language tooltips.
• A sprint details view lists committed, completed, and carried-over issues, with board and date context.
• Metrics respect the selected time range, and completion rate counts only sprints finished within it, so story points match that same set of sprints.

On-demand real-time usage data

Admins can now have real-time access to usage data for their company when they need it, and scheduled Bloomy tasks report their status accurately.

• A Request Today's Usage Data action in Usage Insights runs the current day's data, shows progress, and delivers results to the History tab.
• On-demand runs now return in minutes rather than the longer wait they took before.

Bloomy reads your Activity Log

Bloomy can now answer questions grounded in your Activity Log, and longer conversations run to completion.

• Ask Bloomy to summarize activity logs, coverage, sessions, and more.
• Ask Bloomy to surface workflow patterns, context switching, and automation candidates from activity sessions for companies that have the optional opt-in window-title telemetry enabled.
• Access stays limited to companies and users with the Activity Logs module and the matching page permission.
• Longer, multi-step Bloomy conversations now run to completion instead of stopping early.
• Diagrams render more reliably, common formatting mistakes are repaired automatically, and view links open in a new tab.

Privacy controls and EU data residency

This release expands how teams control what is collected and where EU data is processed.

• Agent collection now has three clear states, collecting everything, collecting only what you allow, or collecting nothing, with explicit actions to turn collection on or off.
• Companies on the EU deployment start in a passive state, collecting nothing until an admin sets a policy.
• On the EU deployment, Bloomy defaults to EU-hosted models for data residency, with other providers available only when an admin opts in.
• Windows offers two installer choices, one with the browser extension and one without, and the setup page hides browser-extension controls for teams that do not use it.
• Windows device-agent updates no longer leave a duplicate entry in installed programs.

Who benefits

• Admins and leaders: a richer Activity Log with filters, a fuller timeline, and more accurate device-to-person matching.
• Engineering leaders: Jira sprint delivery metrics in Custom Views and executive reports.
• Admins: on-demand usage data, clearer collection controls, and two Windows installer choices.
• EU-based customers: passive collection by default and EU-hosted model processing for data residency.
• Everyone using Bloomy: activity-log answers and longer conversations that finish.

Try it

• Open Usage Insights, Activity Log and use the filters and redesigned timeline.
• Use Request Today's Usage Data in Usage Insights for a same-day pull.
• Review sprint delivery on the Task Velocity card in Engineering Insights.
• Ask Bloomy about your activity logs, and review collection controls in Integrations, Device Agents.