Docs menu
⌘K

Core Concepts

Plugins

A skill teaches the agent a workflow. A plugin changes the CLI itself. It can add an auth provider, hook into a lifecycle event, register a TUI command, or provide a workspace adapter.

Install a plugin

midas plugin @acme/midas-plugin
midas plugin @acme/midas-plugin --global
midas plugin ./local-plugin.ts

Without --global, the plugin is added to the current project. With it, the plugin is available in every project. The command installs the package and updates config.

Load a local plugin

A plugin can also be a TypeScript or JavaScript file in .midas/plugins/ or ~/.config/midas/plugins/. Use this for a team plugin you do not want to publish to npm.

{
  "plugin": [
    "@acme/midas-plugin",
    ["./plugins/company-auth.ts", { "issuer": "acme" }]
  ]
}

What a plugin can add

  • An auth provider, so a company can sign in through its own identity service.
  • A hook on a lifecycle event, such as a session or a tool call.
  • A TUI command or a workspace adapter.
  • Configuration that other parts of Midas can read.

Safety

A plugin is code running on your machine with your account. It can do more than a skill, which is just instructions. Read the source before you install one, and pin a version for a team.

A plugin is not an MCP server. An MCP server adds tools to the session over a protocol. A plugin changes the CLI itself. See MCP for the tool path.

Related

  • Configuration has the full plugin section.
  • Skills is the instruction path for a repeatable workflow.
  • MCP connects an external tool.