Skip to main content

​
Choose your agent

Arrange deployment access, then follow the setup for your agent. OpenClaw 1.2.11 is verified in both npm and its GitHub release. The npm-prefixed package completed a normal isolated standalone OpenClaw install. Installation does not itself enable the plugin or establish runtime protection; follow the pinned setup guide and verify the supported boundaries. OpenCode 0.4.9 remains a source-only Git/local distribution and is not published to npm. Native OpenCode 2.2.6 PTY qualification loaded the complete plugin package, required a distinct slash-completion or command-palette result row before selection, and observed the resulting toast and clean owned-process shutdown on both routes. OpenCode exposes no equivalent final-assistant-text hook, and native deactivation cleanup is not observable through its public interface. For each agent, confirm its supported platform, lifecycle hooks, and blocking controls in its setup guide. For managed Macs, let the macOS app prepare supported integrations. Coordinate manual plugin setup with the Mac’s managed configuration.

​
Codex and Claude Code

Contact Silmaril for plugin access and installation instructions. For managed protection on Macs, use the macOS app.

​
Pi

The qualified Pi 1.5.0 host and plugin require Node.js 22.19.0 or newer. Install the published package.
Or install the matching Git release.
Follow the Pi setup guide to configure deployment access. Each input callback receives a fresh request identity. Retries of that classification keep the same identity.

​
Understand host boundaries

Hook names do not imply equal containment across hosts. A pre-tool hook can deny an action only when that host honors its deny response. A post-tool replacement can change later model context on supported surfaces, but it cannot undo a tool side effect. A final-message replacement cannot retract tokens that were already streamed.

​
Verify the plugin

Start a new agent session and verify its activity in your Firewall. Check the hook names for the actions you intend to protect. Use a controlled test agreed with Silmaril to confirm blocking on supported boundaries. Observed activity proves that a hook reached the Firewall. Verify native denial, replacement, and stream withholding separately for each boundary you depend on.

​
Next steps

To protect a service you run, start with the quick start. To manage protection for coding agents across Macs, use Silmaril for macOS. To review findings from an MCP client, connect Firewall MCP.