Skip to content

Glossary

AI copilot

An AI copilot is help built into the tool you are already in, and what distinguishes it is placement rather than capability: it starts with your work in front of it instead of asking you to describe it.

In plain terms

Help that lives inside the software you were already using. You do not switch to another window and explain the situation, because it can see the document, the spreadsheet or the code in front of you. That saves the explaining, which is most of the effort, and it also means you get whatever help that vendor decided to build.

01

Why it matters

Because the explaining is the expensive part and this removes it. Describing a spreadsheet to something that cannot see it takes longer than the edit, so the same capability delivered in place gets used many times a day where the same capability in a separate window gets used occasionally, and adoption follows placement far more reliably than it follows quality.

02

How it works

It begins with access to what you are working on, which is the whole of the difference. The document, the sheet, the mailbox or the repository is already there, so a request can be short and specific rather than a paragraph of setup, and short specific requests are the ones people actually make.

The vendor chooses what it can do, and that boundary is firmer than it looks. Where a separate assistant will attempt anything you describe, one built into a tool does the things its maker wired up, so it may be excellent at rewriting a paragraph and unable to help with the thing next to it.

It usually inherits the permissions already in place rather than establishing its own. Whatever the product decided you may see is what it works from, which is why this arrangement passes security review more easily than a separate tool asking to connect to everything, and why the answers it gives differ between colleagues.

Quality varies enormously behind a similar-looking button, and the phrase itself tells you nothing. Some are deeply wired into the product's own data and actions; others are a general assistant in a sidebar with the current file pasted in, which is a different thing entirely wearing the same label.

The lock-in is real and worth naming. Help that only exists inside one product becomes a reason to stay with that product, so the convenience is genuine and the strategic cost is paid quietly over several years rather than at the point of purchase.

The same request, two places

The same request, two placesIt is tempting to treat this as a convenience story, and it is really an adoption story. Any capability with a setup cost attached gets reserved for work large enough to justify the setup, which means it is used for the occasional big job and never for the constant small ones. The constant small ones are where the hours actually go. Removing the setup does not make the tool better at its job; it changes which jobs get given to it, and the aggregate effect is far larger than the per-task improvement suggests. This is also why buying decisions made on demonstrations mislead so consistently. A demonstration shows one impressive task done well, which is the case where the setup cost was always going to be worth paying, and it tells you almost nothing about the forty small requests a day that decide whether anyone still uses the thing in March.In a separate assistantPaste or describe the contextfirst.Explain what the columns mean.Get the answer, copy it back.Worth doing for a big task.Inside the tool"Summarise this by region."It already knows the columns.The change lands where itbelongs.Worth doing forty times a day.The right column is not fasterat the task. It is faster ateverything around the task, andthat is what decides whether acapability gets used.
It is tempting to treat this as a convenience story, and it is really an adoption story. Any capability with a setup cost attached gets reserved for work large enough to justify the setup, which means it is used for the occasional big job and never for the constant small ones. The constant small ones are where the hours actually go. Removing the setup does not make the tool better at its job; it changes which jobs get given to it, and the aggregate effect is far larger than the per-task improvement suggests. This is also why buying decisions made on demonstrations mislead so consistently. A demonstration shows one impressive task done well, which is the case where the setup cost was always going to be worth paying, and it tells you almost nothing about the forty small requests a day that decide whether anyone still uses the thing in March.
03

Seen in the wild

  • A coding assistant embedded across every major editor, wired into the flow of repositories, branches and pull requests rather than sitting beside it.

    GitHub Copilot
  • AI threaded through an office suite, working inside the documents, mail and meetings on an organisation's own tenant under the permissions already there.

    Microsoft Copilot
  • A workspace layer that drafts and edits in place and answers from the pages and databases the team already keeps.

    Notion AI
04

Common misconceptions

People assume

It is the same capability as a standalone assistant, just placed differently.

In fact

Placement changes what gets asked, which changes what gets used. A request that would take a paragraph to set up elsewhere takes four words here, and the things people do many times a day are exactly the things that were too tedious to explain, so the usage pattern is not a subset of the other one.

People assume

Anything called a copilot is deeply integrated.

In fact

The label covers both a deeply wired feature and a general assistant in a sidebar with your current file pasted into it. Telling them apart takes a specific test rather than a demonstration: ask it something that requires knowing your data rather than your document.

People assume

Buying one is a small decision because it comes with the tool.

In fact

It is a small decision that compounds. Help existing only inside one product is a reason to keep that product, and teams that came to depend on it find the switching cost is no longer only the data and the training but the working method that grew around it.

05

Telling them apart

AI copilot vs AI assistant

AI copilot

Inside the tool, starting from your work.

AI assistant

A separate place you go and describe things to.

The first cannot help with anything its maker did not wire up; the second will attempt anything and knows nothing about your situation.

06

Questions

How do I tell a real one from a chat box in a sidebar?
Ask it something that requires knowing your data rather than reading your screen. A genuinely wired feature can answer about records, history or state it was given access to; a general assistant with your file pasted in can only work with what is visible, and the difference shows immediately.
Is it better than a general assistant?
For work inside that tool, usually yes, because the setup cost is gone. For anything crossing tools, or anything its maker did not anticipate, it is worse or simply unavailable. Most teams end up with both, which is a reasonable outcome rather than a failure to decide.
Does it see everything in our account?
It generally works within the permissions already governing you, which is why this arrangement clears security review more easily than a separate tool asking for broad access. The practical consequence is that two colleagues can ask the same question and get different answers, which is correct behaviour rather than inconsistency.
What should we actually check before rolling one out?
Whether it does the specific things your people do repeatedly, rather than whether it demonstrates well. A convincing demonstration establishes that the capability exists somewhere in the product, and daily value comes from a handful of repeated actions, so testing those directly settles the question in an afternoon.
07

Key takeaways

  • Placement, not capability, is what makes this a different thing.
  • Removing the explaining is what turns occasional use into daily use.
  • The vendor's wiring sets a firm boundary the label does not reveal.
  • It usually inherits existing permissions, which helps it clear review.
  • Convenience now, switching cost later; both are real.
09

Tools that use this

  • GitHub Copilot

    Embedded across editors and wired into the repository workflow.

  • Microsoft Copilot

    Inside the office suite, on the tenant's own files and permissions.

  • Notion AI

    Drafts in place and answers from the team's own pages.

Last checked July 2026

All glossary terms