Agents and IDEsClaude Code

Connect Claude Code

Install the AgentKeeper plugin in Claude Code, prove that its hooks loaded, and validate one allowed and one blocked action before rollout.

Use this guide for one Claude Code workstation. For repository-managed hooks, use GitHub repo hooks. For an endpoint fleet, start with the Windows, macOS, or Linux package and use this page to validate the resulting Claude Code session.

Prerequisites

  • A Claude Code version that supports plugins and hooks.
  • An AgentKeeper account with permission to connect a workstation.
  • A test policy with one harmless allowed action and one controlled denied action. Do not test a destructive command against real data.

Install the plugin

Run these commands inside Claude Code:

/plugin marketplace add rad-security/claude-code-plugin
/plugin install agentkeeper
/reload-plugins
/agentkeeper:connect

Complete the browser approval, then fully quit and reopen Claude Code. Reloading makes the connect command available in the current session; restarting proves that Claude Code loads the plugin and its hooks at startup.

Validate the live hook

  1. In the restarted Claude Code session, ask Claude to list files in a test workspace.
  2. Open Activity in AgentKeeper and filter to the workstation and Claude Code source.
  3. Confirm the real action appears. A connect response or self-test does not satisfy this step.
  4. Run the controlled action that the test policy denies.
  5. Confirm Claude Code refuses the action before execution and Activity records a blocked verdict with the expected policy or detector.

The workstation is ready when a restarted Claude Code session produces fresh Activity evidence and a known denied action is stopped before execution.

Understand the boundary

AgentKeeper can block only when Claude Code emits a supported event before the action. Post-tool and lifecycle events provide audit or feedback; they cannot undo a completed action. If the hook cannot reach AgentKeeper, the integration fails open so a service outage does not stop development.

Maintain or remove the integration

  • Re-run /reload-plugins after a plugin update, then restart Claude Code.
  • Repeat the allowed-action and controlled-block checks after a Claude Code, plugin, policy, or package change.
  • Use Setup health for a stale or missing hook.
  • Use Uninstall one workstation or fleet rollback for removal and rollback.
Was this page helpful?