All plugins

opensop

GitHub profile1 plugin in the catalog

Plugins by opensop

1 plugins by opensop in the catalog, most-starred first.

opensopopensopTurn your best agent workflow into a file anyone can run. An OpenSOP process file sets, step by step, what is a script (must be certain) and what needs the agent (judgment). Hermes starts a run with sop_run, does its steps and submits them with sop_submit; the next script step checks the work, so scripts decide done. The run lives on disk, not in the conversation: Hermes is re-anchored on its open step every turn and across compaction, nudged to finish it before wrapping up, and refused when it tries to decide a step reserved for a person (seat belts, not a sandbox). Any agent or person can pick the run up with the opensop CLI, and every step leaves a receipt. Requires the opensop CLI 0.10.0+ on PATH. Disclosure — sop_run, sop_submit and sop_retry go through Hermes's approval prompt (process hash, inputs, run id, run folder) because a run's script steps run as shell commands with your permissions, outside Hermes's terminal approvals; a run this profile started or continued through an approved call does not prompt again. llm and judgment steps can drive coding-agent CLIs (claude, codex, cursor-agent, kimi) with the permission the file declares, so only run process files you trust. The plugin has no credentials of its own. It runs opensop with a scrubbed environment: PATH, HOME, LANG, LC_*, TMPDIR, SSH_AUTH_SOCK, OPENSOP_*, the variables the process file references (env.X / ${env.X}), and ANTHROPIC_API_KEY only when the file has an llm or judgment step on a claude* model (the CLI calls the Anthropic API directly for those). The approval prompt lists which variables will be forwarded. Hermes's other provider keys never reach script steps or the agent CLIs they drive. Run folders are written under OPENSOP_LOCAL_HOME, the nearest .opensop cell or ~/.opensop-local; the plugin keeps a session-to-run map and approved run folders in plugin state. Tool calls are bounded by the plugin's timeout setting (plugins.entries.opensop.settings.timeout, default 1800 s); on timeout the CLI and its child processes are stopped. The plugin makes no network calls, never auto-approves or changes approval settings, starts no Hermes children, runs nothing in the background and has no self-updater.Communityautomation