@VladUZHchecks…feat/sidclaw-governance-example → next1 files · +102 −0review: @haxzieupdated 8h agoAdds a Python example showing how to govern Composio tool execution with SidClaw — an open-source approval and audit layer for AI agents.
The example uses Composio's native before_execute / after_execute modifier API, so it integrates directly with composio.tools.execute() without any changes to Composio internals.
python/examples/sidclaw_governance.py — a standalone script showing:
create_composio_governance_modifiers() from SidClawcomposio.tools.execute()GITHUB_CREATE_ISSUE → operation: "create_issue", target_integration: "github"ActionDeniedError when policy denies or requires approval| Policy decision | Behavior |
|---|---|
allow | Tool executes immediately. Outcome recorded to hash-chain audit trail. |
approval_required | Execution pauses until a human approves in the SidClaw dashboard. |
deny | ActionDeniedError raised. Tool never executes. |
Composio gives agents access to 1000+ tools. As agents move to production — especially in regulated industries (financial services, healthcare) — teams need a governance layer that decides whether an agent should actually be allowed to execute a given Composio action, and can produce an audit trail of every execution.
SidClaw fills that gap using Composio's own modifier API, so it's fully compatible with any existing Composio setup.
pip install sidclaw)Addressed the Cursor Bugbot review — this is a false positive.
The code uses modifiers=modifiers on lines 78 and 95 (passing the list directly to the modifiers parameter), not **modifiers dict unpacking. This matches the existing Composio examples pattern.
The comment on line 42 says "returns a list of Modifier objects" — the bot misread it as "returns before_execute and after_execute functions."
No code changes needed. Ready for review.
Someone is attempting to deploy a commit to the Composio Team on Vercel.
A member of the Team first needs to authorize it.
beep boop inactive for 60 days, closing in 48 hours