When you add an MCP server in Manage > Apps and Integrations > MCP Servers, you'll choose how people connect: Personal, where each person signs in with their own account, or Shared, where an admin authorizes the connection once and everyone on a Knowledge Agent that uses the server is connected automatically. Previously, every person had to sign in to every server before they could chat. Now a shared server just works, with no sign-in prompts for your team at all.

If your integration runs on a service account or a single team credential, or you simply want a Knowledge Agent to work for hundreds of people without asking each of them to authorize, shared connections were built for you. Personal connections aren't changing, and they remain the right choice whenever actions should run under each individual's own account and permissions.

You choose the connection type deliberately when the server is created, and the account the admin authorizes with defines exactly what the connection can reach. Each person still reviews and approves the individual actions an agent wants to take on their behalf, just as they do today, so a shared credential never becomes a blank check. Guru manages the connection behind the scenes, keeping it healthy without anyone needing to re-authenticate.

A good first step is a low-stakes internal tool: set it up as shared, enable it on one Knowledge Agent, and watch teammates use it in chat without a single connect prompt. If you have questions about which connection type fits a given tool, your Guru team is happy to help.

This recap video gives a walkthrough of major September updates to Operator Mode and Knowledge Agent skill/prompt version histories:

Previously, finding copies of the same policy or process meant a manual audit. Now you can give your Quality Agent a plain-language rule, like "if this card is nearly identical to another card, unverify it." As it runs, the agent checks each card against the content it's scoped to. When it unverifies a card, it points to the duplicate it matched, so cleanup starts with a clear reason.

It's especially useful for teams with a lot of overlapping content, or anyone who has seen the same process written up in three different places. Whoever owns the agent sets it up. Everyone else simply benefits from a cleaner knowledge base.

It catches near-duplicates even when the phrasing has drifted. The agent only unverifies the card it's currently reviewing and never deletes or archives anything, so the final decision on what to merge or retire stays with you. When the agent links to a duplicate in its reasoning, your existing permissions still apply, so no one can open a card they aren't allowed to see.

Open your Quality Agent and add one simple duplicate rule. Review what it unverifies in your next quality results before building on it.

A complete, defensible history for your Knowledge Agent's prompts and skills

Previously, saving a change overwrote what was there, with no record of how the agent was configured before. Now every save creates a new version. A History button above the prompt in agent settings, and in each skill's options menu, opens a table of every version showing who made the change and when. From there you can view any version, compare two side by side, or revert to a previous version and add change notes. History covers changes made since May 2026.

. It's especially valuable for teams with audit, compliance, or regulatory obligations that need to show exactly how their AI was configured at any point in time. It's just as useful as a safety net if you iterate on prompts often. Access follows the same permission as editing the agent's settings, and the people chatting with your agent won't see anything change.

. A revert is recorded as its own event, so the history is never rewritten. Answer details now also show the exact prompt and skill versions used to generate each answer. That means you can trace a questioned answer back to the configuration that produced it, even after a dozen changes since.

. Start small. Compare the current version of a skill you've been iterating on against an earlier one, or open the details of a recent answer to see which version produced it. From there, the history builds itself every time you save.

Before, the agent followed one behavior everywhere. Now, on the agent's Slack tab, each channel can stay on its default or be customized. Open a channel's settings and you can set whether the agent responds to all messages or only when @mentioned, whether it does the same for thread follow-ups, and whether it responds to people, bots, or both.

Regular users do not configure anything. It is especially useful if you run both a high-traffic general channel and a dedicated Q&A or support channel from the same agent.

Every channel keeps its existing behavior until you choose to customize it, and each setting is independent, so you can be as precise as you want. In a focused Q&A channel, let the agent respond to everything and stay in the thread. In a busier channel, keep it to @mentions only, or filter out other bots so it does not react to automated posts. Even when thread responses are on, the agent only follows up in threads it is already part of, so it will not jump into unrelated conversations.

Start with a dedicated Q&A channel: let the agent respond to all messages and follow up in threads there, then keep busier channels tighter and adjust from what you see.

Previously, pointing a skill at a particular file meant naming it in the instructions and relying on the agent to search for it each time. Now you attach the document directly from a References section in the skill editor, and the skill grounds in that exact file. References are stored by the document's ID, not its name, so they keep working even if someone renames or moves the file.

It's aimed at Knowledge Agent Owners and Admins who want a skill to lean on a specific source, a brand guide, a policy doc, a pricing sheet, rather than whatever a search happens to surface. The people chatting with your agent don't need to do anything, and they don't need their own access to the referenced document. If you don't manage skills, nothing changes for you.

If a referenced document is ever archived or deleted, the skill doesn't fail, it keeps running and flags the reference so you know to update it. You manage everything from one References list in the skill editor, adding or removing references as your skills change.

Head to the skill editor, find the References section, and attach a document your skill depends on. Start with a skill that already leans on one specific source, that's where you'll feel the difference first.

Agents can create and organize collections and folders, move and archive cards in bulk, and run the full draft-to-publish loop on your behalf. Previously, an agent could find and explain your content but every actual change still meant opening the editor yourself. Now you can describe the change in chat — "reorganize these cards into folders by region," "draft a card summarizing this policy" — and the agent does the work.

It's especially built for admins and knowledge managers who spend time on structural upkeep: reorganizing collections, retiring stale content, or building out new spaces card by card. Everyday readers won't see anything change — this only affects what agents can do for the people who manage content, and only within the permissions those people already have.

An agent can only do what you can do — writes are permission-checked operation by operation. Cards are archived rather than permanently deleted, so anything an agent retires is restorable from the UI, and agents can't delete collections at all; that deliberately stays a human decision. Draft edits made from chat sync live into the editor, so if a teammate has the draft open, they see the agent's changes in real time and nobody's work gets overwritten. Agents can even add or remove collaborators on a draft — though a draft's owner can never be removed.

Open a chat with one of your Knowledge Agents and ask it to draft a new card on a topic you know well — it can build with headings, tables, callouts, and collapsible sections, so the result looks like a card your team made by hand. Once you've reviewed and published that first draft, work up to bigger jobs like reorganizing a folder or archiving outdated cards. This is live for all customers today.

Previously, when someone left your workspace, any draft only they owned was permanently deleted. Now those drafts persist, and workspace admins get full visibility into every draft in the workspace. From the Drafts tab in Card Manager, admins can filter between My Drafts, All Drafts, and Has no Collaborators, then claim any draft with one click to edit or publish it.

If you've ever offboarded an employee and wondered what in-progress knowledge walked out the door with them, this is for you. It's particularly valuable for teams with retention or audit obligations, where draft content may need to be produced on demand. Non-admins' experience doesn't change: you still see only your own drafts (plus a new Date Created column for everyone).

Claiming a draft is deliberate and scoped: joining grants you edit and publish rights on that one card only — it doesn't open up broad access to content across the workspace or change what appears in your search results. And the original author isn't cut out: when you claim their draft, they're kept on as a collaborator, so a returning teammate still has access to their own work. Nothing is reassigned automatically; admins claim drafts by choice, per draft.

Head to Card Manager → Drafts and check the Has no Collaborators filter — you might find work worth rescuing.

Instead of clicking through settings screens, just describe what you want: "I want you to be able to answer questions about our leave policy," and your agent drafts the skill with you. You can edit its instructions in plain language, or

If you own a Knowledge Agent — especially one using skills — Operator Mode is for you. It's the answer to the most common question we hear from teams building agents: "It gave a bad answer... now what?" You'll find it on your agent's Chat and Skills pages. (Regular users won't see it; entry requires the Manage agent settings permission.)

Every change your agent proposes comes with an explicit accept/reject confirmation before anything is written, so nothing changes without your sign-off. Once you approve, changes are live immediately — fix a skill after a bad answer, regenerate the response to confirm it's right, and the next person who asks gets the better answer automatically. Skills update in real time on the Skills page, and your Operator Mode sessions are visible only to you.

Operator Mode is live now for all customers. Open one of your Knowledge Agents, enter Operator Mode from the Chat or Skills page, and start with something small — ask it to explain a recent answer, or describe one new skill you've been meaning to build.

Your Knowledge Agents can now connect to Microsoft Work IQ, so they can work directly with these Microsoft 365 apps in real time.

Ask an agent to check your Outlook calendar, draft an email, search SharePoint, or post to a Teams channel, all from Guru chat and all under your existing Microsoft permissions.

An admin enables the Microsoft connections, you sign in once with Microsoft. A Microsoft 365 Copilot license is required to use these connections.