web3blind

VK Messenger gateway with community Long Poll, media attachments, allowlists, and project-lane routing.

Durable non-blocking questions with exact answer binding and gateway continuation. Disclosure — its pre_gateway_dispatch hook sees every gateway message and consumes only `dq <id> …` answers from the stored recipient; with `enable_tool` on, the model can send questions to any chat the gateway already authorizes, and a question marked continue_agent resumes that chat's agent with the user's answer; questions and answers are stored unencrypted in $HERMES_HOME/deferred-questions/questions.sqlite3; it calls private gateway and adapter methods, so a Hermes update can break delivery until it is re-pinned.

One-use HTTPS forms for missing environment secrets, native encrypted Browser Vault logins/TOTP setup keys and payment cards, protected hosted payment-field filling, nested HTTPS verification codes/passcodes, and approved secret operations outside chat and LLM input. Disclosure — /senv setup supplies a skill using sudo for host packages and TLS setup after approval; the TLS listener binds all interfaces by default; pre_gateway_dispatch observes gateway messages to bind commands to their sender. In interactive Telegram sessions, secure_env_vault saves logins or fills a code field through the captured browser supervisor without explicitly submitting the site form. Explicit parent payment/nested-code targeting requires compatible host task/profile ownership and browser-generation evidence and fails closed without it; this is not a general fix for native Vault named-tab selection. Payment filling requires separate native consent and exact document/control guards; explicit resume requires existing nonempty values to match Vault. Site input callbacks, especially 3-D Secure, may authorize or auto-submit an operation. Unknown outcomes require external verification before retry. secure_operation executes administrator-allowlisted, SHA-256-pinned external Python consumers with gateway privileges; consumers are trusted, not sandboxed, and none are enabled by default. Secret input is not persisted by this mode; consumers must enforce their own handling policy. Links are bearer authorization, not submitter identity; cancellation cannot stop an already-running consumer.