Rune

FHE-Encrypted Organizational Memory for AI Agents

Rune is an agent-native plugin that transforms organizational memory into a strategic asset by connecting the isolated activities of local agents through encrypted memory.

Works with Claude Code, Codex CLI, Gemini CLI, and any MCP-compatible agent.

# In the Claude Code session
/plugin install github.com/CryptoLabInc/rune

# In the Codex CLI session
$skill-installer install github.com/CryptoLabInc/rune

What is Rune?

This is the complete plugin with everything needed to run Rune locally:

• MCP server with FHE-encrypted vector operations (enVector + Vault integration)
• Capture filtering and recall via FHE-encrypted pipelines
• Installation scripts for Claude Code, Codex CLI, and manual setup
• Agent specifications (Scribe for capture, Retriever for recall)

Requires external infrastructure (deploy separately):

• Rune-Vault server (team-shared, deployed by admin — see rune-admin)
• enVector Cloud account (sign up at envector.io)

MCP Tools

Rune exposes these tools via MCP (stdio transport). Any MCP-compatible agent can use them directly.

Tool	Description
capture	Capture organizational decisions via FHE-encrypted storage pipeline
recall	Search encrypted team memory via Vault-secured pipeline (query expansion → encrypted scoring → Vault decryption)
vault_status	Check Rune-Vault connection status and security mode
reload_pipelines	Re-read config and reinitialize scribe/retriever pipelines

Example — capture a decision:

capture(text="We chose PostgreSQL over MongoDB for better ACID guarantees and JSON support.")

Example — recall past context:

recall(query="Why did we choose PostgreSQL?", topk=5)
→ { found: 3, results: [...], sources: [...] }

Quick Start

Claude Code

$ claude plugin marketplace add https://github.com/CryptoLabInc/rune.git
$ claude plugin install rune

• In the Claude code session:

> /plugin marketplace add https://github.com/CryptoLabInc/rune.git
> /plugin install rune

Codex CLI

In the Codex CLI session:

> $skill-installer install https://github.com/CryptoLabInc/rune.git

Gemini CLI

$ gemini extensions install https://github.com/CryptoLabInc/rune

Other Agents

See AGENT_INTEGRATION.md for Gemini CLI, OpenAI, and custom MCP client setup.

After Installation

Run /rune:configure and follow the instructions given by the agent.

Architecture

Your Machine                    Cloud / Team Infrastructure
━━━━━━━━━━━━━                  ━━━━━━━━━━━━━━━━━━━━━━━━━━
AI Agent + Rune Plugin
  ├─ enVector MCP Server ──→   enVector Cloud (encrypted vectors)
  │    └─ recall tool    ──→   Rune-Vault (team-shared, secret key holder)
  ├─ Scribe (capture)               decrypts result ciphertext, returns top-k
  └─ Retriever (recall)

Supported Agents: Claude Code, Codex CLI, Gemini CLI, custom MCP clients

flowchart TD
    Cloud[("enVector Cloud<br>(Encrypted Storage)")]

    subgraph MCP [envector-mcp-server]
        Capture["capture tool<br>(local secret key, owner's data)"]
        Recall["recall tool<br>(Vault-secured, shared team memory)"]
    end

    subgraph Vault [Rune-Vault]
        Decrypt["decrypt_scores()<br>(secret key holder)"]
    end

    subgraph Client [Client Agents]
        Agent["Claude / Gemini / Codex / Custom"]
    end

    %% Capture flow
    Agent -- "capture" --> Capture
    Capture -- "|Encrypted Data|" --> Cloud

    %% Recall flow (4-step pipeline)
    Agent -- "recall" --> Recall
    Recall -- "1. encrypted similarity scoring" --> Cloud
    Recall -- "2. decrypt result ciphertext<br>(secret key never leaves Vault)" --> Decrypt
    Decrypt -- "indices + similarity values" --> Recall
    Recall -- "3. retrieve + decrypt metadata<br>4. return raw results" --> Agent

    %% Styles
    style Cloud fill:#eff,stroke:#333
    style Capture fill:#eef,stroke:#333
    style Recall fill:#eef,stroke:#333
    style Decrypt fill:#fee,stroke:#333
    style Agent fill:#efe,stroke:#333

Loading

Data Flow:

• Capture: Agent evaluates + extracts → MCP capture → Tier 1 embedding check → FHE-encrypted insert → enVector Cloud
• Recall: MCP recall → query expansion → encrypted similarity scoring on enVector Cloud → Rune-Vault decrypts result ciphertext (secret key held exclusively by Vault) → retrieve and decrypt metadata → return raw results to agent

Key Design:

• Agent calls MCP tools (capture, recall). Agent never contacts Vault directly.
• recall tool uses a Vault-secured pipeline. The secret key never leaves Vault. This isolation prevents agent tampering attacks from indiscriminately decrypting shared vectors.
• Rune-Vault holds the secret key exclusively. It decrypts only score ciphertext and metadata ciphertext — never sees raw vectors.
• envector-mcp-server uses Public Keys (EncKey, EvalKey) for encryption and search. No LLM API key required — agents handle evaluation and extraction directly (agent-delegated mode).

Prerequisites

Before installing, you need:

1. Rune-Vault Access (from your team admin)

• Vault Endpoint: Your Vault gRPC endpoint (e.g., vault-host:50051)
• Vault Token: Authentication token provided by your admin

2. enVector Cloud Credentials

• Cluster Endpoint: Your enVector endpoint (e.g., runestone-xxx.clusters.envector.io)
• API Key: Your enVector API key

Don't have these? Contact your team administrator or see the full Rune deployment guide.

Configuration

Configuration File

~/.rune/config.json:

{
  "vault": {
    "endpoint": "your-vault-host:50051",
    "token": "your-vault-token"
  },
  "envector": {
    "endpoint": "runestone-xxx.clusters.envector.io",
    "api_key": "your-api-key"
  },
  "state": "active"
}

Starting the MCP Server

cd rune && ./scripts/start-mcp-servers.sh

Logs: ~/.rune/logs/envector-mcp.log

Vault MCP runs on a remote server deployed by the team admin via rune-admin, not locally.

Plugin States

State	Behavior
Active	Full functionality — capture and recall enabled, fail-safe switches to Dormant on errors
Dormant	No network requests, no token waste — shows setup instructions, ready to activate

Set "state": "active" in config after infrastructure is ready. The plugin automatically falls back to Dormant if operations fail.

For Team Administrators

Rune requires a deployed Rune-Vault server and an enVector Cloud account. The Vault holds the team's secret key for decrypting search results — it is the single point of trust in the system.

Deploying Infrastructure

See the Rune-Admin Repository:

1. Deploy Rune-Vault — OCI/AWS deployment via Terraform. Vault holds the secret key and enforces access policy (max results per query, audit trail).
2. Create enVector Cloud account — Sign up at envector.io, create a cluster, generate API keys.
3. Provision team index — Set the shared index name on the Vault server. All team members connecting to this Vault automatically use the same index.

Onboarding Team Members

Provide each team member with:

1. Vault gRPC endpoint and authentication token (same for all members)
2. enVector cluster endpoint and API key (shared or individual)

Members install the plugin and enter these credentials in ~/.rune/config.json. See examples/team-setup-example.md for a complete walkthrough.

Security Management

• Token rotation: Generate new Vault token, distribute to current members, revoke old token.
• Access revocation: Rotate Vault token — departed members lose access immediately.
• Multiple projects: Deploy separate Vault instances per project for isolated memory spaces.

Full deployment guide: https://github.com/CryptoLabInc/rune-admin/blob/main/deployment/README.md

Security & Privacy

Zero-Knowledge Encryption:

• All data is encrypted client-side using Fully Homomorphic Encryption (FHE) before leaving your machine.
• enVector Cloud performs similarity scoring on encrypted data only — the server never accesses plaintext.
• Rune-Vault decrypts only score and metadata ciphertext (not raw vectors) to select top-k results.

Data Storage:

• Local: Credentials in ~/.rune/config.json (user-only access recommended: chmod 600).
• Cloud: Only FHE-encrypted vectors and encrypted metadata on enVector Cloud. No plaintext stored remotely.

Third-Party Sharing:

• Rune does not share data with third parties. In team deployments, Vault is operated by your team admin.

Your Rights:

• Configuration reset: Delete ~/.rune/config.json to remove all local credentials.
• Full removal: Uninstall the plugin and delete ~/.rune/.

Troubleshooting

Plugin not working?

cd rune && ./scripts/check-infrastructure.sh

Missing credentials?

cp config/config.template.json ~/.rune/config.json
# Edit with your credentials, set "state": "active"

Need to reset?

rm ~/.rune/config.json

Related Projects

• Rune-Admin - Infrastructure deployment and admin tools
• pyenvector - FHE encryption SDK
• enVector Cloud - Encrypted vector database

Support

• Issues: GitHub Issues
• Documentation: Full Rune Docs
• Email: zotanika@cryptolab.co.kr

License

Apache License 2.0 - See LICENSE

Credits

Built by CryptoLabInc

Part of the Rune organizational memory ecosystem.