Installing and managing plugins

Agento loads plugins from both local files and published npm packages.

Plugin discovery scopes

Plugins can be registered in two scopes:

1. Project scope: <workspace>/.agento/plugins/ or listed in <workspace>/.agento/config.json.
2. Global scope: ~/.config/agento/plugins/ or listed in ~/.config/agento/config.json.

Configuring plugins

To enable plugins in your repository, list their package names or file paths in .agento/config.json:

{
  "$schema": "https://agento.tekibo.in/schemas/config.json",
  "plugins": [
    "@my-org/agento-plugin-database",
    "@community/agento-plugin-docker",
    "./.agento/plugins/local-rules.ts"
  ]
}

Installing local TypeScript plugins

For project-specific tools, place your plugin TypeScript file directly inside .agento/plugins/:

.agento/
├── config.json
└── plugins/
    └── staging-deployer.ts

In .agento/plugins/staging-deployer.ts:

import { definePlugin, defineTool, z } from "@agento/sdk";

export default definePlugin({
  id: "com.myrepo.staging",
  name: "Staging Deployment Tools",
  version: "0.1.0",
  registerTools() {
    return {
      trigger_staging_deploy: defineTool({
        description: "Trigger a deployment to the team staging environment",
        parameters: z.object({
          branch: z.string().describe("Git branch to deploy"),
        }),
        execute: async ({ branch }) => {
          return { status: "queued", branch, timestamp: new Date().toISOString() };
        },
      }),
    };
  },
});

Agento automatically loads and activates TypeScript plugins from .agento/plugins/ at session startup.