The agent that grows with you
Python aiai-agentai-agentsanthropicchatgptclaudeclaude-codecodexhermeshermes-agentllmnous-researchopenai
catalog: bump iowap → 0.3.2
felix00eb4833d534
diff --git a/plugin-catalog/iowap.yaml b/plugin-catalog/iowap.yamlindex 0f6d22aca0d..b9bc7a68a66 100644--- a/plugin-catalog/iowap.yaml+++ b/plugin-catalog/iowap.yaml@@ -1,11 +1,11 @@name: iowaprepo: https://github.com/iowap-org/iowap-hermes-integration-sha: b67e0b276f2215434ecc27ef94f57b82192f6fbe+sha: 8ada6297345e0c5464e1b0015478867fd1c23944description: "Fleet control for Hermes Desktop: live statusbar chip (N/M IOWAP nodes online), a draggable fleet pane, a full fleet page (status, load, queue depth, capabilities per node, activity) and a tasks page that submits to any task-type capability on the fleet and tracks submitted tasks live (per-stage status dots, result previews, artifacts). Data stays local via the local node-cli against your own IOWAP relay; agent sessions join through an optional iowap-task bridge into a shared track store. Disclosure — the dashboard backend runs the local node-cli (the IOWAP node client from github.com/iowap-org/iowap-node) to read your relay's node list, capabilities and task results, and to submit tasks you start from the Tasks page to nodes on your IOWAP fleet. Relay health also goes through the local node-cli (`server health`) — the plugin itself makes no raw HTTP calls to the relay; node identity comes from the node's own ~/.relay state files. Tracked task ids are stored in your Hermes home under plugin-data/iowap/."maintainer: Kesuektier: communitycategory: desktop-version: "0.3.1"+version: "0.3.2"docs_url: https://github.com/iowap-org/iowap-hermes-integration#readmecapabilities:provides_tools: []