your 5dive doesn’t have to look like ours. build the piece you need.

Every company has a workflow that sounds a little weird when you explain it to someone else. Your agents need to work with yours. You can build that missing piece as a plugin, without waiting for our roadmap.

the thing only your team needs

Maybe deployments need an approval in a tool your team built. Maybe Friday means a report for three people who want it formatted a very particular way. You know the one.

Put every request like that into core and everyone inherits everyone else’s workflow. The runtime gets bigger, and changing your own little corner means understanding more of it.

We’re making those pieces plugins. Core stays the runtime. Your addition lives in its own repo, with its own code and a job you can actually describe.

Adding one looks like this:

sudo 5dive plugin add <owner>/<repo>
sudo 5dive plugin list

Any repo that follows the 5dive plugin format installs this way, your own included. Only plugins from 5dive’s own GitHub count as official. For anything else, the install says so before any code lands: “Not from 5dive. It runs with your agents’ access; there is no sandbox.”

In a terminal, add shows where the plugin comes from and what it will get, then waits for your yes. Read that before you agree.

On 5dive.ai, Marketplace → Plugins → Install from a repository is for 5dive’s own plugins. For one you or someone else built, ask your box’s first agent to install it.

we moved our own first

The council is now an opt-in plugin. A box that never uses it no longer loads about 12,000 lines of it on every command.

sudo 5dive plugin add 5dive-ai/5dive-council

Already have councils? Add the plugin and they keep working. Their data stays where it was.

The web UI is a plugin too:

sudo 5dive plugin add 5dive-ai/5dive-ui
5dive ui

Core owns the data. The plugin owns the page. Changing a screen used to mean cloning the whole runtime. Now it’s one repo you can read in an afternoon.

Voice and browser each live in their own repo and install the same way. Voice lets you speak with your agent and hear it talk back. Browser is the big one: agents that use websites.

the council left core. the UI left core. voice and browser live in their own repos.

You choose the pieces your company uses, and you can build the next one.

what can yours add?

A plugin can add a channel, a command, a skill, an MCP server or a hook. A channel gives you another way to talk to your agents, like voice. A command gives your box a new verb:

5dive <verb>

Skills and MCP servers reach every agent on the box, including agents you hire later. Claude Code agents get them natively. Other agent types get them through their AGENTS.md.

A plugin can’t take over a built-in command. Installation also refuses a second plugin claiming a command that’s already taken.

Some things you could build:

• An internal deploy command that follows your team’s process.
• An approval step that goes to your own tool.
• A connector for your CRM or support desk.
• A connection to a Raspberry Pi or lab device.
• A report only your team reads.

A plugin doesn’t need an audience beyond the people who use it.

build it, or have your agent build it

A plugin is a normal repo in the Claude Code plugin format, plus one small 5dive section in the manifest that says what the plugin adds and what it needs. A plain Claude Code plugin without that section is refused.

It has .claude-plugin/marketplace.json at the root, and the plugin itself has a manifest, .claude-plugin/plugin.json. A new command is a script at bin/<verb>.

Start from the 5dive plugin template, the smallest plugin that installs: one command, one skill and two settings. Press Use this template on GitHub, rename it, then build from there.

Give your agent the workflow: what starts it, what it should do, and what you want back. Point it at the template and ask it to build that as a plugin. Keep the first version small enough that you can read it and try the whole thing yourself.

You can upgrade it later, disable it while leaving the code on disk, remove it, or rollback to an older version. It’s your box, so you’re the off switch for every plugin on it.

keep it or share it

Your company’s plugin can stay private. If it turns out to be useful beyond your team, publish the repo so someone else can use it too.

need something 5dive doesn’t ship? tell your agent to build it as a plugin, starting from the template. keep it to yourself, or put the repo on github if someone else could use it.

Get a managed box at 5dive.ai, or self-host from github.com/5dive-ai/5dive.

Photo: u/m_dstoic via r/MechanicalKeyboards.