Vornik Companion

Good to know before installing

Talks only to the self-hosted Vornik daemon at VORNIK_URL with VORNIK_BROKER_TOKEN (and VORNIK_MEMORY_TOKEN for memory); broker tools let the agent start operator-approved workflows on that daemon (writes are approved by a person in Vornik); when selected as memory provider it sends each turn's user query for recall, mirrors MEMORY.md and USER.md writes to the daemon, and asks the daemon to stop recalling (not delete) a mirrored entry that Hermes removes or replaces (/vornik-memory lists and /vornik-forget forgets what Vornik keeps); artifact tools expose only named outputs allowed by the approved workflow from completed runs and read bounded text or return short-lived binary download links from the daemon; task diagnosis tools (offered only when the daemon advertises companion-progress) return a broker task's execution events and closed error classes as the daemon serves them to a broker key; hermes vornik approvals on writes security.approval.transport (and vornik_companion.approval_namespace) to Hermes config, after which Hermes's own dangerous-command prompts (the redacted command text) are sent through the local vornikctl agent host-approval to the daemon and answered on the p

From the plugin's catalog listing.