# Plugins: let agents use your own tools

A plugin adds actions to your account. Agents call them as tools. Under the default policy, no write runs until a person approves it.

Source: https://codeherder.com/blog/plugins-connect-your-own-tools/

November 12, 2026 · The CodeHerder team · 2 min read

- [product](https://codeherder.com/blog/topics/product/)
- [workflow](https://codeherder.com/blog/topics/workflow/)

A plugin adds actions to your account. An action is a short, fixed job. It can call CodeHerder, or it can call an outside service over HTTPS.

An agent can run an action as a tool. A plugin can also run an action on its own when an event happens in your workspace.

## What an admin approves

A plugin does nothing until an admin installs it. At install, the admin ticks each CodeHerder action the plugin may call. The plugin never gets more than that.

Each install creates one agent, named after the plugin with “(plugin)” at the end. That agent gets the lowest role that covers your approvals. It is never owner.

## Ask or Allow

Every action is a read or a write. The write policy decides what happens to a write.

- Ask is the default. A write waits for a person.
- Allow runs the write at once. Use it only for a plugin you trust.

A read always runs.

Under Ask, an agent that wants to write files a question. The task waits until a person answers. A write that starts from an event becomes an offer. An offer expires after 7 days.

## What agents get

Each action becomes a tool on every harness. The agent gets the tool when you approved every CodeHerder action it calls. If the plugin needs a connection, the agent gets the tool after you connect it.

## Two plugins ship today

### Onboarding task

This plugin creates a first task in each new workspace. Under Ask, it offers the task and waits for you.

### HTTP endpoint

This plugin sends a JSON body to one HTTPS endpoint when an event happens. You choose the event. It does nothing until you pick one.

## Try it from the CLI

```
ch plugin catalog
ch plugin install builtin:onboarding-task --approve task.create
ch plugin run <installId> <actionId> --input '{"title":"Try it"}'
ch plugin runs
ch plugin offers --status pending
```

`ch plugin run` goes through the same checks as an agent’s call. `ch plugin runs` shows each hook run, its outcome and any error.

## For leaders

You do not need to read code for this part. Under the default policy, nothing writes until a person approves it. CodeHerder records every hook run, so you can see what ran. `ch plugin offers` lists each write that waits for a person.

A plugin is not a plugin source. A plugin source copies skills, agents and commands into your catalog. A plugin adds actions.

## Learn more

- [Plugins](https://codeherder.com/docs/plugins/) in the docs
- [Plugin sources](https://codeherder.com/docs/plugin-sources/)
- [Asking a human](https://codeherder.com/docs/asking-a-human/)
- [All integrations](https://codeherder.com/integrations/)
