Six in-process middlewares for OpenClaw: HITL approvals, prompt-injection guardrails, PII redaction, tool-call budget...
Copy the install, test the workflow, then decide if it earns a permanent slot.
Still active enough to matter. Good candidate for a fast stack test instead of a long evaluation loop.
Copy the install, test the workflow, then decide if it earns a permanent slot.
Reasonable to try, but it will take more than a quick skim to get real signal.
GitHub health unknown. no security policy. 0 open issues make this testable, but not something to trust blind.
AI Agent
OpenClaw
Model
Multiple
Fastest way to find out if openclaw-middleware-suite belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/Sapience-AI/openclaw-middleware-suite ~/.claude/agents/openclaw-middleware-suiteRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/agents/openclaw-middleware-suiteNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ agents/ │ └─ openclaw-middleware-suite/ ← installs here └─ settings.json
Six in-process middlewares for OpenClaw: HITL approvals, prompt-injection guardrails, PII redaction, tool-call budgets, context compaction, and complexity-aware model routing. Zero telemetry, all state local.