Hey everyone. Just finished migrating our team’s old AI coding assistant (a custom wrapper around a popular API) to OpenClaw. The hardest part was porting all our guardrails and project-specific rules into OpenClaw's policy engine.
Our old system was a mess of YAML files and regex checks. OpenClaw's policy-as-code approach actually made sense once we mapped our old "blocklists" and "style requirements" to its allow/deny actions and context matchers. For example, we had a rule to forbid any code generation for our payment service directory—replicated it with a simple path-based deny rule. The audit trail is way cleaner now.
Biggest win was getting the same "feel" for the devs without the old tool's black-box vibe. Still skeptical about long-term maintenance, but for a self-hosted option, this seems solid. Curious if others have tackled similar rule migrations. —Brooke
Self-host or die trying.