What happened
Tencent announced Buddy One at its Global Digital Ecosystem Conference on October 29, 2026. The company describes it as a cross-application AI collaboration system for individual users. It links several Tencent workplace products—Tencent Docs, Tencent Meeting, Tencent Drive, the ima knowledge base, and the WorkBuddy agent—around a common WorkBuddy Agent foundation.
Access starts in the WorkBuddy desktop application. Users on WorkBuddy PC version 5.9.0 or later can open the personal area, go through Settings and the management center, and link the accounts they want to use. Tencent says that this removes the need to repeat authorization when using WorkBuddy and reduces the need to manually copy context between applications.
Once accounts are linked, a user can state a request in WorkBuddy rather than specify which connected application should be searched. The agent is intended to retrieve and combine material from authorized documents, meeting content, and knowledge bases. The report says the system uses “Buddy One cross-application search” and labels matched material with the application it came from, such as ima, Tencent Docs, or the WorkBuddy knowledge base. Answers are described as including sources.
Buddy One also changes how AI usage is metered across the connected products. WorkBuddy credits are upgraded by default into Buddy One credits that can be used in WorkBuddy, Tencent Docs, ima, and Tencent Drive. The balance is shared: consumption in one application reduces the balance across the connected set. Tencent says this includes credits in plans, promotional credits, and credits bought directly. Tencent Meeting is included in the connected product group and in the VIP bundle, while the supplied report does not describe it as a consumer of the shared AI-credit balance.
Tencent has also introduced a Buddy One VIP subscription priced at 700 yuan per month on a recurring monthly basis. It includes WorkBuddy Flagship, Tencent Meeting Professional, Tencent Docs Super Member Plus, shared cross-application AI credits, and 1 TB of storage usable across WorkBuddy, Tencent Docs, ima, and Tencent Drive. Tencent says shared memory between products is planned for a later stage, and that more products will join.
What the archive adds
This is a new event, but it adds a product-integration layer to Tencent’s earlier work on agent memory. Tencent-Hunyuan’s Hy-Memory release made persistent agent memory inspectable as a software stack; Buddy One says shared memory across workplace products is still to come. It also sits beside the earlier office-agent launch of MWS AI Cowork, while taking a different route: linking Tencent’s own applications under one account and credit pool.
Trend signal
No supplied site pattern is a close enough match: Buddy One demonstrates cross-application retrieval, but the material does not establish an external capability interface, governed memory write loop, or runtime security boundary.
Why now
Tencent announced Buddy One at its October 29 Global Digital Ecosystem Conference and made it available through WorkBuddy PC 5.9.0 or later. The source gives no further explanation of why Tencent chose this moment, beyond the launch and the accompanying subscription offer.
Connections to other events
The closest archive connection is Tencent’s Hy-Memory release, which framed persistent memory as inspectable software. Buddy One does not yet provide shared memory; Tencent says that feature will arrive later. The nearby MWS AI Cowork launch shows another office-task agent spanning documents, spreadsheets, websites, and connected applications. Buddy One’s distinguishing claim is not a broader task list but a common account, retrieval path, and consumption balance across a vendor-owned workplace suite.
Why it matters
For teams building AI assistants, the important unit is increasingly not a single chat interface or connector. It is a controlled route from a user request to authorized information held across several systems, with evidence about where the answer came from and a commercial model that spans products.
Buddy One illustrates both the promise and the design work involved. A user should not have to decide whether a meeting, document, drive item, or knowledge-base entry holds the answer. But builders still need to define account linking, the precise scope of each authorization, source attribution, and what happens when a shared balance is spent in another application. The announced future memory layer raises an additional question: which product can write what durable context, and how will a user inspect or revoke it?
What happens next
- Tencent adds the announced shared-memory capability to Buddy One. (3 months, 60%). Watch for: a product update defining which connected applications can read, write, inspect, or delete shared memory.
Limits and uncertainty
This Field Note is based on a report by IT Home describing Tencent’s announcement. The supplied material does not provide technical documentation, geographic availability, API access, data-retention terms, permission granularity, or independent testing of retrieval quality. It does not establish how source citations are generated, whether every connected source is searchable under every account configuration, or how conflicts between applications are handled. The planned shared-memory feature is an announced future capability, not a shipped feature in the material.
Skill to build now
Map one realistic cross-application question in your own workflow—for example, a request that needs a project document, meeting notes, and a knowledge-base policy. Define the minimum authorization each source requires, require the assistant to return source-level attribution, and decide whether usage should be billed per connector, per task, or from one shared allowance. This exercise exposes the product choices hidden behind the phrase “search everything.”
Reader takeaway
Buddy One is a concrete move from isolated workplace copilots toward an agent layer that can retrieve across a suite under one identity and one spending balance. The meaningful implementation question is not whether the agent can search more places, but whether its permissions, citations, billing, and eventually memory remain legible to the user.
Open question
When Tencent introduces shared memory, will users receive a clear, inspectable boundary between source retrieval and durable cross-application context?