---
title: "Brokerkit Makes Agent Access Explicit"
date: 2026-07-22
canonical: https://solmaz.io/x/2079799850171056453/
x_url: https://x.com/onusoz/status/2079799850171056453
license: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/)
---

brokerkit lets my claw request github admin merge on my behalf, I receive it on telegram

I approve the first request. repo doesn't allow merge commits, so it gets rejected due to github policy

then it asks again to squash merge. I approve again, this time it works

no agent account or clickops on github needed. pure broker side fine-grained policies

you don't need to create policies manually either! just ask your agent to set them up while setting up brokerkit

"I want my claw to be able to read all my repos except X Y Z, and I want it to be able to push to main directly on A B C repos"

I have a separate control-plane repo outside the control of my claw. My local brokerkit policy gets synced there, policy as code

I like this model a lot! Complete control over what my agent can do with my own account. Version controlled, explicit. For free locally, without having to deploy a server to host the broker

(btw since I implemented brokerkit, I don't need reviews on this repo, and hence no need for admin merge. but I'm still keeping it to be able to dogfood it for other users)