On a more theoretical level, I’m interested in the idea of building customized access subsets through a templated schema on individual APIs. The mechanisms are a little different, git is local with a remote mirror handled by the daemon, Stripe is more simple with more-or-less static requests, and the Vercel CLI opens a connection where it runs through a series of requests within a window with a pre-defined grant. But underneath the technical aspects remains the same idea of customizing access with an almost arbitrary precision.
There’s a quote from the West Wing about money in politics that I’ll paraphrase here. “Money in politics is like water on pavement, it will find every crack.” I believe this to be increasingly true for authorization surfaces in the age of agentic AI. Pre-defined roles and keys will have extraneous permissions for any one task you might trust an agent with. You couple these excess permissions across a number of providers and the combinatorial growth in possible actions start getting more and more dangerous. Cermet is an attempt to get ahead of that.
https://github.com/suarezc/cermet
I was having fun building with Claude, I was having less fun knowing it had access to all my projects in Github through the CLI and gh. You put your token in the Cermet daemon, you write your parameters in the SQL-eqsue prose, your agent can only do those things. Right now it supports a healthy subset of Github and Stripe operations and lets you deploy through Vercel.
What models do you use for the diff level edits? My concerns would be speed, though I'm coming from letting opus ruminate for minutes at a time so my heuristics may be off.
I've been suckered into running claude code and codex independently and vaguely scanning the output before moving on. I don't love the code-base familiarity that produces.Anybody figure out a neat harness setup where one goes file by file, method by method with the agent? Looking for suggestions and what the SOTA is for this sort of thing.