July 20, 2026SidekickSidekick Launch Arc
Sidekick Becomes The Company AI App
Sidekick became a branded, governed AI workspace with connectors, skills, approvals, budgets, outputs, memory, and Slack and Teams surfaces.
- A branded AI app for every team
- Connectors, skills, mentions, and shared threads
- Approvals, budgets, and policy controls
- Desktop, web, Slack, and Teams surfaces
- Durable outputs and personal memory
July is the Sidekick launch arc. Sidekick moved into a real employee app: branded, connected to tools, governed by approvals and budgets, and usable across the surfaces where work already happens.
What changed
- Teams got a branded employee workspace and admin console.
- Connectors, skills, mentions, and a launcher made the app more useful in daily work.
- Approvals, consent, sharing rules, and budgets became part of the flow.
- Sidekick expanded across desktop, web, Slack, and Teams.
- Generated outputs and memory started persisting across work.
Why it matters
Sidekick gives employees one governed place to do AI work, instead of scattering prompts, files, and decisions across disconnected tools.
Fixes & housekeeping
- Faster thread launch.
- Smoother streaming.
- Cleaner composer behavior.
- Better branding persistence.
- More reliable connector sign-in.
- Stronger enterprise auth.
- Safer artifact previews.
- Desktop launch and packaging fixes.
July 19, 2026Relay
Relay Becomes Manageable
Relay gained the surfaces teams need to configure routing, check setup, inspect reports, and meter usage.
- Safer onboarding and setup checks
- Routing controls and training progress
- Usage metering for billing
Relay moved from background infrastructure toward a product teams can configure and trust.
What changed
- Teams got safer onboarding and clearer setup steps.
- Routing setups became easier to edit and inspect.
- Training progress and reports became visible in the product.
- Usage metering connected Relay to billing.
Why it matters
Relay became something admins can manage directly, not just something engineers wire up.
Fixes & housekeeping
- Clearer report cards.
- Safer onboarding.
- Cleaner billing flow.
- Better model contest polish.
- Corrected model logos.
July 18, 2026Visibility
Visibility Gets Real Ownership
Visibility added manager scope, billing evidence, auditability, onboarding, and cleaner admin controls.
- Managers see the right slice of the company
- Finance gets better billing and usage evidence
- Admins get audit logs, onboarding, and cleaner settings
July made Visibility feel more ready for larger organizations. The product connected usage to ownership, access, auditability, and the commercial path.
What changed
- Managers got scoped views of their part of the company.
- Finance got cleaner evidence around usage, seats, forecasts, and exports.
- Admins got audit logs, onboarding, billing pages, flags, and a refreshed dashboard system.
Why it matters
Visibility became easier to roll out safely across more stakeholders.
Fixes & housekeeping
- Cleaner filters.
- More accurate CSVs.
- Clearer sync badges.
- Better docs access.
- Faster reads.
- Improved backfills.
June 30, 2026VisibilitySpend And Agent Visibility
Spend, Teams, And Agents Come Together
Visibility connected spend, people, teams, and agent usage into one clearer operating view.
- Cleaner spend evidence and exports
- Team and manager-scoped views
- Agent inventory and usage details
- Faster dashboard performance for larger workspaces
June was the big finance and operations release. Visibility got much better at answering who used AI, which teams owned the spend, where agents were running, and what changed over time.
What changed
- Spend views got clearer paid-seat evidence, cost views, and exports.
- Departments, groups, managers, and people became easier to reason about.
- Agent usage became easier to find, sort, and explain.
- Large workspaces loaded faster.
Why it matters
Visibility became useful for finance and operators, not just security and IT.
Fixes & housekeeping
- Faster dashboard reads.
- Cleaner department counts.
- More reliable syncs.
- Better CSVs.
- Clearer seat logic.
- Smoother navigation.
June 28, 2026Relay
Relay Starts Sharing The Model Path
Relay began giving teams one shared path for model traffic and cost attribution.
- One controlled path for model usage
- Model activity tied back to people and teams
- Cost context starts flowing into Visibility
Relay’s June work was quieter than the Visibility work, but it set up an important platform layer: model usage could start moving through one shared path.
What changed
- Model usage started moving through Relay.
- Activity could be connected back to the same people, teams, and cost picture Visibility uses.
Why it matters
Relay began turning model choice into something teams can manage, measure, and eventually optimize.
Fixes & housekeeping
- More dependable background work.
- Better install reliability.
- Cleaner configuration.
- Rollout support around the Relay path.
May 31, 2026Visibility
Managed Rollouts Get Real
Visibility added the install, health, and diagnostic pieces teams need for managed deployments.
- Managed install and uninstall scripts
- Mac and Windows smoke tests
- Health alerts based on rollout impact
May turned deployment into something admins could operate at scale. The product gained the checks, scripts, and alerts needed to understand whether a rollout was actually healthy.
What changed
- Hosted install and uninstall paths made setup easier.
- Mac and Windows checks helped catch problems before rollout.
- Device health alerts became more tied to actual impact.
- Managed browser extension deployment improved coverage.
Why it matters
Visibility moved from "installed somewhere" to "operated across a managed fleet."
Fixes & housekeeping
- Faster lookups.
- Better lifecycle cleanup.
- Cleaner integration handling.
- Stronger identity preservation.
- Fewer false matches in app detection.
April 30, 2026Platform
Easier Rollouts, Better Accountability
Oximy became easier to deploy across a fleet, with better rollout paths and clearer model usage.
- Bulk enrollment and cleaner install paths
- Extension onboarding and updates
- Early Relay usage and cost tracking
April was about getting Oximy into more real environments with less hand-holding, while making AI-generated work easier to inspect after it happened.
What changed
- Admins got stronger install, enrollment, update, and uninstall paths.
- Extension onboarding and update flows improved.
- Oximy started showing more detail around generated work, integrations, and model usage.
Why it matters
Deployment became less fragile, and model-powered work became easier to review.
Fixes & housekeeping
- Cleaner enrollment packages.
- Stronger live updates.
- Clearer model prompts.
- More reliable generated-output handling.
March 31, 2026Visibility
Activity Turns Into Action
Visibility started grouping work, surfacing next steps, and making captured activity easier to act on.
- Related AI work grouped into topics
- Follow-ups and next steps became easier to spot
- Capture and device health got more resilient
March made the activity stream more useful. Instead of only showing what happened, Visibility started helping teams understand what it meant.
What changed
- Related conversations could be grouped into readable workstreams.
- Follow-ups and next steps became easier to surface.
- Capture, authentication, and device health became more dependable.
Why it matters
Admins got closer to a workflow view, not just a log of AI usage.
Fixes & housekeeping
- Better duplicate handling.
- Safer private access.
- Stronger image links.
- Cleaner backfills.
- More reliable desktop trace handling.
February 28, 2026Visibility
More Sources, Clearer Controls
Visibility added more workplace signals, better device control, and the first policy workflows.
- Microsoft Copilot activity enters the picture
- Device controls get easier to manage
- Policy, scoring, and alerting move closer to usage
February broadened the coverage. Visibility started seeing more of the tools employees used at work and gave admins better controls for managed environments.
What changed
- Microsoft Copilot support became part of the Visibility picture.
- Admins gained clearer device commands, rollout settings, and release controls.
- Policy generation, security scoring, regulation tracking, and alerts moved closer to the activity feed.
Why it matters
Official AI tools and shadow AI started showing up in the same operating view.
Fixes & housekeeping
- More dependable device status.
- Cleaner dashboard responses.
- Sturdier retries.
- Quieter logs.
- Broader tool coverage.
January 30, 2026VisibilityVisibility Foundation
Visibility Gets Its First Map
The first Visibility release turned scattered AI activity into a readable company map.
- See which AI tools people are using
- Tie usage back to employees, devices, and teams
- Start tracking adoption, approvals, and policy risk
The first release was about replacing guesswork with evidence. Visibility began showing what AI work was happening, who it belonged to, and where admins should pay attention.
What changed
- Activity from common AI tools started rolling into one company view.
- Usage became connected to employees, devices, and workspaces.
- Early policy, approval, adoption, and oversight views came online.
Why it matters
Teams could finally start from what people were actually doing, instead of surveys, expense reports, or anecdotes.
Fixes & housekeeping
- Cleaner activity details.
- More reliable image previews.
- Safer search behavior.
- Sturdier tool recognition.