Agents are eating the video stack

Zoom made the loudest move. On 21 Oct it announced a tool for detecting deepfake risks during video calls, then on 23 Oct used Zoomtopia 2026 to introduce AI agents and new security controls. On 24 Oct it announced the acquisition of Onyx, and by 30 Oct and 31 Oct the completed deal was described as adding open-source enterprise knowledge search to Zoom AI Services. On 27 Oct Zoom also added deepfake detection capabilities and unveiled a Unified Context Layer.

Riverside made the same strategic turn in product language. On 27 Oct its website navigation added Agents and AI Translation, while removing All AI Tools and AI Co-Creator. On 29 Oct app version 4.24.0 introduced Riverside Agents: Producer, Editor, Clipper and Marketer, with the Editor handling cuts, clean-up and captions, and the Clipper identifying moments for clips.

Loom’s shift was quieter but pointed in the same direction. On 24 Oct it replaced the homepage line “Meet the all-new Loom for Mac” with “Show it in Loom, ship with any agent”, and changed a call to action from “See all use cases” to “Explore now”. The category’s language is narrowing. Recorded and live communication is being repackaged as an input layer for agents.

Zoom’s fortnight was unusually developer-heavy. On 22 Oct it released meetingsdk-web v6.5.0, created meetingsdk-web and meetingsdk-web-sample, and its top repository stars moved from 95 to 1,069. On 23 Oct it added seven repositories tied to the Video SDK, including samples for React, Vue.js, JavaScript, Angular, a Moodle TinyMCE plugin and RTMS audio transcription. On 28 Oct it created rtms-samples and ai-services-quickstart, then on 30 Oct added rtms-compliance-sample-js.

The usage signals followed the repository work. On 27 Oct @zoom/appssdk downloads rose from 41,048 to 54,034, while @zoom/videosdk rose from 42,037 to 59,439. On 28 Oct @zoom/meetingsdk climbed from 63,376 to 110,880. On 29 Oct @zoom/videosdk rose again, from 56,800 to 78,728.

Vimeo also had a strong developer week, but in a different mode. On 24 Oct @vimeo/vimeo downloads rose from 28,179 to 36,900. On 29 Oct @vimeo/player increased from 1,167,623 to 1,531,841, while @vimeo/vimeo rose from 41,103 to 53,583. Its Psalm repository shipped a sequence of 7.0.0 release candidates on 24 Oct, 28 Oct, 30 Oct, 31 Oct and 1 Nov, addressing conditional taint sinks, ArrayAccess offset handling, taint-analysis memory use, composer autoload crashes and sealed keyed array narrowing.

Descript’s developer signals were more mixed. On 26 Oct it created a resvg repository. On 29 Oct it released v0.2.2 with a Go provider enhancement and created video-outpainting. Package demand was volatile: on 27 Oct @descript/web-audio-js, @descript/immer and @descript/kali all rose sharply, but on 28 Oct @descript/immer fell from 14,044 to 4,949.

Vimeo’s fortnight carried both brand investment and post-deal pressure. On 20 Oct, IMDb reported that the short film grant programme prize had increased from $150,000 to $300,000, while Mashable reported layoffs after an acquisition. On 22 Oct, IMDb again reported the grant increase, and The National Law Review reported that 12,000 customers had migrated from Vimeo to Gumlet following the acquisition by Bending Spoons.

Operationally, Vimeo also had a difficult run around uploads. On 26 Oct a minor incident meant newly uploaded videos might not play in embeds because of incorrect privacy settings, lasting about 72 minutes. On 29 Oct a critical incident caused delays in processing new video uploads for about 108 minutes. On 30 Oct a major incident again caused delays in processing new uploads for about 97 minutes.

There was also an ecosystem security note. On 28 Oct two CVEs were published for Stored Cross-Site Scripting in the All-in-One Video Gallery plugin for WordPress, which supports YouTube, Vimeo and self-hosted videos. Both were scored 6.4. That is not the same as a Vimeo platform vulnerability, but it matters because video distribution often depends on third-party embed infrastructure.

The marketing layer was active but disciplined. Between 22 Oct and 2 Nov, Zoom’s Google Ads observations repeatedly showed 40 creatives running while new creatives entered the set, including 8 new creatives on 22 Oct, 5 on 23 Oct, 9 on 26 Oct, 5 on 27 Oct, 3 on 28 Oct, 6 on 29 Oct and 4 on 2 Nov. Vimeo and Descript showed the same 40-running pattern on their observed days while adding new creatives across the fortnight.

That constancy is the useful detail. The visible number did not expand, but the composition kept moving. Zoom’s ad refreshes overlapped with Zoomtopia announcements, the Onyx acquisition and the SDK repository push. Riverside’s navigation changed on 27 Oct, two days before its Agents app release on 29 Oct. Loom’s agent-facing homepage copy appeared on 24 Oct, one day after Zoom added seven Video SDK repositories and the same day Zoom announced Onyx.

Descript was pruning as well as shipping. On 23 Oct it removed four product pages tied to newsletter and onboarding unsubscribe options, search and an unsubscribe list page. On 24 Oct it removed five product pages including bradyyourtutor, espdaniella, sam-despo, this-is-tech-today and tour. On 28 Oct it removed pages related to event recording, season content and storyboarding. In a market obsessed with launch noise, removals were the cleaner positioning signal.

The category’s AI and developer push came with service noise. Zoom had minor service degradations on 20 Oct affecting meeting summaries via email for about 111 minutes and the UK website for about 598 minutes. It also reported incidents on 22 Oct affecting the Zoom Learning webpage for about 101 minutes, on 23 Oct affecting meetings services in the US with monitoring status, on 24 Oct affecting multiple services for about 46 minutes, and on 29 Oct affecting the Evaluations Acknowledge Button in Zoom Quality Management in the US for about 996 minutes.

Riverside reported two resolved minor incidents on 31 Oct, one lasting about 38 minutes and the other about 176 minutes. Descript reported a major outage on 28 Oct affecting Generate Layout that was resolved almost immediately, and on 30 Oct it was monitoring increased latency for agent API jobs. The strategic direction is clear, but reliability remains part of the product, especially when the new product surface is framed as an agent doing production work on the user’s behalf.