cancel
Cancel the active dev workflow loop (archives by default, --hard to wipe)
Publish a local workflow directory to the cloud workflow hub
> /plugin marketplace add jie-worldstatelabs/stagent > /plugin install stagent@stagent
How it fires
How this command gets triggered: by you, by Claude, or both.
/publishContext preview
What this command does when you run it.
Publish a local workflow directory to the cloud workflow hub
description: "Publish a local workflow directory to the cloud workflow hub" argument-hint: "<workflow-dir> [--name <name>] [--description <desc>] [--dry-run]" allowed-tools: Bash, Read, Glob
Publish a local workflow directory to the workflow hub served by `$STAGENT_SERVER` (default: the baked-in plugin server).
The directory must contain `workflow.json`; `readme.md` and one `<stage>.md` per stage declared in `workflow.json` are optional but recommended. `name` defaults to the directory's basename; `description` is auto-derived from `readme.md`'s first non-heading line when omitted.
Arguments from the user: `$ARGUMENTS`
bash "${CLAUDE_PLUGIN_ROOT}/scripts/publish-workflow.sh" $ARGUMENTSThe script prints the resulting template URL on success, plus the one-line pull command a teammate can use from their own plugin:
/stagent:start --flow=cloud://<name> <task>
Open the template URL printed above to verify the README renders, the state-machine graph looks right, and each stage's markdown shows up when you click its node.
A Claude Code plugin that runs config-driven development workflows as a state machine. You declare stages, transitions, and inputs in a single workflow.json; the plugin's hooks and scripts drive the loop.
Repo: jie-worldstatelabs/stagent
Cancel the active dev workflow loop (archives by default, --hard to wipe)
Resume a paused dev workflow, or take over a cloud session from another machine
Create a new workflow suite (published to hub by default), or edit an existing one with --flow=<path>
Pause the active dev workflow loop without clearing state — resume later with /stagent:continue