Mechanics that Travel

Vendors are not copying MCP or Plan Mode as brand names. They are copying machinery that already proved it can change a behavior that matters for agent products: trust enough to delegate, lower the cost of letting the agent cook, make work pick-up-able, and extend the product without rewriting the core.

Delegate with trust

People hand an agent more important work when they can inspect, constrain, and undo it.

Propose, then approve

The interesting part is not a Plan button. Someone proposes a piece of work, the work becomes visible before it becomes a change, feedback attaches to the proposal, and approval is what moves state. That is the pull-request mechanic wearing an agent costume. It lowers the cost of letting an agent cook because the human is reviewing a plan, not an already-mutated repo. Every tool that copied planning mode was copying that sequence, not a menu label.

Undo as a first-class verb

Stories did not win because photos disappeared. They won because they lowered the pressure to create. Checkpoints do the same job for agents. If you can rewind the session, you do not have to be sure before you delegate. The mechanic is a cheap undo that makes ambitious runs feel reversible. Tools that shipped rewind were not adding a setting — they were buying the user permission to take a bigger risk.

Permission envelopes

Delegation dies when the only options are 'trust everything' or 'approve every call'. An envelope — sandbox, allow-list, read-only, ask-once — lets people hand over more work without raising the blast radius. The mechanic is a fence you can see, not a terms-of-service paragraph. Once one vendor proved users would grant broader autonomy inside a fence, the rest of the category had to ship a fence too.

Show the thinking

Verification gets more likely when the reasoning is inspectable. Visible thinking is not a party trick — it is a way to check the agent's work without standing up a second reviewer. People trust a long, consequential run more when they can watch the argument form. That is why extended-thinking toggles traveled: they turn a black box into something you can audit while it is still running.

Reduce commit anxiety

Unfinished or agent-proposed work is cheap to share and cheap to revert, so people actually let the agent run.

Propose, then approve

The interesting part is not a Plan button. Someone proposes a piece of work, the work becomes visible before it becomes a change, feedback attaches to the proposal, and approval is what moves state. That is the pull-request mechanic wearing an agent costume. It lowers the cost of letting an agent cook because the human is reviewing a plan, not an already-mutated repo. Every tool that copied planning mode was copying that sequence, not a menu label.

Undo as a first-class verb

Stories did not win because photos disappeared. They won because they lowered the pressure to create. Checkpoints do the same job for agents. If you can rewind the session, you do not have to be sure before you delegate. The mechanic is a cheap undo that makes ambitious runs feel reversible. Tools that shipped rewind were not adding a setting — they were buying the user permission to take a bigger risk.

Make work multiplayer

Work becomes visible, reviewable, and pick-up-able by a human or another agent without a meeting.

Spawn a worker

A pull request makes work visible to other people. Subagents and background tasks make work visible to other workers. The human stays on one thread; the extra labor happens off to the side, with its own state, and reports back. The mechanic is fan-out without forcing the user to become a process manager. Once Cursor and Claude Code showed that parallel agents felt like more throughput rather than more chaos, every rival had to answer it.

Extend without rewriting

Third parties add capability so the product compounds instead of waiting on the vendor's roadmap.

Protocol, not plugin

A plugin marketplace is a vendor's garden. A protocol is a pipe anyone can attach to. MCP traveled because it let tools inherit the rest of the internet's connectors instead of rebuilding each one. The mechanic is interoperability as the product: once users could plug the same server into two agents, staying on a tool that could not speak the protocol started to feel like a tax. That is network-density machinery, which is why it copied faster than most features on this list.

Packaged recipes

Custom slash commands, skills, and lifecycle hooks are not power-user chrome. They let a behavior get written once and reused without opening the agent's internals. Contribution happens as a byproduct of solving your own problem, then sharing the recipe. The mechanic increases contribution without a giant reward — the same reason Stories and sticker packs spread. Tools that shipped a skill, command, or hook format were copying a way to let the crowd extend the product.

Keep context alive

The next session does not start from zero — the project, the web, and the user's intent survive.

Persistent instructions

AGENTS.md and CLAUDE.md are not documentation features. They are a way for work to leave enough context behind that the next session — or the next person — can pick it up without another meeting. The mechanic is memory that lives in the repo, not in a chat transcript that dies when you close the tab. Once one tool taught users to keep a file the agent always reads, every other tool had to honor the same file or lose the project's accumulated taste.

Live world input

An agent trapped in the repo is guessing. Web fetch, screenshots, and voice are the same mechanic in different costumes: let the model see the world the user is already looking at. That collapses the 'paste more context' ritual and makes the next turn cheaper. Vision and search copied quickly because users felt the absence immediately — a coding agent that cannot look at the error screenshot or the live docs is doing half a job.

Meet the user in habitat

The agent shows up where work already happens: the editor, git, CI, and the login people already pay for.

Native habitat

The mechanic is not 'we built an IDE plugin'. It is showing up in the habitat where the work already lives so using the agent does not feel like switching products. Editor extensions, git/PR actions, CI headless mode, and 'log in with the plan you already pay for' are all the same move: remove a context switch. Consumer apps learned this with sharing sheets and camera rolls. Agent tools learned it by embedding in VS Code, JetBrains, GitHub, and the subscription people already have.

How this is built

The behaviors and mechanics are a human-curated taxonomy — judgment about why a capability copied, not an automated notice that it did. First-ship dates come from the same release-note pipeline as Who Copies Whom?. See the methodology page.

Download the taxonomy (JSON) · Query the API · Who copies whom · Compare tools