By CryptoLabInc
Capture and retrieve encrypted organizational memory with zero-knowledge privacy, enabling teams to store institutional knowledge, search past decisions, and receive context-aware answers via FHE encryption and HashiCorp Vault integration.
Activate Rune (resume from dormant) and verify pipelines come up healthy
Capture organizational context to encrypted memory
Configure Rune — collect Vault credentials and write ~/.rune/config.json
Deactivate Rune to pause organizational memory without clearing configuration
View recent capture history
Continuously monitors team communications and artifacts to identify and capture significant decisions, architectural rationale, and institutional knowledge. Converts high-value context into encrypted vector embeddings for organizational memory.
Searches organizational memory for relevant decisions, synthesizes context from multiple sources, and provides actionable insights. Handles FHE decryption securely through Vault.
Admin access level
Server config contains admin-level keywords
Uses power tools
Uses Bash, Write, or Edit tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Encrypted shared memory for AI agents.
Rune gives every AI agent on your team the collective experience of the entire organization — automatically, privately, and without anyone searching for it.
Without Rune With Rune
━━━━━━━━━━━━ ━━━━━━━━━
Developer: "Should we use MongoDB?" Developer: "Should we use MongoDB?"
Agent: "MongoDB is great for Agent: "Your team chose PostgreSQL
flexible schemas..." over MongoDB in March. ACID
compliance was non-negotiable
(generic advice, no team context) for transaction integrity."
Two weeks later: "Wait, the team The developer never searched.
already rejected MongoDB??" The agent just knew.
Works with Claude Code, Codex CLI, Gemini CLI, and any MCP-compatible agent.
Claude Code:
# From terminal (local clone)
$ claude plugin marketplace add ./
$ claude plugin install rune
# From inside a Claude Code session (remote)
> /plugin marketplace add https://github.com/CryptoLabInc/rune
> /plugin install rune
Gemini CLI:
# From terminal
$ gemini extensions install https://github.com/CryptoLabInc/rune.git
Codex CLI:
# From inside a Codex session
> $skill-installer install https://github.com/CryptoLabInc/rune.git
Your next step is always
/rune:configure. The plugin install only places a small bootstrap; the actual runtime (rune-mcp + runed daemon) is downloaded the first time you run/rune:configure, in a single flow that also collects your Vault credentials. You never need to run a separate install command yourself.
> /rune:configure # Claude Code, Gemini CLI
> $rune configure # Codex CLI
You'll need from your team admin:
That's all. enVector Cloud credentials are delivered automatically via the Vault bundle. On a fresh machine, /rune:configure also handles binary download and daemon setup in the same step.
Don't have these? See rune-admin for deployment, setup/check-prerequisites.md for the full prerequisite checklist, or examples/team-setup-example.md for a walkthrough.
Once configured, Rune works automatically. No commands to memorize. No queries to write. Just work with your agent as usual.
Your agent will:
Debugging that saves 4 hours:
Dev: "The payment service is timing out"
Agent: "A similar timeout was investigated last month — root
cause was connection pool exhaustion under concurrent
webhook processing. Fix was async batch processing
with a 50-connection pool limit."
Knowledge from a teammate's past session, surfaced automatically.
Onboarding that just works:
New hire: "I'm thinking of using Redis for the job queue"
Agent: "Your team evaluated Redis vs SQS for the job queue
in February. SQS was chosen because Redis required
dedicated ops capacity the team doesn't have."
The new hire's agent already has institutional knowledge
they haven't been taught yet.
You don't "query" Rune. Your agent draws from it the way an experienced engineer draws from years of past projects — the relevant context just surfaces.
| Approach | Limitation | Rune |
|---|---|---|
| Built-in memory | Siloed per vendor. Your team's Claude memory and Codex memory never connect. | One shared memory across all agents. Vendor-independent. |
| RAG pipelines | Chunks documents into fragments. Destroys reasoning structure. Requires ongoing pipeline maintenance. | Agent judges significance and stores decisions, not document chunks. No pipeline to maintain. |
| Wikis & docs | Manual. Nobody updates the wiki after the meeting. | Captures automatically during work, not after. |
| Plaintext vector DBs | Your organizational knowledge is readable by the cloud provider. | FHE encryption — the cloud stores and searches only ciphertext. Mathematically guaranteed. |
Agent Swarm (your team) Cloud Infrastructure
━━━━━━━━━━━━━━━━━━━━━━ ━━━━━━━━━━━━━━━━━━━━
Alice's Agent ─┐
Bob's Agent ───┤── MCP ──► enVector Cloud (encrypted vectors)
Carol's Agent ─┘ │
Rune-Vault (secret key holder)
decrypts similarity scores only
Capture: Agent judges significance → generates reusable insight → novelty check against existing memory → FHE encrypt → store
npx claudepluginhub cryptolabinc/rune --plugin runeQuery Intent Solutions' governed knowledge brain from Claude Code — qmd://-cited answers, per-user audit, deterministic governance. Compile, then govern.
The memory layer for agent teams. Deterministic retrieval, hard per-project isolation, zero LLM in the critical path.
Persistent memory for Claude Code — memories survive across sessions, projects, and machines
Bridge Claude Code's session lifecycle into AKB's agent-memory vault.
Long-term semantic memory for Claude Code, powered by OpenViking. Auto-recall relevant memories at session start and capture important information during conversations.
Persistent agent memory that survives across sessions — auto-compacting 3-tier memory with hybrid search. Your agent remembers what it learned, decided, and built.