npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ampcode/plugin

v0.0.0-20260329002101-ga1fed52

Published

Amp Plugin API

Readme

Amp Plugin API

Amp plugins are TypeScript files that extend and customize Amp. Plugins live in .amp/plugins/ (project) or ~/.config/amp/plugins/ (global).

The Amp plugin API is experimental. Expect many breaking changes if you choose to use it right now. Do not use it for anything critical.

The plugin API supports:

  • Event handlersamp.on(...) for hooking into tool calls, messages, and other events
  • Toolsamp.registerTool(...) for custom tools
  • Commandsamp.registerCommand(...) to add to Amp's command palette
  • User input and UIctx.ui.notify(...), ctx.ui.confirm(...)
  • AI & system utilitiesamp.ai.ask(...) for yes-no LLM answers

You can use plugins to:

  • Format files and report file diagnostics after each edit
  • Ensure Amp runs tests before finishing its work
  • Block or require confirmation for commands you deem risky
  • Correct common agent mistakes that AGENTS.md alone can't fix

See Amp Plugin API documentation.

Using Plugins

Run the Amp CLI with PLUGINS=all amp to use plugins. If the PLUGINS env var is not set, plugins are disabled. Plugins can execute arbitrary code, so only enable plugins when running Amp in trusted workspaces.

Limitations:

  • The Amp plugin API only works in the Amp CLI, not the Amp editor extension.
  • The Amp plugin API only works when the Amp CLI is installed via the binary install method, not via npm install.

Authoring Plugins

Use this prompt:

Make an Amp plugin to __________. See https://ampcode.com/manual/plugin-api for docs.
  • Ensure you're running with PLUGINS=all amp
  • Use Ctrl-o plugins: reload to reload all plugins after they're changed.
  • All plugin files must start with // @i-know-the-amp-plugin-api-is-wip-and-very-experimental-right-now.

Example Plugin

.amp/plugins/permissions.ts:

// @i-know-the-amp-plugin-api-is-wip-and-very-experimental-right-now
import type { PluginAPI } from '@ampcode/plugin'

export default function (amp: PluginAPI) {
	// Ask the user before executing any tool.
	amp.on('tool.call', async (event, ctx) => {
		const confirmed = await ctx.ui.confirm({
			title: `Allow ${event.tool}?`,
			message: `The agent wants to execute the "${event.tool}" tool.`,
			confirmButtonText: 'Allow',
		})
		if (!confirmed) {
			ctx.logger.log(`User rejected tool execution: ${event.tool}`)
			return {
				action: 'reject-and-continue',
				message: `User rejected execution of tool ${event.tool}.`,
			}
		}
		return { action: 'allow' }
	})
}

Acknowledgment

Amp's plugin API is inspired by pi's extension API, created by the awesome genius Mario Zechner.