Bridge keep everything local, but make it accessible from anywhere through open infrastructure. CEP-22 and CEP-41 forced me to start playing with @ContextVM. So I tested with something I work with everyday, my hermes agent. An experiment that I Think it was worth every sat paid on @routstr to build it. Sending media files over ContextVM is probably not what it was designed for, but it's a discussion for a different post. hermexVM @routstr for open model routing. @ContextVM over Nostr for the encrypted connection. What you can do in a conversation ● Chat with any configured Hermes agent and receive responses live. ● See thinking, status updates, tool calls, progress, output, and errors as they happen. ● Approve or reject sensitive tool actions and answer the agent’s clarification questions. ● Reply to or copy individual messages. ● Render rich Markdown, including code blocks and links. ● Take Photos, attach images, audio, video, PDFs, archives, code, text, and other files. ● Record voice messages and turn them into an editable transcription before sending. ● Send selected messages or a full transcript to another agent, either as a new conversation or into an existing one. Features ● Multiple Hermes agent profiles. ● Persistent conversation history with automatic resume and live reattachment after connection drops. ● Model selection for each conversation. ● Project selection and project creation. ● Searchable Hermes skill picker, grouped by category. ● Linked conversation and agent-handoff history. ● Automatic upload retry and recovery from temporary relay failures. ● Explicit client allowlisting at the bridge. ● Android and web support—the web client can also be built and published as a Nostr nsite. ● Connect to multiple Bridges. image and on @Zapstore #Bridge #hermexVM #Hermes #Routstr #ContextVM #Nostr #localfirst

Replies (1)