Skip to content

Plugins

Plugins add provider manifests, credentials, tools, runtime hooks, background work, and optional skills. Start with a packaged plugin when one exists; build a custom plugin only when the app needs a new provider or deterministic runtime behavior.

PluginUse it for
Agent BrowserBrowser automation
AmplitudeProduct analytics queries
CloudflareCloudflare resources and APIs
DatadogLogs, metrics, and incidents
GitHubRepository, issue, and pull-request workflows
HexHex projects and runs
LinearIssues and projects
MaintenanceRepository maintenance workflows
MemoryLong-term scoped memory
NotionNotion content
SchedulerDurable scheduled tasks
SentrySentry issues and telemetry
VercelVercel projects and deployments

Install only the packages the app needs:

Terminal window
pnpm add @sentry/junior @sentry/junior-github @sentry/junior-sentry

Create one plugin set for local development and production builds:

plugins.ts
import { defineJuniorPlugins } from "@sentry/junior";
import { githubPlugin } from "@sentry/junior-github";
export const plugins = defineJuniorPlugins([
githubPlugin({
botNameEnv: "GITHUB_APP_BOT_NAME",
botEmailEnv: "GITHUB_APP_BOT_EMAIL",
}),
"@sentry/junior-sentry",
]);

Point Nitro at the plugin module:

nitro.config.ts
import { defineConfig } from "nitro";
import { juniorNitro } from "@sentry/junior/nitro";
export default defineConfig({
preset: "vercel",
modules: [juniorNitro({ plugins: "./plugins" })],
routes: {
"/**": { handler: "./server.ts" },
},
});

Pass the same set to the app:

server.ts
import { createApp } from "@sentry/junior";
import { plugins } from "./plugins.ts";
export default await createApp({ plugins });

Manifest-only plugins may be registered by package name. Plugins with runtime hooks export a JavaScript factory. Each provider page documents its required registration and environment variables.

App-local declarative plugins live under the app content root:

app/plugins/<plugin-name>/
├── plugin.yaml
└── skills/
└── <skill-name>/
└── SKILL.md

Use this shape for app-specific provider configuration or workflows that do not need backend hooks. Runtime hooks and host tools require a code plugin; follow Build a Plugin.

Run validation before deploy:

Terminal window
pnpm exec junior check

If a plugin declares sandbox dependencies, also build its dependency snapshot:

Terminal window
pnpm exec junior snapshot create

Open the provider page for credential setup, or follow Build a Plugin for a custom integration.