Amp от Sourcegraph добавил глобальные плагины и навыки для AI-агентов

Sourcegraph in August 2026 added global plugins and skills to the AI coding agent Amp — extensions are now stored in the company's cloud, work across all projects and devices without manual synchronization of configuration files.

How do Amp's global plugins and skills work?

Global plugins and skills are cloud-based extensions of the Amp agent that work everywhere Amp is running: on a local machine, in CI, and in orbs environments. Previously, users stored plugins locally in the `~/.config` directory, making them inaccessible to other team members and requiring manual synchronization when switching devices.

A plugin in Amp's terminology is a set of instructions and tools that change the agent's behavior. A skill is a more specific capability: running a formatter on every file being edited, browser testing, creating release notes from a template. Through the agent in natural language, you can now:

• create a personal plugin that runs a formatter on every file the agent edits;
• import a browser testing skill from a repository into personal skills for all projects;
• find out if anyone on the team has a skill for writing release notes;
• check whether imported plugins are outdated.

For workspace administrators, an additional option is available: copying a specific member's plugin to the team workspace. Management is done through the User Settings and Workspace Settings sections in the Amp interface.

How do personal plugins differ from team plugins?

Personal plugins are designed for experimentation: a user can ask the agent to build something new and immediately reload plugins in the same thread, without restarting the development environment. This reduces the iteration cycle to a few seconds.

Team plugins are published by workspace administrators and are loaded by default for the entire team. Sourcegraph recommends the following sequence: first test the plugin in personal space, ensure it works correctly — and only then publish it to the team. If major changes are needed to an existing team plugin, it is worth importing it to personal space, refining it, and publishing the updated version.

"Personal plugins and skills are much more than a replacement for `~/.config`: they can be shared with the team so people can discover, import, and remix them," — from the official

Amp blog.

Remix and update in a single command

Amp supports full plugin sharing and remixing. A personal plugin can be opened to the workspace; other members can find it, import it, and adapt it to their tasks. If updates appear in the original — just run the command `amp skill update <name>` or `amp plugins update <name>`, or ask the agent to update the skill to the latest version.

According to the Amp blog, global plugins are becoming not just a replacement for local configuration files, but a full-fledged platform for discovering and sharing extensions within an organization — analogous to npm packages or VS Code extensions.

What this means

Agentic development environments are growing ecosystems of extensions — just like IDEs did back in the day. Team sharing and plugin remixing lower the barrier to entry for the entire team: there is no longer a need to write configuration from scratch, it is enough to import and adapt a colleague's ready-made skill. This is especially valuable for companies with dozens of developers, where standardizing agent behavior is organizationally beneficial. If this pattern spreads to other AI development tools, "installing a plugin for an agent" will become as routine an action in a couple of years as installing an extension in VS Code.