Plugins

Boardwalk plugins let your coding agent drive the Boardwalk CLI for you: scaffold a workflow, run it locally, validate it, deploy it, and trigger runs, all from inside the harness you already use. Open source (MIT, source).

What a plugin is

A plugin is one shared skill set, use-boardwalk-cli, packaged for four harnesses: Claude Code, Codex, Cursor, and OpenClaw. It is not a workflow extension or a runtime add-on. It teaches the model the boardwalkcommand surface so that when you ask it to "ship this as a workflow," it knows exactly which commands to run. The CLI ships separately as @boardwalk-labs/cli and is what the plugin actually invokes, so install it too.

Install

Claude Code

claude plugin marketplace add boardwalk-labs/plugins
claude plugin install boardwalk@boardwalk-labs

Codex

npx codex-plugin add boardwalk-labs/plugins

Then open /plugins in Codex and enable boardwalk.

Cursor

Marketplace publication is pending. Until then, install from a local checkout of the repo by symlinking it into your Cursor plugins directory:

ln -s "$(pwd)" ~/.cursor/plugins/local/boardwalk

OpenClaw

openclaw plugins install ./

What it does

Installing the plugin gives the model the full CLI surface: init, dev, check, login, deploy, run, cancel, project linking, the credential-resolution order, the run-event channels, and the self-hosting knobs. The same skill is single-source-of-truth across all four harnesses, so a fix lands everywhere at once. For the commands themselves, see the CLI reference.