Pulse CLI
The Pulse CLI lets an AI agent, or you at a shell, operate a Camunda 7 process engine: Operaton, CIB seven or Camunda 7. The agent names what should happen in one short command, and the CLI sends the requests to the engine's REST API.
sh
npx @miragon/pulse-cli guide| Page | What it covers |
|---|---|
| Getting started | A first triage and process, then your engine, Claude Code or CI |
| Installation | npm, Homebrew, standalone executable, container image, shell completion |
| Workflow commands | Inspect, wait, advance, retry, deploy, status |
| Command structure | Names, arguments, variables, request bodies, files, dates |
| Output and errors | Formats, previews, error fields, exit codes |
| Configuration | Options, environment variables, config and project files, profiles |
| Authentication | Basic auth, OAuth logins, bearer tokens, token commands, other headers |
| Safety | Previews, confirmation, read-only mode |
| Recipes | Command lines for everyday tasks |
| AI agents | The guide, the Claude Code plugin and its skill |
| Engines | Compatibility, choosing the engine, adding a difference or an engine |
| Architecture | Engine port, adapters, catalog generation |
| Architecture decisions | Why the CLI is built the way it is |
| Development | Building and testing the CLI in the Pulse repository |