plugins/

Command encoding is an example plugin bundling three small, unrelated utility actions that don't individually warrant their own supervised process — "base64.encode@1", "base64.decode@1", "hash.sha256@1", and "uuid.generate@1" — the same "several actions, one process" pattern the "text" example plugin already establishes for string operations.

Command http is the reference example plugin demonstrating a real connector-consuming action (vision document section 7.4's http.request example): it contributes one connector type, "http.connection@1", and one action, "http.request@1", which requires that connector to be bound.

Command json is an example plugin contributing basic JSON manipulation actions — "json.parse@1", "json.stringify@1", "json.jsonpath@1", and "json.merge@1" — the kind of utility operations most real workflows need (e.g.

Command mysql is the fourth reference example plugin demonstrating a real connector-consuming action, mirroring plugins/examples/postgresql for a second SQL engine: it contributes one connector type, "mysql.connection@1", and two actions — "mysql.query@1" and "mysql.execute@1" — the same query/execute pair the vision document names for PostgreSQL (section 8.3), so a workflow author switching engines only changes which connector/action ids they bind, not the shape of a step.

Command openai is the second reference example plugin demonstrating a real connector-consuming action, this time targeting the OpenAI Chat Completions API specifically: it contributes one connector type, "openai.connection@1", and one action, "ai.generate_text@1" (the action id is deliberately generic — see the vision document's own example list, section 7.4 — so a future provider plugin could contribute the same action bound to a different connector, without workflows changing).

Command postgresql is the third reference example plugin demonstrating a real connector-consuming action (vision document sections 7.3/8.3): it contributes one connector type, "postgresql.connection@1", and two actions — "postgresql.query@1" and "postgresql.execute@1" — the exact pair named as the worked example in the vision document (section 8.3).

Command text is the reference example plugin from the vision document (section 20): a small library of text actions — "text.uppercase@1", "text.lowercase@1", "text.join@1", "text.split@1", "text.echo_connector@1" — all served by the same process.

Command time is an example plugin contributing basic date/time actions — "time.now@1", "time.format@1", "time.parse@1", "time.add@1", and "time.sleep@1" — the kind of utility operations most real workflows need (timestamps, expiries, scheduling windows, pacing).