Nostr VPN

Humans and agents

A private network for your agent.

Let an agent reach a service on your own computer or server. Local keys and signed network approval replace the VPN provider signup. No email or phone number is required.

By Nostr VPN ยท Updated

Can an agent use Nostr VPN?

Yes, when its execution host can run the nvpn daemon and has permission to configure a VPN. A terminal alone is not enough: Linux needs a tunnel device and network administration permissions. Hosted agent computers may not provide them. Check the host before installation; use a supported computer you control when needed.

The agent workflow guide covers installation, persistent identity, signed enrollment, JSON status, and an end-to-end connection check.

Install the agent plugin

The plugin packages the same command line workflow for Codex, Claude Code, Grok Build, and Hermes. It adds instructions; installing it does not start a VPN or grant networking privileges.

hermes plugins install mmalmi/nostr-vpn/plugins/nostr-vpn --no-enable
hermes plugins enable nostr-vpn

For other platforms, follow the plugin installation guide. OpenAI's local-program plugin path requires desktop execution. A dot can use a supported local task on a connected computer; a cloud-only dot does not gain that access by installing the plugin. Grok Bot can follow the guide using its terminal where the host permits VPN operation.

Prove the connection works

  1. Choose the two devices.

    Use a computer that runs the agent and a device hosting a service you want it to reach. Initialize separate identities and keep their configuration in persistent private storage.

  2. Approve the joining device.

    Follow the released CLI quickstart. The administrator reviews and approves the signed request in the app. The source guide documents newer headless approval commands; check the installed CLI's help before using them.

  3. Check daemon status.

    Run nvpn status --json with the same configuration used to start the daemon. Require a daemon-backed status before interpreting readiness. A saved configuration alone does not prove there is a live VPN.

  4. Reach the intended service.

    Request the actual service at the peer's VPN address or .nvpn name. Report whether it responded, and test name resolution separately. Stop the test session when finished.

Private network enrollment remains an administrator decision. No provider signup does not mean automatic access to someone else's devices. Paid exits are a separate, experimental feature and require funding; they are not needed for this private mesh workflow.

More tools without provider signup

Hashtree Git lets agents publish code with ordinary Git commands. Iris Chat lets you exchange private messages with your agent. Use each independently, or receive a request in Iris, work through a private connection, and return a repository link.