LIOP Agent (CLI)

Zero-Config security gateway for desktop AI applications

The LIOP Agent is a pre-compiled, production-ready CLI utility included with the @nekzus/liop package. It acts as a bridge between standard AI interfaces (like Claude Desktop or Cursor) and the decentralized Logic-Injection-on-Origin Protocol.

Instead of writing a custom server, users can simply run the agent to instantly gain “Logic-Injection-on-Origin” capabilities.

Installation

The agent is distributed via the main SDK package. You can run it directly using npx:

npx -y @nekzus/liop

Or install it globally to have the liop-agent command available system-wide:

npm install -g @nekzus/liop
liop-agent

🤖 Claude Desktop Integration

LIOP is designed to be a drop-in replacement for MCP servers. To add LIOP tools to your Claude Desktop experience, update your configuration file:

Windows (%APPDATA%\Claude\claude_desktop_config.json)

{
  "mcpServers": {
    "liop-agent": {
      "command": "npx",
      "args": ["-y", "@nekzus/liop"]
    }
  }
}

Once configured, restart Claude Desktop. You will see the 🛡️ LIOP Guard status in your logs.

Core Features

1. Identity Persistence

The agent generates a unique PeerID (Ed25519 keypair) the first time it runs. This identity is stored in: ~/.liop/identity.json

[!IMPORTANT] If you move to a different machine, copying this folder will allow you to keep your reputation and verified access across the Mesh.

2. Autonomous Routing

The agent uses the LiopMcpRouter internally. When a tool call is received from Claude:

1. It queries the Kademlia DHT to find nodes providing that tool.
2. It establishes a Kyber768 + AES-256-GCM secure tunnel.
3. It executes the logic on the remote server and returns the verified result.

3. Bootstrap Discovery

By default, the agent connects to the official LIOP Alpha Nexus. However, you can point it to any mesh bootstrap node:

npx @nekzus/liop /ip4/1.2.3.4/tcp/4001/p2p/PEER_ID

Security & Diagnostics

The agent only communicates via STDIO. It prints status logs and discovery events strictly to stderr, ensuring that the stdout channel remains clean for valid JSON-RPC 2.0 messages required by the LLM client.

Local Mesh Diagnostics (LiopMeshStatus)

The agent automatically exposes a local diagnostic tool called LiopMeshStatus. When an LLM calls this tool, the agent intercepts it locally instead of routing it over the P2P network. It instantly returns a rich, human-readable report detailing:

• Connected Bootstrappers and Peer IDs
• Active Nodes (Vault, Bank, Oracle)
• Tool routing tables and Kademlia DHT state
• Token consumption and telemetry estimates

This allows AI clients to autonomously diagnose connection drops or verify which tools are available without burning bandwidth or duplicating diagnostic requests across multiple nodes.

If you encounter connection issues, check for the 🛡️ icon in the console or ask the LLM to call LiopMeshStatus.