armorclaude

ArmorClaude

ArmorIQ intent-based security enforcement plugin for Claude Code and Claude Cowork. Enforces that an AI agent declares what it intends to do before doing it, and every action is checked against that declared intent.

How It Works

User Prompt ──► UserPromptSubmit hook ──► Intent plan captured ──► Signed token
                                                                        │
Tool Call ──► PreToolUse hook ──► Policy check ──► Intent verification ──┘
                                      │                    │
                                  deny/allow         drift detected?
                                                          │
Tool Result ──► PostToolUse hook ──► Audit log sent to IAP

1. Before the agent acts: Intercepts prompts, captures a structured plan (from Claude's built-in plan mode or an LLM fallback call), and sends it to ArmorIQ IAP for a signed intent token.
2. On every tool call: Checks the tool against the approved plan, verifies the token hasn't expired, evaluates local policy rules (allow/deny by tool name, data classification like PCI/PII), and optionally verifies CSRG cryptographic proofs. Blocks execution if any check fails.
3. After tool execution: Sends audit logs to ArmorIQ IAP for compliance tracking.
4. Fail-closed: If planning fails, identity is missing, or the token is invalid — all tool calls are blocked by default.

Install

One-line install (recommended)

curl -fsSL https://armoriq.ai/install_armorclaude.sh | bash

This adds the armoriq Claude Code marketplace and installs the armorclaude plugin. Dependencies are installed automatically on first hook fire.

Manual install (Claude Code marketplace)

claude plugin marketplace add armoriq/armorClaude
claude plugin install armorclaude@armoriq

Verify

claude plugin list
# ❯ armorclaude@armoriq  Status: ✔ enabled

claude mcp list | grep armorclaude
# plugin:armorclaude:armorclaude-policy: ... ✓ Connected

First-run behavior

The plugin ships its Node dependencies uninstalled. On the first launch (first hook fire or first MCP-server start), scripts/bootstrap.mjs performs a one-time npm install and prints to stderr:

[armorclaude] installing dependencies (one-time)...

• Requires Node.js >= 20 and npm on PATH, plus network access on that first run.
• The bundled MCP server (armorclaude-policy) registers once dependencies finish installing; it stays connected on subsequent runs without reinstalling.
• No API key is needed to start. With api_key blank the plugin runs in local-only mode (no data leaves your machine — see Data & Privacy); a key only adds backend audit, intent tokens, and CSRG proofs.

If claude mcp list does not show ✓ Connected, run the server directly from the plugin directory to surface the install/startup error:

node scripts/bootstrap.mjs mcp

Update / disable / uninstall

claude plugin update armorclaude
claude plugin disable armorclaude   # turn off without removing
claude plugin enable  armorclaude
claude plugin uninstall armorclaude

Requirements

• Claude Code 2.x (claude --version)
• Node.js >= 20
• (Optional) ArmorIQ API key for backend audit + CSRG proofs — get one at https://armoriq.ai

Getting an API key via the CLI: account registration (armoriq register) is provided by the Python CLI, not the TypeScript CLI. Install it with pip3 install armoriq-sdk, then run armoriq register. On macOS use pip3 (plain pip is often not on PATH).

Structure