Install
openclaw skills install lulu-cliClawHub Security found sensitive or high-impact capabilities. Review the scan results before using.
Manage LuLu macOS firewall rules from the command line. Use when connections are blocked, domains need allowing/blocking, or firewall rules need reviewing. Prevents data exfiltration while allowing essential services. Triggers include "connection blocked", "allow domain", "firewall rules", "check blocks", "lulu", "unblock".
openclaw skills install lulu-cliCLI for managing LuLu macOS firewall rules. LuLu is a free, open-source macOS firewall that blocks unknown outgoing connections.
Requires: macOS 13+, LuLu installed, sudo for write operations.
LuLu runs as a macOS system extension. When configured in passive mode with new connections defaulting to block, any unrecognized outbound connection is silently blocked and logged as a passive rule.
/Library/Objective-See/LuLu/rules.plist (NSKeyedArchiver binary format, owned by root)reload (kill + auto-restart) is needed after changesrecent without needing a reloadMost usage follows this pattern:
# 1. Check recent blocks
lulu-cli recent 10
# 2. Allow the blocked domain
sudo lulu-cli add --key '*' --path '*' --action allow --addr api.example.com --port 443
# 3. Apply
sudo lulu-cli reload
List all firewall rules. Optionally filter by keyword (matches key or binary path).
lulu-cli list # all rules
lulu-cli list curl # rules for curl
lulu-cli list node # rules for node
lulu-cli list '*' # global/wildcard rules only
No sudo required.
Show the N most recent block rules, sorted by creation date (newest first). Default: 20.
lulu-cli recent # last 20 blocks
lulu-cli recent 5 # last 5 blocks
No sudo required. This is the first command to run when diagnosing connection failures.
Add a new firewall rule. Requires sudo.
Flags:
--key KEY -- signing identity (e.g. com.apple.curl) or * for global--path PATH -- binary path or * for global--action allow|block -- rule action--addr ADDR -- domain, IP, or regex pattern (default: *)--port PORT -- port number or * for any (default: *)--regex -- treat --addr as a regex pattern# Allow a domain globally (all apps)
sudo lulu-cli add --key '*' --path '*' --action allow --addr example.com --port 443
# Allow a domain and all subdomains (regex)
sudo lulu-cli add --key '*' --path '*' --action allow \
--addr '^(.+\.)?example\.com$' --port '*' --regex
# Allow for a specific app only
sudo lulu-cli add --key "/usr/bin/curl" --path /usr/bin/curl \
--action allow --addr example.com --port 443
# Block a domain
sudo lulu-cli add --key '*' --path '*' --action block --addr malicious.com --port '*'
Delete rule(s) by key. Requires sudo.
Flags:
--key KEY -- required--uuid UUID -- specific rule UUID. If omitted, deletes ALL rules for the key.# Delete a specific rule by UUID
sudo lulu-cli delete --key "com.apple.curl" --uuid "A1B2C3D4-..."
# Delete ALL rules for a key
sudo lulu-cli delete --key "com.apple.curl"
Delete rules matching specific criteria. Requires sudo.
Flags:
--key KEY -- required--action allow|block -- optional filter--addr ADDR -- optional filter--port PORT -- optional filter# Delete all block rules on port 53 for curl
sudo lulu-cli delete-match --key "com.apple.curl" --action block --port 53
Toggle a rule's enabled state. Requires sudo.
Flags:
--key KEY -- required--uuid UUID -- requiredsudo lulu-cli enable --key '*' --uuid A1B2C3D4-...
sudo lulu-cli disable --key '*' --uuid A1B2C3D4-...
Restart the LuLu system extension to apply rule changes. Requires sudo.
sudo lulu-cli reload
Kills the extension process. macOS auto-restarts registered system extensions within ~8 seconds. There is a brief gap in filtering during the restart.
Always run reload after add, delete, enable, or disable.
Show usage information.
lulu-cli help
com.apple.curl) or binary path for unsigned apps. Use * for global rules that apply to all apps.allow or block* (any)* (any)default (system), apple, user (manually created), passive (auto-created from blocked connections)* and path=* apply to all applicationsNot all processes should get unrestricted internet access. When using LuLu as a security boundary for AI agents:
Allow-all (addr=* port=*) -- Only for processes the agent cannot invoke:
Domain allowlist only -- Any process an agent could use to reach the internet:
node (Claude Code, OpenClaw runtime)python / uv (agent scripts)curl (command-line HTTP)git / gh (could push to arbitrary remotes)When in doubt, leave a process restricted to the domain allowlist. It's easy to add an allow-all later; harder to notice data leaking through an over-permissive rule.
If a connection is failing:
lulu-cli recent to see if it was blockedsudo lulu-cli reload to applyIf the domain doesn't appear in recent, the problem is not the firewall.